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

[Sgsg666]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise  

So you getting about 2200h now or more?

yeah dok im sticking to 1.5.8 my vegas got higher output compared to 1.5.9. https://www.reddit.com/r/havenprotocol/comments/8ohw6t/haven_v3_hardfork_coming_in_2_weeks/ - haven is also forking.
https://www.reddit.com/r/stellite/comments/8p1tss/v4_mandatory_update_for_all_node_maintainers_of/ - stellite too

[doktor83]

thanks for forking infos guys, srb is prepared for stellitev4, the other two ill have to check them out.

[livada]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise 

So you getting about 2200h now or more?

he say 200 per RIG not per CARD

[henri2018]

V1.5.9

- Added "max_difficulty" parameter in pools, if reached miner will reconnect to pool
- Better logging on miner crash
- Kernels are now built in Cache directory
- Probably fixed situation when miner crashes on pool switch
- Fixed .srb file creation on every miner run
- Hopefully reduced nicehash duplicate share errors
- Changed the way devfee pools are used

+ Now you can define a "max_difficulty" for every pool you have in pools config. Sometimes it happens that pool sends abnormally high difficulty, and miner can't find a share for a long time. In this case, by setting "max_difficulty", when ever pool difficulty is higher than the value you set, miner disconnects and reconnects to the pool.

+ There is now a Cache directory where the miner creates cached versions of OpenCL kernels

+ Some reported miner crash after multiple pool disconnect/reconnects , not able to log in etc.. I hope i found the cause of it and fixed it

+ Learned from the previous big mistake with devfee pools hardcoded in the miner, now miner gets the list of devfee pools from http://srbminer.com, so please allow/don't block it on your firewall

Cool stuff, dok. Starting to move to 1.5.9 now, 5 left remaining  .

EDIT:
All 8 rigs now running with 1.5.9, and looking good.

Thanks, dok!

[doktor83]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise  

So you getting about 2200h now or more?

yeah dok im sticking to 1.5.8 my vegas got higher output compared to 1.5.9. https://www.reddit.com/r/havenprotocol/comments/8ohw6t/haven_v3_hardfork_coming_in_2_weeks/ - haven is also forking.
https://www.reddit.com/r/stellite/comments/8p1tss/v4_mandatory_update_for_all_node_maintainers_of/ - stellite too

1.5.8 shouldnt be faster than 1.5.9, cause nothing was changed that could impact speed. Placebo 

[doktor83]

V1.5.9

- Added "max_difficulty" parameter in pools, if reached miner will reconnect to pool
- Better logging on miner crash
- Kernels are now built in Cache directory
- Probably fixed situation when miner crashes on pool switch
- Fixed .srb file creation on every miner run
- Hopefully reduced nicehash duplicate share errors
- Changed the way devfee pools are used

+ Now you can define a "max_difficulty" for every pool you have in pools config. Sometimes it happens that pool sends abnormally high difficulty, and miner can't find a share for a long time. In this case, by setting "max_difficulty", when ever pool difficulty is higher than the value you set, miner disconnects and reconnects to the pool.

+ There is now a Cache directory where the miner creates cached versions of OpenCL kernels

+ Some reported miner crash after multiple pool disconnect/reconnects , not able to log in etc.. I hope i found the cause of it and fixed it

+ Learned from the previous big mistake with devfee pools hardcoded in the miner, now miner gets the list of devfee pools from http://srbminer.com, so please allow/don't block it on your firewall

Cool stuff, dok. Starting to move to 1.5.9 now, 5 left remaining  .

Maxithanks for the support 

[livada]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise  

So you getting about 2200h now or more?

yeah dok im sticking to 1.5.8 my vegas got higher output compared to 1.5.9. https://www.reddit.com/r/havenprotocol/comments/8ohw6t/haven_v3_hardfork_coming_in_2_weeks/ - haven is also forking.
https://www.reddit.com/r/stellite/comments/8p1tss/v4_mandatory_update_for_all_node_maintainers_of/ - stellite too

1.5.8 shouldnt be faster than 1.5.9, cause nothing was changed that could impact speed. Placebo  

al nije tako. 1.5.9. ti je  potpunao ista kao i 15.7 odnosno sporija od 1.5.8 pricamo o 200 HR manje po rigu kod vege kod heavy

[WebTosha]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise  

So you getting about 2200h now or more?

yeah dok im sticking to 1.5.8 my vegas got higher output compared to 1.5.9. https://www.reddit.com/r/havenprotocol/comments/8ohw6t/haven_v3_hardfork_coming_in_2_weeks/ - haven is also forking.
https://www.reddit.com/r/stellite/comments/8p1tss/v4_mandatory_update_for_all_node_maintainers_of/ - stellite too

1.5.8 shouldnt be faster than 1.5.9, cause nothing was changed that could impact speed. Placebo 

