Hello, one question: i do not check  how to disable some GPUs in cmdline setup i used, e.g --cgpuid 2,3 for disable GPU 0 and 1, but again miner takes all 4 GPUs, - when miner is running, i can disable GPUs with numbers without any problem. But i need to disable it in cmdline. what did i make wrong??? thx for help I just tested on v1.8.8 this and it works, uses only those gpu's : SRBMiner-CN.exe --ccryptonighttype turtle --cpool POOL --cwallet WALLET --cgpuid 2,3,4 --cgputhreads 2,2,2 --cgpuintensity 0,0,0 --cgpuworksize 8,8,8
Show me how are you setting up things. Hello,
when I start the miner I get these settings:
GPU0: Radeon RX 580 Series [ellesmere] [8192 MB][I: 107.0][W: 8][T: 2][F: 4][BUS: 1]
GPU1: Radeon RX 580 Series [ellesmere] [8192 MB][I: 107.0][W: 8][T: 2][F: 4][BUS: 2]
GPU2: Radeon RX 580 Series [ellesmere] [8192 MB][I: 107.0][W: 8][T: 2][F: 4][BUS: 3]
GPU3: Radeon RX 580 Series [ellesmere] [8192 MB][I: 107.0][W: 8][T: 2][F: 4][BUS: 5]
GPU4: Radeon RX 580 Series [ellesmere] [8192 MB][I: 107.0][W: 8][T: 2][F: 4][BUS: 6]
GPU5: Radeon RX 580 Series [ellesmere] [8192 MB][I: 107.0][W: 8][T: 2][F: 4][BUS: 7]
GPU6: Radeon RX 580 Series [ellesmere] [4096 MB][I: 105.0][W: 8][T: 2][F: 4][BUS: 9]
But in the config I have Intensity 0 and no Fragment set at all !
Are these an optimal config for my cards or are overridden by the config file ?
thx
When you set intensity to 0 it means miner automatically sets everything for you (intensity, worksize,fragments). I've just upgraded from V 1.8.5 to V 1.8.8. The new version is completely unstable and crashes the computer on a regular basis. Sometimes is crashes itself.
Will need to revert.
If you are not using the auto settings, check that your gpu id's are set ok, because 1.8.8 uses different gpu ordering (by bus id). You can run --listdevices to see the which gpu is which id. From the release notes for 188: + The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed.
NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!
|
|
|
|
I can't figure out why sometimes (usually?) the tweaking profile doesn't apply when set from the command line. Nothing in the log I can see. It just says tweaking enabled like usual.
I can always hit +/- to manually set the tweak in this case. I'm launching from awesome miner service (run as administrator). Can you put some extra logging to figure this out?
Next version will contain a little more info about tweaking in the log. Have you tested the cmd line launch without using awesome miner ? I mean, just making a .bat and running directly SRB with the same parameters. Hello,
I have never been able to get any version / driver combination completely stable for my single Vega 56 (1450/935 MHz, 925/925 mV).
Also playing around with voltages and freqs could not prevent the occassional crash.
Now I'm using 1.8.8 on 18.6.1, and besides crashing it also usually drops to half the hash rate.
It is my only GPU so I have three monitors connected, does that cause any of this perhaps?
Does anyone have a suggestion to solve it?
Thanks!
Using multiple displays + using the computer + mining all at the same time, can get you crashes. Hello doktor,
I have the same problem with EIO.dll as livada on one of my rigs, the other rigs are working fine.
When I stop the miner, disable the auto run of it, and restart the rig I'm still unable to run WinAMDTweak.
Please advise if I can perform any testing/debug steps in order to assist you to debug the issue.
Regards
I don't know what to tell you more, you read everything so you know that you should disable tweaking in SRB if using an external tweaker. Hi, doktor83. And yet another bug. On my second rig. Miner work but on which pool? Please, see log https://pastebin.com/pUA5zmZMI think this the same bug but with different effects. Still investigating  |
|
|
|
Thanks for reporting, i see what is happening, but don't get it why it is happening, going to investigate. I see you got fixed the duplicate BUS ID's, what did solve it ? |
|
|
|
i try send PM but ypou block mesage and i must send this... You block AMD mem TWEAK forever with 1.8.8? After start srbminer 1.8.8 AMD mem TWEAK not work. restart not solved this . ALways say EIO error. Any sugest or i must reinstal windows if use 1.8.8 version? 1.8.7 and 1.8.6 block AMD tweak but after restart all work. Now 1.8.8 block AMD tweak forever  WTF It does not 'block forever', if miner is not running nothing is 'blocked'. Restart solves everything. Use --disabletweaking as i told many times and use ElioVP's tool. Don't mix and you are good. read my post. after start 1.8.8 AMD tweak block forever. Now i not start AMD tweak. afterr restart AMD not work. you block this forever. this is big prbolem now . Now i must reinstal Win? howe you block this? give me any soluton for unblock EIO.dll. you block in registry? not in memory. if block only in memopry after restart amd must work. i not tell not work in SRBMINER aMD not work with cli mode gui mode or any miner after 1.8.8 start. block FOREVER And i understud why you block AMD tweak befoe start but not understud why you not UNBLOCK AMD tweak after close srb miner? Im tired of this, and dont have anything else to add. You are wrong, its not 'blocking forever'. Tested on few rigs + got a few guys test it for me. After restart all good. I know you will continue your rage, but i wont react to it anymore, dont want to repeat myself 100x times again. |
|
|
|
i try send PM but ypou block mesage and i must send this... You block AMD mem TWEAK forever with 1.8.8? After start srbminer 1.8.8 AMD mem TWEAK not work. restart not solved this . ALways say EIO error. Any sugest or i must reinstal windows if use 1.8.8 version? 1.8.7 and 1.8.6 block AMD tweak but after restart all work. Now 1.8.8 block AMD tweak forever WTF It does not 'block forever', if miner is not running nothing is 'blocked'. Restart solves everything. Use --disabletweaking as i told many times and use ElioVP's tool. Don't mix and you are good. |
|
|
|
[2019-05-11 22:47:31] GPU0: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 1]
[2019-05-11 22:47:31] GPU1: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 1]
[2019-05-11 22:47:31] GPU2: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 5]
[2019-05-11 22:47:31] GPU3: Radeon RX 560 Series [baffin] [2048 MB][I: 26.0][W: 32][T: 2][F: 8][BUS: 5]
Something is messed up, gpu's have same bus id's, and that shouldn't happen. Driver is reporting it bad. Try to DDU & reinstall video drivers. Or if using the duplicateid parameter disable it |
|
|
|
anyone knows why my computer uses a tweak a few moments later, often sight out and black screen....help me doc Its hard to help if you dont provide any information |
|
|
|
1) Precompiling program BUS.....
Finished program precompilation BUS...
....infinitely............
2)When the miner starts, it displays a message
Error: Description = Invalid query
What does this mean?
Can you upload a logfile somewhere? |
|
|
|
Hello, does anyone know the difference b/w ‘normalv4_64‘ and ‘normalv4’ algos?
normalv4 = CN/R normalv4_64 not in use atm |
|
|
|
you suggest changing the intensity?
No, i suggest reading the 1.8.8 release notes No more --gpureorder, device ordering by bus id is now the default/only display mode [NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!]
oh you mean setup the config file as this examples shows. I mean your device id's changed and are now ordered by busid, so what was id 3 is now maybe id 2, you should identify your devices with --listdevices , and edit your config according to those device id's. |
|
|
|
you suggest changing the intensity?
No, i suggest reading the 1.8.8 release notes No more --gpureorder, device ordering by bus id is now the default/only display mode [NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!]
|
|
|
|
V1.8.8- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad - User is now informed about tweaking status on the screen too, not just in log - No more --gpureorder, device ordering by bus id is now the default/only display mode - Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger - min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter - Fixed a few cosmetical things on web stats + If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%. This also brings a small hashrate increase for RX cards on UPX2 as a side effect + The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed. + Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger. The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5). 5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action. min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec. Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart. hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting) Im running into the same issue. what did you do to fix? Read back a few posts |
|
|
|
Hello, anyone know why I’m seeing this message (in light grey) after the miner been running for a while (not just right after startup)? “Precompiling program [Bus...” “Program finished precompiling [Bus...” Win10 / Vega64 / v1.8.8 / Monero Its all good, just thar from 1.8.8 user can see these messages, before it wasnt displayed. |
|
|
|
For the life of me, I cannot get 1.8.8 to run on any algo.... Whenever I hit H or S, I get nothing... Very slow response times... Compute Errors and GPU Crashes. I've tried on CN-GPU and CN-HOSP.
I'm using command line to run the miner, as I always have... Did something change here that I missed? 1.8.6 runs fine.
--ccryptonighttype hospital --cpool [Server]:[Port] --cwallet [User] --cpassword [Password] --apienable
Which gpu's and driver? |
|
|
|
Swap the intensities in 1.8.8 in gpu_conf, so : id:1 = intensity 112 id:0 = intensity 122 You should be all back to normal Check the post above yours |
|
|
|
hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting)
This is interesting, yes, because on vega56 i do the testings, and nothing changed as you say. Are you running the --resetvega parameter ? Also the same ODT as before? Can you test it a few times, just to be sure that there is really a change in hashrate, because there shouldnt be... I have an issue, my computer cashes because now SRB tries to use the Vega cores inside the Ryzen 2400G to mine, how could I disable the APU in your miner ?
Thanks
By now, you mean from v1.8.8 ? The ordering of the devices changed - they are now ordered by bus id so it is the same order as in ODT. Run SRBMiner-CN.exe --listdevices in cmd and set device id's you use according to that |
|
|
|
V1.8.8- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad - User is now informed about tweaking status on the screen too, not just in log - No more --gpureorder, device ordering by bus id is now the default/only display mode - Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger - min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter - Fixed a few cosmetical things on web stats + If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%. This also brings a small hashrate increase for RX cards on UPX2 as a side effect + The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed. NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!+ Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger. The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5). 5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action. min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec. Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart.
|
|
|
|
As I'm running stock bios for my RX cards on XMR dude, any enhancements would be appreciated that you've found this far. It'll help me (and others) see where to be begin with tweaking their own Polaris set up. Finally, does this tool work in conjunction with srb miner?
It does, you just have to use the --disabletweaking parameter, to disable the built-in tweaking. |
|
|
|
How do I enable tweaking on my VII... eavery time i start miner it sais tweaking: disabled
Run as admin, its in the readme I did. it still shows disabled Are you running version 1.8.7 ? If so, look at the log file at the beginning theres more info why is tweaking disabled, if not running 1.8.7 then thats the problem |
|
|
|
How do I enable tweaking on my VII... eavery time i start miner it sais tweaking: disabled
Run as admin, its in the readme |
|
|
|
|
Show Posts
