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

[a1ternative]

Why? Already tried,and different versions,from diff locations,but got message "SRBminer already running  bla bla".Currently using claymore on v7 and srb for heavy.But I need 2 srb's .So how to implement this??

[ZaGunShow]

take of the commenting (/* and */)

Thank you so much.

Figured out autostart of Devcon.exe and the start.bat with the blockchain driver.
Hashing at 2060-2070 on Vega 64s.
Auto reboots on fail and up and running automatically within 2 min.  

Rockin!

(Now just to play with tweaks on individual cards for less crashing)

[Littlegrand]

good additional options:

- "0,1,2,3,4,5" etc turns off/on gpu during mining
- add to the "s" command current OC settings (this will be usfule when awesome Miner adds support, hope soon)
- "p" - to cycle trough pools list on the fly during mining



if i come up with something more interesting I'll let you know Smiley

Good job so far

Ohh I definately second the 0,1,2,3,4,5....I have 2 GPUs in one rig that I have to shut off and on for them to hash at max speed and with SBMiner it means stopping and starting the program over and over.



--J

[doktor83]

take of the commenting (/* and */)

Thank you so much.

Figured out autostart of Devcon.exe and the start.bat with the blockchain driver.
Hashing at 2060-2070 on Vega 64s.
Auto reboots on fail and up and running automatically within 2 min.  

Rockin!

(Now just to play with tweaks on individual cards for less crashing)

does that means no hashrate drop on  vega?
Could you share a short how-to-do-it so other Vega users can set it up too ?

[goodminer]

Can someone give me an example of commands for simple bat file, this is too complicate with separate files config, pools etc...
Can we use single bat file to run this miner, like with Claymore for example?

why is it complicated ?

config.txt :

{
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"target_temperature" : 0,
}

pools.txt :

{
"pools" :
[
   {"pool_use_tls" : true, "pool" : "pool-address", "wallet" : "wallet", "password" : "x", "location" : "europe"},
   {"pool_use_tls" : true, "pool" : "pool-address2", "wallet" : "wallet2", "password" : "x", "location" : "europe"}
]
}

Then just run start.bat and off you go.

Ok, thank you, any suggestion what is the best config for r7 370 card and rx 470? Which worksize and intensity for all algos?
I tried cryptonightv7 with my r7 370 and max is 455 h/s, but my gpu is pretty freezing even if I lower intensity under default one.
How to set up other configs and pools for other coins and order miner to mine on it? I tried just like you said in description, but can't start miner, it said that can't start txt file.

[heavyarms1912]

Why? Already tried,and different versions,from diff locations,but got message "SRBminer already running  bla bla".Currently using claymore on v7 and srb for heavy.But I need 2 srb's .So how to implement this??

tried changing name of .exe file?

[R0land]

Why? Already tried,and different versions,from diff locations,but got message "SRBminer already running  bla bla".Currently using claymore on v7 and srb for heavy.But I need 2 srb's .So how to implement this??

You can start the miner with:

SRBMiner-CN.exe -c config.txt

write it to a .bat-file and start it.

[CryptoPlay]

take of the commenting (/* and */)

Thank you so much.

Figured out autostart of Devcon.exe and the start.bat with the blockchain driver.
Hashing at 2060-2070 on Vega 64s.
Auto reboots on fail and up and running automatically within 2 min.  

Rockin!

(Now just to play with tweaks on individual cards for less crashing)

Can you share your config please?
What are u using to auto re start?

[tenmoi]

Hi all,

What is worksize? I read it’s the local gpu thread, but how many of these are there in an rx 570?

Thank you.

[bovineplane]

For those running Vega.  Below are some of my settings a hashrates. These are on a reference 56 running 950 mem, non soft table mods. Stock bios on the newest drivers - non-blockchain.

All below running V1 on Stellite.

Intensity/thread/worksize/hash