unbelievable but true. my RX 550 2gb at 1.5.8 gave out stably 6590 hashes at setting 26/8/2, and on 1.5.9 neither as more than 6510 hashes

[doktor83]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise  

So you getting about 2200h now or more?

yeah dok im sticking to 1.5.8 my vegas got higher output compared to 1.5.9. https://www.reddit.com/r/havenprotocol/comments/8ohw6t/haven_v3_hardfork_coming_in_2_weeks/ - haven is also forking.
https://www.reddit.com/r/stellite/comments/8p1tss/v4_mandatory_update_for_all_node_maintainers_of/ - stellite too

1.5.8 shouldnt be faster than 1.5.9, cause nothing was changed that could impact speed. Placebo 

unbelievable but true. my RX 550 2gb at 1.5.8 gave out stably 6590 hashes at setting 26/8/2, and on 1.5.9 neither as more than 6510 hashes

what happens on 27/8/2?

[WebTosha]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise  

So you getting about 2200h now or more?

yeah dok im sticking to 1.5.8 my vegas got higher output compared to 1.5.9. https://www.reddit.com/r/havenprotocol/comments/8ohw6t/haven_v3_hardfork_coming_in_2_weeks/ - haven is also forking.
https://www.reddit.com/r/stellite/comments/8p1tss/v4_mandatory_update_for_all_node_maintainers_of/ - stellite too

1.5.8 shouldnt be faster than 1.5.9, cause nothing was changed that could impact speed. Placebo 

unbelievable but true. my RX 550 2gb at 1.5.8 gave out stably 6590 hashes at setting 26/8/2, and on 1.5.9 neither as more than 6510 hashes

what happens on 27/8/2?

in this case, everything is not stable, or the cards do not start all at once, but only after a couple of reboots and after that in a couple of hours all the same 0 the hashes are shown and the reboot is going on. But on the other hand, the speed on version 1.5.8 strongly diverged by the indications on the pool, and 1.5.9 shows approximately equal values with the pool. So we stay on 1.5.9 I think 6500 with 13 RX 550 cards is a good result, the main thing is that there would be stability.
Thank you for the miner.

[henri2018]

V1.5.9

- Added "max_difficulty" parameter in pools, if reached miner will reconnect to pool
- Better logging on miner crash
- Kernels are now built in Cache directory
- Probably fixed situation when miner crashes on pool switch
- Fixed .srb file creation on every miner run
- Hopefully reduced nicehash duplicate share errors
- Changed the way devfee pools are used

+ Now you can define a "max_difficulty" for every pool you have in pools config. Sometimes it happens that pool sends abnormally high difficulty, and miner can't find a share for a long time. In this case, by setting "max_difficulty", when ever pool difficulty is higher than the value you set, miner disconnects and reconnects to the pool.

+ There is now a Cache directory where the miner creates cached versions of OpenCL kernels

+ Some reported miner crash after multiple pool disconnect/reconnects , not able to log in etc.. I hope i found the cause of it and fixed it

+ Learned from the previous big mistake with devfee pools hardcoded in the miner, now miner gets the list of devfee pools from http://srbminer.com, so please allow/don't block it on your firewall

wow many thanks dok, will try now mining on nicehash with max_difficulty.

ok, and report is it working like it should
You can define max_difficulty for every pool like :

{"pool" : "lotsofcoinspool1", "wallet" : "", "password" : "x", "max_difficulty" : 150000},
{"pool" : "lotsofcoinspool2", "wallet" : "", "password" : "x", "max_difficulty" : 400000}

yes I already define max_difficulty, will monitoring for a while.
just to let you know I can confirm hash rate drop after reconnecting to pool for RX Vega.

SRBMiner 1.5.9 AMD Driver 18.5.2.

First running.
https://imgur.com/a/pVgDVlp

After reconnect because of network error.
https://imgur.com/a/g4GC6xz

Edit :
Reconnecting due to high diff work perfectly.
https://imgur.com/a/8icbdsL

Bro, in my case, after reconnecting, the hashrate was drop. But after waiting a few minutes, it's back normal.
May be you were too quick to observe?

[Alantre]

Any hashrate increase? Like for 1.5.8. when you didn´t say anything and my vegas hashed like 200 more per rig, what a nice surprise 

So you getting about 2200h now or more?

he say 200 per RIG not per CARD

Apologies, I misread..I got really excited but it's still better I suppose. Will try it out this weekend

[doktor83]

V1.5.9

- Added "max_difficulty" parameter in pools, if reached miner will reconnect to pool
- Better logging on miner crash
- Kernels are now built in Cache directory
- Probably fixed situation when miner crashes on pool switch
- Fixed .srb file creation on every miner run
- Hopefully reduced nicehash duplicate share errors
- Changed the way devfee pools are used

