|
V1.5.6
- Added support for Cryptonight B2N
- Added parameter "min_rig_speed" in config file
- Added parameter "main_pool_reconnect" in config file
- Added optional parameter --resetfans in .bat
- "shutdown_temperature" parameter now must be set to a value > 0 to get activated
- Added 1 min avg hashrate display
- Fixed a bug in watchdog restarting process
- Added support for CPU builtin OpenCL GPU (just for fun)
+ Cryptonight B2N is for Bitcoin2Network coin
+ "min_rig_speed" parameter defines the average hashrate we want to maintain. If 5 min average hashrate is less than the value we defined, restart miner. This option expects you to enter a value in H/S
+ "main_pool_reconnect" minimum value is 180 seconds (3 min), defines how often should miner try to reconnect back to main pool if not mining on it currently. If not set default value is 10 minutes.
It is activated only when it can't connect to main pool from the reconnecting process, so if user changes pool by pressing P, it won't try to connect back to main pool, because user changed the pool himself.
+ Removed auto fan reset on miner exit and put new parameter in bat : --resetfans, which if used resets fans to default settings on miner exit
+ CPU builtin OpenCL GPU
Tested and works on Intel HD 3000 builtin GPU
If user wants to use it has to put --usecpuopencl in bat, and define cpu_conf in config:
"cpu_conf":
[
{ "intensity" : 1, "worksize" : 1, "threads" : 1}
]
you can use "platform" : number , if not used, autodetected
This option is here more mostly for fun, as it hashes slower than a CPU miner would.
The OpenCL kernel is totally unoptimised, so maybe in the future if i get very motivated, i will look into speeding it up, if it's achiveable.
But hey, it's available, you can use it if you want
Tested and works on Intel HD 3000 builtin GPU
|
|
|
|
@doktor83, today I saw this: [2018-05-29 12:00:03] Connected to devfee pool
[2018-05-29 12:00:08] Pool sent a new job (ID: 8286)
[2018-05-29 12:00:51] Pool sent a new job (ID: 8287)
[2018-05-29 12:01:10] Could not login to devfee pool
[2018-05-29 12:01:10] Now mining for user I have no blocking rules, so you should possibly check your devfee credentials in source could you tell me which algo is this? |
|
|
|
V1.5.5 (read more)- No need for all that stuff in start.bat anymore, because watchdog can now restart the whole miner process without it - Fixed kernels 3 & 4 for heavy algo - Fixed OCL binary caching for Vega cards - Added last job received info in stats and API - Added 'job_timeout' parameter to pools config, it reconnects to pool if no job received for 'job_timeout' time (in seconds), default is 5 min - Pool reload now checks if current pool is first in reloaded pools list, if not, it switches to first pool Found a bug. Watchdog was unable to restart the miner when GPU hung up. Error returned was could not find file - was clear it couldn't handle a space in a folder name in the path to SRBMiner-CN.exe May want to either encapsulate the path or use the 8.3 folder name. I moved it into folder with no spaces, but means won't restart if put it in Program Files or anywhere else with a space. true, thanks for the report, i will fix it. |
|
|
|
Very nice, thanks for this  |
|
|
|
information is gold. Reading this thread you get information.  Some people would still miss it, but this could be in the original post: "Some users report higher hash-rates with RX580's on CN-Heavy algorithm when running GPU-Z in the background. Mileage may vary." I will put this right away in the tips section on first page  |
|
|
|
information is gold. Reading this thread you get information. |
|
|
|
Hi Doc!
any news about the known hashrate drop in heavy?
no news, i did not look into it as it can be easily fixed with gpu-z |
|
|
|
my rig have a strange pattern, every 48 hours nontsop mining will get 90 Celcius shutdown , while my GPU not showing any burned effect , anyone know how to fixed this ?
i'm using SRB latest version.
had same issue when running SRB 1.5.1 on windows 1803 update. So when i rollback to 1709 windows 10, everything look fine.
So, if you updated to 1803 probably that's causing the problem, or worse if your gpu's are really getting to 90c. By default if not set "shutdown_temperature", is set to 90c. I will just disable this default setup, so if "shutdown_temperature" is not explicitly set in config, it wont be enabled and no more problems on 1803. |
|
|
|
Good afternoon! Tell me who can know? Installed 56 Vega. When the farm is connected to the monitor, the miner works. When I unplug and restart without a monitor with TEAMWiever produces such an error. What could it be?   first try lowering intensity |
|
|
|
Hello, I have the problem in between, the miner complained that he overheated and then want to restart. then the mining rig crashes. I have 5 Vega 64 in the rig and use version 1.5.5.1, do you have an idea? What's weird is that I have a second rig with 3 x Vega 64 and this is crashes at the same time. Sometimes the whole works without problems 3 days...
does it say "critical shutdown, temperature reach 90C" ?? i had same issue when running SRB 1.5.1 on windows 1803 update. So when i rollback to 1709 windows 10, everything look fine. have you checked, maybe it really reached 90c ?  |
|
|
|
Hey Doctor
is it possible to do that miner show error messages in friendly english coding system and not depend on which one of languages of OS i use ?
All other miners don't have that problem, it's hard to do that?
miner shows its own messages on english, but its works with some windows components (like ws2_32.dll) which return those messages. |
|
|
|
hi guys im using 1.5.3 srb
i still cant get set how to turn off auto fan
if i start mining it will always set auto
any help?
many thanks
what do you want to do ? Set fan speed ? yes im setting with msi ab but if i start srb it always set fan to auto in msi? do we have an option to set auto fan = false? hi doc, any clue?? thanks If you have set any of these, miner will take over control of fans : - target_temperature - target_fan_speed |
|
|
|
Maybe your RX470 have Samsung memory which allow for Hs rates above 1000 without many tricks. My RX580, they have hynix memory, which works well for Ethereum mining but not as well for Cryptonight mining.
Anyway I am not giving up on SRB, it is just that it seems it needs more parameters than Cast and that it is a long learning curve.
Cheers.
i never used cast, but looking at the parameters, how does one set intensity and stuff like that? I don't see any option for tuning or optimisation? |
|
|
|
Hello Doc,
Thank you for the wonderful miner.
I've upgraded two of my Vega64 rigs from 8 to 10 cards per rig, and had to ditch the blockchain driver in order to support 10 cards.
With the new driver xmr-stak is not performing so well as with the blockchain driver, and I made a test between xmr-stak, cast-xmr and srb.
The results are excellent in favor of the SRB:
10 x Vega64 1408/950 GPU & 1100/950 MEM:
srb miner - 20100 h/s - 0.85% fee = 19930 total
xmr-stak - 19454 h/s - 0% fee (I'm compiling my version with the dev fee removed, as 2% default is a bit high) = 19454 total
cast-xmr - 19900 h/s - 1.5% fee = 19600 total
Also from the 3 miners only SRB continued to mine with 1 card crashed (with 9 of 10 cards), and the bus ID reorder made it very easily to find which card is this and to tune its mem down a bit.
So I want to thank you and congratulate you for the excellent miner. You also have a very reasonable dev fee so I'm planning to deploy the miner on all of my rigs.
I have the following feature request, that I will be very happy, if it could be addressed.
Is it possible to add a pool priority (xmr stak has this option) so if the primary pool fails and the miner switches to the secondary pool, the miner to start to mine to the primary pool again when it's up again?
Easy walkaround could be if that's hard to implement, to enable a scheduled pool reload (at this moment at the reload, the miner connects to the primary pool if it's not connected).
Regards
Hi and thank you for the kind words The feature you want is on the wishlist and soon it will be implemented, possibly in the next version. |
|
|
|
why do you guys use SRB miner instead of CAST?
SRB does not offer any performance advantage, it is more complicate to set up and actually performance is very erratical, since any time you restart it, you may get a different hash rate, at least for me.
I have been using it for a couple of days on 2 rigs one with Vegas and the other with RX580 and I could not find any plus VS Cast.
Just wondering if I am missing something.
im curious, which part is complicated to set up? |
|
|
|
can you explain with english words what do you want to say, cause i still can't read minds ? |
|
|
|
hi guys im using 1.5.3 srb
i still cant get set how to turn off auto fan
if i start mining it will always set auto
any help?
many thanks
what do you want to do ? Set fan speed ? |
|
|
|
Soon algo changes every month  |
|
|
|
|
V1.5.5.1
- Just a quick fix of 1.5.5 new 'job_timeout' option. Looks like the default 5 minute wasn't enough, so its increased to 15 minutes now
|
|
|
|
|
Show Posts