118/2/8/1863
119/2/8/1859
120/2/8/1888
109/2/16/1869
109.5/2/16/1892
110/2/16/1893
110.5/2/16/1932
111/2/16/1890
109.5/2/20/1851
92/2/20/1731
100/2/24/1793
105/2/24/1814
110/2/24/1832
115/2/24/1857
120/2/24/1892  *Locked Win - hard reset required after a few minutes then had to uninstall drivers and cards then re-install*

Appears worksize 16 was the sweetspot. Someone with modded cards running higher clockspeeds give it a run and post some results.

[typerc]

For those running Vega.  Below are some of my settings a hashrates. These are on a reference 56 running 950 mem, non soft table mods. Stock bios on the newest drivers - non-blockchain.

All below running V1 on Stellite.

Intensity/thread/worksize/hash

118/2/8/1863
119/2/8/1859
120/2/8/1888
109/2/16/1869
109.5/2/16/1892
110/2/16/1893
110.5/2/16/1932
111/2/16/1890
109.5/2/20/1851
92/2/20/1731
100/2/24/1793
105/2/24/1814
110/2/24/1832
115/2/24/1857
120/2/24/1892  *Locked Win - hard reset required after a few minutes then had to uninstall drivers and cards then re-install*

Appears worksize 16 was the sweetspot. Someone with modded cards running higher clockspeeds give it a run and post some results.

hmmm... I'll have to do some more testing... after seeing this...

I'm running stock bios XFX RX Vega 56 cards GPU 1407/950 MEM 925/900 with 85% pp tables running 6 cards pulling 1140-1160watts from the wall. Also running latest AMD Adrenalin 18.3.4 drivers.

112/2/16/1886 <--stable running V1 on Electroneum

If I turn the memory up to 950MHz then I can get into the 1920-1940 h/s but its not stable for all the cards. Now with the latest version and the logging is improved I should be able to narrow down the card or cards that are giving me issues.

[inv1s1bl3]

Already mining 24hrs+, the local results are 4.4kh/s, and by the pool i'm getting 4.8-5.2! Really incredible miner, thanks 

[a1ternative]

tried changing name of .exe file?

Oh.Thanks,thats works!

[tenmoi]

After 7 hours I’ve got 9 hw errors and 17 block expires on nanopool. Is this normal? What’s most worrying are those hw errors. HWinfo reports no errors, though. Really appreciate your opinions.

[doktor83]

Who's got a hd 6950 and can test something for me?

[doktor83]

After 7 hours I’ve got 9 hw errors and 17 block expires on nanopool. Is this normal? What’s most worrying are those hw errors. HWinfo reports no errors, though. Really appreciate your opinions.

expired block means the share you sent got old because the block expired in the meantime.
Hw error means gpu result did not pass cpu validation. So if you want try lowering intensity, or mem clock for ex.

[tenmoi]

After 7 hours I’ve got 9 hw errors and 17 block expires on nanopool. Is this normal? What’s most worrying are those hw errors. HWinfo reports no errors, though. Really appreciate your opinions.

Hw error means gpu result did not pass cpu validation. So if you want try lowering intensity, or mem clock for ex.

So this means the shares were wasted and not sent to the pool? My local hashrate is 5057 and the pool reports the average hashrates between 4990 and greater than 5000. Is this ok so I can ignore the hw errors by srbminer?

THank you.

[JuanHungLo]

doktor83,

Very nice work.  I can confirm that 110.5 is the optimal intensity for Vega 56 reference air cards at this point using Blockchain drivers.

I can now confirm that your miner is beating the latest XMR-Stak stellitequestion-compiled-0 miner with better temperature and hashrate, not by much, but still better.

The only thing keeping me from full utilization is the API send for remote monitoring.  I know you are working on it and I anxiously await it.

[popow_sergei]

doktor83,

Very nice work.  I can confirm that 110.5 is the optimal intensity for Vega 56 reference air cards at this point using Blockchain drivers.

intensity 120 for Vega 56 reference

[d2bg]

Could we have an option to keep our pools list in our config file like before? ie, if no pools file look in config file?  I usually keep a long list of configs for easily switching between cryptos depending on the difficulty, and it's helpful to keep all info in one file.