+ Now you can define a "max_difficulty" for every pool you have in pools config. Sometimes it happens that pool sends abnormally high difficulty, and miner can't find a share for a long time. In this case, by setting "max_difficulty", when ever pool difficulty is higher than the value you set, miner disconnects and reconnects to the pool.

+ There is now a Cache directory where the miner creates cached versions of OpenCL kernels

+ Some reported miner crash after multiple pool disconnect/reconnects , not able to log in etc.. I hope i found the cause of it and fixed it

+ Learned from the previous big mistake with devfee pools hardcoded in the miner, now miner gets the list of devfee pools from http://srbminer.com, so please allow/don't block it on your firewall

wow many thanks dok, will try now mining on nicehash with max_difficulty.

ok, and report is it working like it should
You can define max_difficulty for every pool like :

{"pool" : "lotsofcoinspool1", "wallet" : "", "password" : "x", "max_difficulty" : 150000},
{"pool" : "lotsofcoinspool2", "wallet" : "", "password" : "x", "max_difficulty" : 400000}

yes I already define max_difficulty, will monitoring for a while.
just to let you know I can confirm hash rate drop after reconnecting to pool for RX Vega.

SRBMiner 1.5.9 AMD Driver 18.5.2.

First running.
https://imgur.com/a/pVgDVlp

After reconnect because of network error.
https://imgur.com/a/g4GC6xz

Edit :
Reconnecting due to high diff work perfectly.
https://imgur.com/a/8icbdsL

Bro, in my case, after reconnecting, the hashrate was drop. But after waiting a few minutes, it's back normal.
May be you were too quick to observe?

Hashrate drop after pool change (disconnect/connect) is normal, but the hash should stabilize back. The problem is if it won't go back at all.
But i am curious is this somethings specific to 18.5.2 drivers ?

[livada]

V1.5.9

- Added "max_difficulty" parameter in pools, if reached miner will reconnect to pool
- Better logging on miner crash
- Kernels are now built in Cache directory
- Probably fixed situation when miner crashes on pool switch
- Fixed .srb file creation on every miner run
- Hopefully reduced nicehash duplicate share errors
- Changed the way devfee pools are used

+ Now you can define a "max_difficulty" for every pool you have in pools config. Sometimes it happens that pool sends abnormally high difficulty, and miner can't find a share for a long time. In this case, by setting "max_difficulty", when ever pool difficulty is higher than the value you set, miner disconnects and reconnects to the pool.

+ There is now a Cache directory where the miner creates cached versions of OpenCL kernels

+ Some reported miner crash after multiple pool disconnect/reconnects , not able to log in etc.. I hope i found the cause of it and fixed it

+ Learned from the previous big mistake with devfee pools hardcoded in the miner, now miner gets the list of devfee pools from http://srbminer.com, so please allow/don't block it on your firewall

wow many thanks dok, will try now mining on nicehash with max_difficulty.

ok, and report is it working like it should
You can define max_difficulty for every pool like :

{"pool" : "lotsofcoinspool1", "wallet" : "", "password" : "x", "max_difficulty" : 150000},
{"pool" : "lotsofcoinspool2", "wallet" : "", "password" : "x", "max_difficulty" : 400000}

yes I already define max_difficulty, will monitoring for a while.
just to let you know I can confirm hash rate drop after reconnecting to pool for RX Vega.

SRBMiner 1.5.9 AMD Driver 18.5.2.

First running.
https://imgur.com/a/pVgDVlp

After reconnect because of network error.
https://imgur.com/a/g4GC6xz

Edit :
Reconnecting due to high diff work perfectly.
https://imgur.com/a/8icbdsL

pls give me comand to start NH i try but  alvay error.
Where i write this?
"nicehash" : true, - i write this in config but error.

I write  this in pool and agan error .
   {"pool_use_tls" : false, "pool" : "cryptonightv7.eu.nicehash.com:3363", "wallet" : "address", "password" : "x", "max_difficulty" : 1500000}, for 6 vega

[doktor83]

pls give me comand to start NH i try but  alvay error.
Where i write this?
"nicehash" : true, - i write this in config but error.

I write  this in pool and agan error .
   {"pool_use_tls" : false, "pool" : "cryptonightv7.eu.nicehash.com:3363", "wallet" : "address", "password" : "x", "max_difficulty" : 1500000}, for 6 vega

{
"pools" :
[
   {"pool" : "cryptonightheavy.eu.nicehash.com:3364", "wallet" : "btcwallet", "password" : "x", "nicehash" : true}
]
}

[RuMiner]

1.5.8 shouldnt be faster than 1.5.9, cause nothing was changed that could impact speed. Placebo 

I thought there were my personal suspects, but checked again after reading this and yes, 1.5.8 is a little bit faster.
1.5.9:     "hashrate_total_30min": 7738
I've terminated it and run 1.5.8 with same configs:     "hashrate_total_30min": 7746,
maybe new nicehash features add a tiny lag to a mining process?

