V1.4.1- Added optional parameter reboot_script which if defined disables built in watchdog, and runs a user defined script Ok guys, another option you wished for is added now  You can disable the built in watchdog if it's not working for you, and run a .bat instead on GPU crash. Put the parameter "reboot_script" : "scriptname.bat" in the config file, or just use the .bat i provided (reboot-windows.bat), which restarts your machine.
|
|
|
|
can you try to move the intensity from 32 to for ex 33 and see what happens ?  SRBMiner-CN-V1-4-0 - 835h/s, 1xRX480 Everything other than intensity 32 has lesser results !!! No problem 50, 100, 200h/s difference! Oddly, it is that with the newer versions it produces weaker results. Greetings and thanks to the wonderful work you do @doktor83.  i double checked and nothing has changed from v1.3.1 that should have impact on manually set parameters. I did some changes to auto configure tho. Can you please try 32.5 intensity thanks for your support it means a lot to me. |
|
|
|
|
ATTENTION!
Do not download miner from this link :
https ://github.com/Mainergrud/SRBMiner
I don't know what this is, always download from the link in the first post!
|
|
|
|
can you try to move the intensity from 32 to for ex 33 and see what happens ? |
|
|
|
|
V1.4.0
- Added multiple pools support (failover pools)
- Added GPU crash display & logging back again
- Some minor bug fixes
Every pool now must be defined in a separate pools file.
The logic is simple, if it can't connect to first specified pool, after 2 retries it goes to the second one, and so on.. When reached the last pool, it goes back to the first one.
You can set the number of retries in config.txt adding the "giveup_limit" parameter.
At the moment there is no option to use pools with algo other then the one specified in the config file.
|
|
|
|
but i have 2 rigs. rig 1 is not affected. only rig 2. here are my specs:
rig 1:
sap rx 570 nitro+ 4gb (samsung)
rig 2:
powercolor rx 570 red devil 4gb (hynix&elpida)
Now that is really strange, both cards are 570 4g, i will check what is happening. Regarding hw errors, that means the result GPU returned could not be validated on the CPU, because it's wrong. If you have a few errors don't worry, but if you got a lot i would start with lowering intensity. Intensity can be a decimal number, so for example if you now use 35, you can try 34.5. If not satisfying then 34 and so on. |
|
|
|
Hello doktor,
My hashrate still drops with vega 64, even with 100% fan config in afterburner (8500 to 6000h/s for 6 gpu) after few minutes.
Do you think it is better to use overdrive for this or it will change nothing?
Is it a driver problem? I have Amd Crimson 016.001.001.000 , should i change?
Last question: i can set my mem clock to 1100 max, after this, it reboot my computer, is there a way to go higher, or will it change nothing?
Thanks a lot for your help!
I don't have Vega cards but i found on many many places on the net that vegas hashrate drops, so its not a miner related problem. Maybe someone here who has Vega cards can help you ? |
|
|
|
post your 1.3.1 conf , and 1.3.2 conf here please nothing was done in new version regarding hashing speeds, only some re-work of auto intensity settings. I had to lower a little bit auto settings cause lot of users get false-good intensity value and crashing. So you just need to increase the auto intensity value you get and insert that value instead 0 in the config file.  im on a manual gpu conf before and after the latest update. latest update reduced speed. i dont understand neither. i will check it then. Which algo? Heavy? |
|
|
|
|
i still need that log file to help you
|
|
|
|
|
ok, now --listdevices please
|
|
|
|
Excuse me,noob question. where to put "--logfile filename"? this is my bat file. @echo off
cls
SETLOCAL EnableExtensions
set EXE=SRBMiner-CN.exe
:START
FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto RUNNING
%EXE% -c config.txt --logfile log.txt
TIMEOUT /T 5 /NOBREAK
goto START
:RUNNING
echo "%EXE% is already running"
pause I bolded it for you |
|
|
|
post your 1.3.1 conf , and 1.3.2 conf here please nothing was done in new version regarding hashing speeds, only some re-work of auto intensity settings. I had to lower a little bit auto settings cause lot of users get false-good intensity value and crashing. So you just need to increase the auto intensity value you get and insert that value instead 0 in the config file. |
|
|
|
Hi doktor83. your miner work very well, but Could you please add options to restart a computer instead of restart miner? Because my computer is freeze every time the miner try to restart itself. I have to push the start button to reboot my computer every time if freeze. Thank you. could you try latest version 1.3.2 and clarify that it still hangs on restarting? Also why dont you lower your intensity a little bit so your gpus wont hang? |
|
|
|
Doktor, can you please add support for worker name and email address. Without an email address I can’t change my minimum payout (nanopool)
Thank you.
Here is the format for nanopool. WalletAddress.WorkerName/Email Tks. It works. @doktor. The miner reports open CL 2.0. I wonder why you didn't use 3.0. no gains? it reports the version of opencl your hardware supports |
|
|
|
|
WHY VEGA HASHRATE DROPS AFTER SOME TIME?
Vega's throttle because of flaky drivers. They will throttle themselves if the memory on the cards (HBM) get's too hot.
Until i add an option to set fan RPM you can use OverdriveNTool to set the min fan speed to 3000rpm for example that should keep the card cool enough.
|
|
|
|
|
guys with devfee problem, download 1.3.2 and turn on logging, so if it hangs again we can get more info on what happened so i can fix it.
Also speed for auto is now a little lower on some cards, but if that is the case with you just set it manually and you will get the same speeds as on v 1.3.1
Worker name is pool related, you put it in wallet parameter, but the format is not same on every pool, check it on the pool they have written this info on their site.
|
|
|
|
Hi
when i try to just one gpu:
"gpu_conf" :
[
{ "id" : 3, "intensity" : 120, "worksize" : 16, "threads" : 2},
]
}
i get an error this error:
Error CL_INVALID_DEVICE when calling clCreateContext
however if i run all 4..it works. can you please assist me on getting one gpu only to mine?
thanks
Hi , can you download latest version and try? It should be fixed |
|
|
|
I'm tested 1.3.2 update. For 8Gb Polaris hashrate remained at the same level - 1100 h/s. 4GB Polaris lost performance -725 h/s against 762 h/s in 1.3.1. 4Gb Hawaii productive same level - 670-690 h/s.
Nothing is lost, i just lowered auto setup values a little bit, you can set intensity by hand and you will be back again at the same speeds. |
|
|
|
|
V1.3.2
- Cryptonight UltraHeavy algo updated
- Miner restarting on crash should now work in most cases
- Added detailed device listing with --listdevices parameter
- Added detailed logging, use --logfile filename, log option removed from config.txt
- Hopefully fixed bug when in 'gpu_conf' you want to set only one GPU
- Fixed temperature and rpm display
So you guys still having problems can now enable detailed logging, you have to use parameter --logfile filename, in bat.
I removed log option from config file.
Also please report if you can use 1 gpu now in 'gpu_conf', i think i fixed that one.
|
|
|
|
is there known bug that every 2 gpus showing the same temperature and fan speed?
you may be right, i will check it |
|
|
|
|
Show Posts
