SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[doktor83]

It looks like newer drivers (adrenaline 2019) slow down the crashing issue that occurs because the memory or page file grows too much.
Anyone else can confirm this?

Testing now 19.3.2 and ONT 0.2.8, the timing level whatever i put isn't changing the hashrate for me on Vega56. Is it just me or .. ?

First tests show that hashrate is worse than on 18.6.1 - tested on bittube and v4.
If you use the compiled kernels from 18.6.1 on 19.3.2 then the hashrate will be also good.

[1679594178]

1679594178

[1679594178]

1679594178

[1679594178]

1679594178

[MinermanNC]

I have SRB MINER CN 1.181 running perfectly on windows 7 pushing 2 AMD 7790's

Can not get it to run correctly on Windows 10 pushing 1 R9 270x. It starts and receives work from pool, but does not find any shares. Nor does it display any GPU readings "temp, fan speed etc.. shows all zeros there.

It does show hashing speed of 470, and it identify's the card when I first launch it and again it receives work from pool.  

I have tried the recommended driver 18.5.1 and even tried different compatibility settings. Still no luck getting a share.

I have a feeling its a W10 issue? as it runs fine on W7 with older cards. Any ideas? still testing other cards on different OS

Thanks  

[UnclWish]

It looks like newer drivers (adrenaline 2019) slow down the crashing issue that occurs because the memory or page file grows too much.
Anyone else can confirm this?

Testing now 19.3.2 and ONT 0.2.8, the timing level whatever i put isn't changing the hashrate for me on Vega56. Is it just me or .. ?

First tests show that hashrate is worse than on 18.6.1 - tested on bittube and v4.
If you use the compiled kernels from 18.6.1 on 19.3.2 then the hashrate will be also good.

I think it has long been necessary to update your miner for optimal work with newest drivers. 18.6.1 is too old already.

[doktor83]

It looks like newer drivers (adrenaline 2019) slow down the crashing issue that occurs because the memory or page file grows too much.
Anyone else can confirm this?

Testing now 19.3.2 and ONT 0.2.8, the timing level whatever i put isn't changing the hashrate for me on Vega56. Is it just me or .. ?

First tests show that hashrate is worse than on 18.6.1 - tested on bittube and v4.
If you use the compiled kernels from 18.6.1 on 19.3.2 then the hashrate will be also good.

I think it has long been necessary to update your miner for optimal work with newest drivers. 18.6.1 is too old already.

Newer is not always better, as still the best hashrate can be achieved on 18.6.1 ... old or not

[doktor83]

I have SRB MINER CN 1.181 running perfectly on windows 7 pushing 2 AMD 7790's

Can not get it to run correctly on Windows 10 pushing 1 R9 270x. It starts and receives work from pool, but does not find any shares. Nor does it display any GPU readings "temp, fan speed etc.. shows all zeros there.

It does show hashing speed of 470, and it identify's the card when I first launch it and again it receives work from pool.  

I have tried the recommended driver 18.5.1 and even tried different compatibility settings. Still no luck getting a share.

I have a feeling its a W10 issue? as it runs fine on W7 with older cards. Any ideas? still testing other cards on different OS

Thanks  

When you try out different drivers every time clear the cache directory. R9 270x cards work fine on W10 and 18.6.1 drivers.

[chimaeraa]

It looks like newer drivers (adrenaline 2019) slow down the crashing issue that occurs because the memory or page file grows too much.
Anyone else can confirm this?

Testing now 19.3.2 and ONT 0.2.8, the timing level whatever i put isn't changing the hashrate for me on Vega56. Is it just me or .. ?

First tests show that hashrate is worse than on 18.6.1 - tested on bittube and v4.
If you use the compiled kernels from 18.6.1 on 19.3.2 then the hashrate will be also good.

i F8 .

no i think something in your setting is wrong . B.C  i got 2300 H/S . i seen some screen shot before.


i use new new compiled keener and it's good.

[Iamtutut]

DOKTOR83, there is a memory pill for AMD

Could you implement it on windows ? Right now it's linux only.

Here: https://bitcointalk.org/index.php?topic=5123724.0

[doktor83]

DOKTOR83, there is a memory pill for AMD

Could you implement it on windows ? Right now it's linux only.

Here: https://bitcointalk.org/index.php?topic=5123724.0

No, im not interested. Someone else will probably do it.

[JuanHungLo]

Using latest AMD driver, 19.3.3, win10, SRB 1.8.1, stock intensity, NO PPT, latest OverdriveNTool beta,
Vega 56@64 1552/852, 1100/900 getting H/s = 1994 average, stable for Monero.  Not sure of power draw.