[livada]

pls give me comand to start NH i try but  alvay error.
Where i write this?
"nicehash" : true, - i write this in config but error.

I write  this in pool and agan error .
   {"pool_use_tls" : false, "pool" : "cryptonightv7.eu.nicehash.com:3363", "wallet" : "address", "password" : "x", "max_difficulty" : 1500000}, for 6 vega

{
"pools" :
[
   {"pool" : "cryptonightheavy.eu.nicehash.com:3364", "wallet" : "btcwallet", "password" : "x", "nicehash" : true}
]
}

ok . and max dif to end?

{"pool" : "cryptonightheavy.eu.nicehash.com:3364", "wallet" : "btcwallet", "password" : "x", "nicehash" : true, "max_difficulty" : 1100000}

this is it?

HR * 40 is normal dif? 12000*40 = 480000 and limit 1100000 is to high or ??

and your port NH is 3364? my nH work on 3363 ...

PS: na v7 je skor oidentican HR na 15.8 i 1.5.9 al na heavy je HR dosta veci na 1.5.8

[lebuawu2]

pls give me comand to start NH i try but  alvay error.
Where i write this?
"nicehash" : true, - i write this in config but error.

I write  this in pool and agan error .
   {"pool_use_tls" : false, "pool" : "cryptonightv7.eu.nicehash.com:3363", "wallet" : "address", "password" : "x", "max_difficulty" : 1500000}, for 6 vega

{
"pools" :
[
   {"pool" : "cryptonightheavy.eu.nicehash.com:3364", "wallet" : "btcwallet", "password" : "x", "nicehash" : true}
]
}

ok . and max dif to end?

{"pool" : "cryptonightheavy.eu.nicehash.com:3364", "wallet" : "btcwallet", "password" : "x", "nicehash" : true, "max_difficulty" : 1100000}

this is it?

HR * 40 is normal dif? 12000*40 = 480000 and limit 1100000 is to high or ??

and your port NH is 3364? my nH work on 3363 ...

PS: na v7 je skor oidentican HR na 15.8 i 1.5.9 al na heavy je HR dosta veci na 1.5.8

pool setting should be correct, the order doesn't matter.
port 3364 for cn-heavy and port 3363 for cn-v7.
mine 9500 h/s and I put max diff 800000 base on my observation.

[lebuawu2]

V1.5.9

- Added "max_difficulty" parameter in pools, if reached miner will reconnect to pool
- Better logging on miner crash
- Kernels are now built in Cache directory
- Probably fixed situation when miner crashes on pool switch
- Fixed .srb file creation on every miner run
- Hopefully reduced nicehash duplicate share errors
- Changed the way devfee pools are used

+ Now you can define a "max_difficulty" for every pool you have in pools config. Sometimes it happens that pool sends abnormally high difficulty, and miner can't find a share for a long time. In this case, by setting "max_difficulty", when ever pool difficulty is higher than the value you set, miner disconnects and reconnects to the pool.

+ There is now a Cache directory where the miner creates cached versions of OpenCL kernels

+ Some reported miner crash after multiple pool disconnect/reconnects , not able to log in etc.. I hope i found the cause of it and fixed it

+ Learned from the previous big mistake with devfee pools hardcoded in the miner, now miner gets the list of devfee pools from http://srbminer.com, so please allow/don't block it on your firewall

wow many thanks dok, will try now mining on nicehash with max_difficulty.

ok, and report is it working like it should
You can define max_difficulty for every pool like :

{"pool" : "lotsofcoinspool1", "wallet" : "", "password" : "x", "max_difficulty" : 150000},
{"pool" : "lotsofcoinspool2", "wallet" : "", "password" : "x", "max_difficulty" : 400000}

yes I already define max_difficulty, will monitoring for a while.
just to let you know I can confirm hash rate drop after reconnecting to pool for RX Vega.

SRBMiner 1.5.9 AMD Driver 18.5.2.

First running.
https://imgur.com/a/pVgDVlp

After reconnect because of network error.
https://imgur.com/a/g4GC6xz

Edit :
Reconnecting due to high diff work perfectly.
https://imgur.com/a/8icbdsL

Bro, in my case, after reconnecting, the hashrate was drop. But after waiting a few minutes, it's back normal.
May be you were too quick to observe?

I checked now, after more than 7 hours my hash rate still drop from initial running.

[Elder III]

Well, I tried opening GPUZ while the miner was running just now and I can confirm that I did get a boost of ~50-60 Mhz per GPU. That's with 6 x Rx 580 8GB, 5 Micron Memory, 1 Hynix Memory - all stock Bios - 1250 Core, 2150 Memory, 925 mv Core,  950 mv Memory 18.5.1 drivers.