|
Doktor, kudos on your fabulous miner and keep up the great work!
Question, is there a way to see which particular GPU found results/shares?
|
|
|
|
Played with "fragments" setting, the default from compiled kernel was 4. Found 16 gives best hashrate for my rx560 2gb cards. Tiny ~4 H/s gain. Will try to squeeze something from bralock soon, might take hours of testing  |
|
|
|
... - Run 18.6.1 for less power consumption or 18.5.1 for higher hashrate (marginal differences both).
- Use MSI AB to "extend official overclock limits." Q: are you using MSI AB or ODT to control the fans? I greatly prefer using AB to set a custom fan curve.
- Bump up PL in AB to +5%
- Use ODT 0.2.5 to set highest P state for core/mem clock/voltage, trying 1180MHz/895mV for core and 2000-2100MHz for mem. Q: What about memory voltage?
- Set intensity manually in SRB try 23 to 24 initially. Q: What about worksize? SRB is setting it to 32 automatically (also, double threads true and K auto set to 1).
And that should bring my power consumption down to around 40W per card with a slight boost to hashrate, correct? Depending on what brand 560's you have, they may not be able to go down to 40W and retain 450 h/s, it all depends on how well they can undervolt. I think it's impossible with the 18.5.1 drivers you must use 18.6.1 or no dice. For me 18.5.1 read 40w on gpu-z if I had tested on the wall I'm sure it would actually be 44-45w. 18.6.1 read 36w on gpu-z and goes no higher than 39.5w on the wall for me. The tiny ~5 H/s gain on 18.5.1 is definitely not worth the higher power draw. If you're desperate for lower undervolt you could try lower core clock than 1180, but at this point every step down is negative for hashrate. I just use ODT at fixed fan speeds, my 6x rx560 2gb rig is in my bedroom so I try to keep it quiet like 1600 rpm, as long as my cards stay 65C or under it's okay. On v7 I got max hashrate with -10% power limit. On v8 I have to increase to +10% for max hashrate. PL doesn't really effect consumption, the core voltage effects it most. On v8, my 560's need 865 mV on mem voltage to be 100% stable, at 860 mV they can crash or lose hashrate after many hours. I had it on 860 mV before because it was stable with older v7, so v8 needed +5 mV. Try 8 worksize first and then 12/16 and see if it improves hashrate, doesn't make sense for a 2gb card to go any higher than 16. Holy cannolis did I make myself a metric craptonne of work for myself yesterday. In directly violation of the scientific method - change one variable at a time - I DDU'ed 18.5.1 and installed 18.6.1, then moved the RX 570 from my main desktop over to my 4x RX 560 mining rig, then proceeded to spend the next 4 hours trying to get the mining rig to not crash running either SRB or xmr-stak. I finally gave up on the RX 570 but it wasn't a totally wasted effort: now I am getting 1840H/s out of the 4x RX 560 rig at the same 355W total from the wall (55W actual per GPU) running 18.6.1 and manually setting worksize to 8 (but letting SRB set the intensity, and still with double threads true). And of course this morning I see there is a new version of SRB out, but I am too shell-shocked from yesterday to even contemplate messing around with this today. Oh, and I didn't even get to the point of trying to tweak voltages with ODT; the miner needs to run for more than a few seconds to bother with that kind of optimization. At any rate, thanks for help! Awesome hashrate but still, that's disappointing power consumption. The fact that you can't get the 570 stable suggests an issue with the rig outside of software. Only other thing to try is a different motherboard/PSU or your 560's are just plain power hogs. From experience the best AMD vendors are MSI and Gigabyte, usually have best asic quality and good undervolt results with them. Sapphire is a mixed bag. The worst are PowerColor and XFX, they always seem to use cheap reference design and struggle with undervolt. |
|
|
|
|
Good times, XMR mining the best it's been in a while, hopefully the difficulty can keep under 60G for longer.
Anyone know if AMD is gonna eventually cannibalize Polaris 30 and give us a low power/no-power connector option like the rx550/560?
|
|
|
|
...
At any rate, my 4 cards are consistently doing 460, 420, 420, 460 and using an estimated 54W each (based on Kill-A-Watt monitor, minus the amount used by the system when not mining) and 1200 Core / 1900 Mem and -20% on the power limit, so you are totally kicking my ass in power consumption vs. hashrate. Clearly I have some more tweaking to do but right now I am just happy I got it working stably on v8.
Were you disabling P0-P6 in ODT? You should. Just click each one to grey it out. Also ODT version 0.2.6 is very buggy for me, it has a problem setting core properly so i downgraded to 0.2.5 which works perfectly. What I do is enable "extend official overclock limits" in Afterburner, then from there I only use ODT 0.2.5, you have to do that or you get mem clock setting error in ODT. I also have ODT 0.2.5 installed (not currently using it, however), but I only had P0 and P1 greyed out in my custom CN profile. I'm feeling more adventurous now that things have been running well for a day, but before I start giving myself a migraine I want to clarify a few things you've done: - Run 18.6.1 for less power consumption or 18.5.1 for higher hashrate (marginal differences both).
- Use MSI AB to "extend official overclock limits." Q: are you using MSI AB or ODT to control the fans? I greatly prefer using AB to set a custom fan curve.
- Bump up PL in AB to +5%
- Use ODT 0.2.5 to set highest P state for core/mem clock/voltage, trying 1180MHz/895mV for core and 2000-2100MHz for mem. Q: What about memory voltage?
- Set intensity manually in SRB try 23 to 24 initially. Q: What about worksize? SRB is setting it to 32 automatically (also, double threads true and K auto set to 1).
And that should bring my power consumption down to around 40W per card with a slight boost to hashrate, correct? Depending on what brand 560's you have, they may not be able to go down to 40W and retain 450 h/s, it all depends on how well they can undervolt. I think it's impossible with the 18.5.1 drivers you must use 18.6.1 or no dice. For me 18.5.1 read 40w on gpu-z if I had tested on the wall I'm sure it would actually be 44-45w. 18.6.1 read 36w on gpu-z and goes no higher than 39.5w on the wall for me. The tiny ~5 H/s gain on 18.5.1 is definitely not worth the higher power draw. If you're desperate for lower undervolt you could try lower core clock than 1180, but at this point every step down is negative for hashrate. I just use ODT at fixed fan speeds, my 6x rx560 2gb rig is in my bedroom so I try to keep it quiet like 1600 rpm, as long as my cards stay 65C or under it's okay. On v7 I got max hashrate with -10% power limit. On v8 I have to increase to +10% for max hashrate. PL doesn't really effect consumption, the core voltage effects it most. On v8, my 560's need 865 mV on mem voltage to be 100% stable, at 860 mV they can crash or lose hashrate after many hours. I had it on 860 mV before because it was stable with older v7, so v8 needed +5 mV. Try 8 worksize first and then 12/16 and see if it improves hashrate, doesn't make sense for a 2gb card to go any higher than 16. |
|
|
|
...I much prefer to set intensity myself, however, so if anyone cares to share their settings for the 2GB RX 560 I'd appreciate it.
...
I have RX 560 2gb rig mining XMR. I use manual intensity, all cards needed lower intensity than the auto intensity. I recommend start at 26 and keep decreasing by 0.5 increment if not stable. Some of my cards had to go down to 24 and the lowest is 23.5 Core 1180@895mV/Mem 2000-2100, power limit +10% each card running 450-465 H/s and using ~36W with 18.6.1, the best driver for me. My cards needed +5 mV on the memory compared to v7. I tried 18.5.x it hashes a tiny bit more but uses more power ~40W v8 is more hungry for virtual memory, I have it set at 3x total vram. I also recommend using a reasonably low static difficulty with XMR, variable difficulty can get too high and cause stability/pool problems with weaker cards like the 560. Thanks for the reply - you got my last sMerit for it! After making that post I poked around the log file created by SRB and found the intensity it was setting for the cards: all are at 26.0. I was using OverDrivenTool to set all the clocks and voltages for each power state but I found it cumbersome and once MSI AB was able to deal with 3+ AMD cards again (ie - v4.5.0) I switched back to it. Unfortunately, I haven't been able to unlock core voltage adjustment yet, and as I recall that was another reason why I switched from AB to ODT. At any rate, my 4 cards are consistently doing 460, 420, 420, 460 and using an estimated 54W each (based on Kill-A-Watt monitor, minus the amount used by the system when not mining) and 1200 Core / 1900 Mem and -20% on the power limit, so you are totally kicking my ass in power consumption vs. hashrate. Clearly I have some more tweaking to do but right now I am just happy I got it working stably on v8. Were you disabling P0-P6 in ODT? You should. Just click each one to grey it out. Also ODT version 0.2.6 is very buggy for me, it has a problem setting core properly so i downgraded to 0.2.5 which works perfectly. What I do is enable "extend official overclock limits" in Afterburner, then from there I only use ODT 0.2.5, you have to do that or you get mem clock setting error in ODT. |
|
|
|
@playfast
I don't wanna be spiteful, but 450h@36W(at the wall) is barely possible.
As all polaris GPUs are 100% consistent in relative consumption it would mean an RX 570 can do 900 h/s at 72W but it can't. (or very rarely at least, 1 out of 100 cards maybe)
Did you measure it with killawatt or it's some 'calculated' or GPU-Z value?
I have msi 560 that came with hynix mem and later core steppings, 1050 mV at stock core clock 1196. They are great undervolters, doing 895 mV at 1180 on v8, they could do 885 mV with v7. gpuz reads a solid 36W, kill-a-watt doesn't go over 40W, bounces between 36-40W. They were doing 29-30W on v7, so power consumption went up around 20%. |
|
|
|
I've been using xmr-stak for about a year now, but I just switched over to SRBMiner on my 4x RX 560 rig because the former program is seriously buggy when set to CNv8. Hashrate is just slightly higher than xmr-stak - 1765H/s vs. 1735H/s (not accounting for lost time due to crashes, stuck cards, etc...) - and power consumption is just slightly lower - 355W vs. 375W - but this is letting SRBMiner pick the intensity (double threads set to true). I much prefer to set intensity myself, however, so if anyone cares to share their settings for the 2GB RX 560 I'd appreciate it.
FYI, I had to downgrade from Adrenalin 18.6.1 to 18.5.1 to get SRBMiner to work; prior to that the driver would crash hard - blue screen reboot hard - as soon as it reported it had logged into the pool (so, presumably, as soon as it tried to generate the first share). I have no idea why 18.5.1 works when 18.6.1 didn't, but that's computers for you.
I have RX 560 2gb rig mining XMR. I use manual intensity, all cards needed lower intensity than the auto intensity. I recommend start at 26 and keep decreasing by 0.5 increment if not stable. Some of my cards had to go down to 24 and the lowest is 23.5 Core 1180@895mV/Mem 2000-2100, power limit +10% each card running 450-465 H/s and using ~36W with 18.6.1, the best driver for me. My cards needed +5 mV on the memory compared to v7. I tried 18.5.x it hashes a tiny bit more but uses more power ~40W v8 is more hungry for virtual memory, I have it set at 3x total vram. I also recommend using a reasonably low static difficulty with XMR, variable difficulty can get too high and cause stability/pool problems with weaker cards like the 560. |
|
|
|
|
Dang this v8 is a completely different animal from v7, keep having to make adjustments. It stresses the cards more than I thought, actually had to add 5 mV to mem voltage. Wondering why my cards were underperforming with pool, realized it's bad to roll with variable difficulty on XMR. Static difficulty tuned to find a share every ~45 sec. is definitely better.
|
|
|
|
Meh. I installed the older 18.5.1 driver, and it still doesn't help. It started promising with the secondary GPU spitting over 1200h/s, but the next report shows around 700 again… I could already see its gonna be a problem when in GPU-Z power consumption jumps between 60-140W, instead of being constant.
Big power and hashrate fluctuations are usually caused by too high intensity or too low power limit setting. |
|
|
|
whats the point of dealing with all this instability and extra heat from cnv8 when its less profitable atm than even eth.
hash rate is pretty much back to where it was 500ghs WTF lol
Not happy with it either, XMR difficulty drop ending in a blink  Knocked off ASICs but it seems the difficulty drop attracted too many GPU farms to move away from ETH. |
|
|
|
1 rig 4 x vega56 + 2 x rx570 9400hs 1040watts at the wall
All my rx 570s hashing exactly same on v8 940hs.
My rx 550s are at 450hs each
how do you reach 450 with rx 550? what do you have in the config? I don't buy it either. My best 560's max out at ~465 h/s. I doubt the average 550 can do anything over 430 h/s, if it's real he must have crazy high mem oc and super aggressive timing straps. |
|
|
|
Can someone help? When i start my miner at the very start my main GPU always crash.... i've change 2-3 different cards and the problem is still the same. Using 18.5.1 and 1803win edition. Anyone with same problem like me?
Try to use the integrated gpu on your mobo for main display. |
|
|
|
|
After making some adjustments with v8, I'm hashing at 87-91% of my original v7 rates across all the cards on my rx560 rig.
Has anyone been able to recover more than this? Only thing I haven't played with is the new "bralock" parameter.
Still on 18.6.1 driver, it gives lowest power consumption for me. 18.5.x drivers are a tiny bit faster but power consumption goes up too much.
|
|
|
|
|
Made another discovery with my rx560 rig, v8 actually prefers lower intensity than v7.
0.5 less manual intensity gave all my cards another 15-25 h/s.
|
|
|
|
|
I have a rx560 rig using 18.6.1 drivers, on v8 they all went down to ~380-400 h/s with the same settings from v7 (500-520 h/s)
I had power limit at -10% with v7, on v8 I can get back to ~430-460 h/s just by raising the power limit to +10%
Some cards got a small boost when I increased virtual memory from 16 gb to 20 gb. Haven't tried to change the intensity and worksize yet, doubt they will make any difference. v8 definitely needs more power and virtual memory than v7 to alleviate hash loss.
|
|
|
|
|
Anyone else using this miner with low memory cards like 2gb RX560/560D?
The default intensity setting of 10 seems to be optimal only for 4 gb cards, because it causes errors and crashes on all my 2gb cards. The highest my 2gb RX560 cards can handle without errors is 7 intensity, and I have an older RX560D card that can only handle 4 intensity without crashing.
|
|
|
|
|
I wouldn't spend a single penny into ETH.
My prediction: ETH will soon fall under $150 and inevitably crash to nothing. For the last 2+ years it has been the top coin for mining, so it is clear as day: There is a major conspiracy in place to screw over the long-time miners that continue to HODL. The powers-that-be obviously don't want a lot of overnight millionaires like the early Bitcoin miners.
XMR and DGB are safer bets to make reasonable gains soon.
|
|
|
|
What GPU's are you guys running?
For XMR is Vega the Best. Sometimes not, if you get really unlucky with silicon lottery you can get not enough hashrate for the high power draw. HBM has wild variance, some vega 56 guys have gotten really shafted and hash 200-300 H/s lower than expected. So in many ways the rx 560/570/580 could actually be a safer investment than vega. |
|
|
|
|
Don't underestimate memory voltage.
I was always running some of my rx cards at stock 850 mV. Just bumping them up to 860 mV seems to make them hash a little better and improve rig stability.
|
|
|
|
|
Show Posts