[igotek]

i have just download the latest version.
It works well but there is a problem if i set gpus manually.

No problem on all 3 gpu

Code:

{
"cryptonight_type" : "stellitev8",
"intensity" : 0,
"double_threads" : true
}

mining not started and bat file close immediately.

Code:

{
"cryptonight_type" : "stellitev8",
"intensity" : 0,
"double_threads" : true

"gpu_conf" :
[
{ "id" : 0, "intensity" : 0 , "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 0 , "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 0 , "worksize" : 16, "threads" : 2}
]
}

Is there any chances to set gpus manually ?

[doktor83]

i have just download the latest version.
It works well but there is a problem if i set gpus manually.

No problem on all 3 gpu

Code:

{
"cryptonight_type" : "stellitev8",
"intensity" : 0,
"double_threads" : true
}

mining not started and bat file close immediately.

Code:

{
"cryptonight_type" : "stellitev8",
"intensity" : 0,
"double_threads" : true

"gpu_conf" :
[
{ "id" : 0, "intensity" : 0 , "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 0 , "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 0 , "worksize" : 16, "threads" : 2}
]
}

Is there any chances to set gpus manually ?

yes, put a comma after the double thread true line

[igotek]

Code:

{
"cryptonight_type" : "stellitev8",
"intensity" : 0,
"double_threads" : true,

"gpu_conf" :
[
{ "id" : 0, "intensity" : 0 , "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 0 , "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 0 , "worksize" : 16, "threads" : 2}
]
}

it is the same. not working. The strange thing is older versions work with same config.

[anvl]

 Some bug in the miner. On my systems with two CPUs one card is recognized as BUS: -125 by the miner whereas the system says it's 131.    Seems like not enough bits somewhere. As a result this card doesn't report ADL information.
 doktor83, could you please correct this error in your great miner?

[iRonNuke]

Why am I getting a lot of rejected shares? "Pool rejected result 0x000074E1 for job[2] [low difficulty share]" By a lot I mean some, most shares are ofcourse accepted but still, quite frequent.

Pool difficulty is set at 120000 by default. May I change it for better results?

The pool I'm using is nanopool.org btw.

[doktor83]

Why am I getting a lot of rejected shares? "Pool rejected result 0x000074E1 for job[2] [low difficulty share]" By a lot I mean some, most shares are ofcourse accepted but still, quite frequent.

Pool difficulty is set at 120000 by default. May I change it for better results?

The pool I'm using is nanopool.org btw.

You get low diff shares when your gpu returns a bad result. So loosen on your OC , or depending of your card, maybe you use 'bad' mem. straps.

[RuMiner]

DOKTOR83, there is a memory pill for AMD
Could you implement it on windows ? Right now it's linux only.

Cryptonights are not so sensitive to memory straps, it's good for ETH

[iRonNuke]

Why am I getting a lot of rejected shares? "Pool rejected result 0x000074E1 for job[2] [low difficulty share]" By a lot I mean some, most shares are ofcourse accepted but still, quite frequent.

Pool difficulty is set at 120000 by default. May I change it for better results?

The pool I'm using is nanopool.org btw.

You get low diff shares when your gpu returns a bad result. So loosen on your OC , or depending of your card, maybe you use 'bad' mem. straps.

Is there any way to see what GPU that is getting this error, if it's just one or all GPUs? I can see how many errors and frequency in %. It just says what job number it is?

95,5% accepted shares. Maybe not much to care about in about one hour?

[pbfarmer]

Testing now 19.3.2 and ONT 0.2.8, the timing level whatever i put isn't changing the hashrate for me on Vega56. Is it just me or .. ?

I've never seen any results from changing timing levels in wattman.  I get the sense they put in the functionality, maybe to provide actual timings at a later date.

[pbfarmer]

DOKTOR83, there is a memory pill for AMD
Could you implement it on windows ? Right now it's linux only.

Cryptonights are not so sensitive to memory straps, it's good for ETH

This is absolutely not true.  At least earlier versions of CN (haven't personally confirmed w/ cnv4) saw significant benefits from lower latencies.  ETH on the other hand, being bandwidth sensitive, does best w/ higher clocks, which in some cases requires higher latencies.  For example - the commonly available 'ubermix' straps for samsung were great for CN - they do not seem to be the best for ETH as the timings are so tight, clocks tend to be capped around 2K.

[AVP]

Is anyone experiencing crashes & freezes on GRAFT algo ?

I'm seeing this on RX 470 rigs & RX 560 rigs. (RX 570 rigs seem fine)