Finally I have fixed the bug with Vega.
New version will be available within 24 hours.
Also I will reduce devfee and it will be executed once an hour, similar to dual and zec miners.
Linux will get an update as well? Or holding back on it for now? Yes I will release Linux version too. Though Vega won't work in Linux, currently I don't support ROCm drivers. What is the expected speed for Vega? Can't wait ))) |
|
|
|
you are unhappy to not have sell your secret guide for vega? ...
I'm silently crying in the corner )) Well since you are in a corner not doing anything, do you mind helping me undervolt, I'm having a time... If I apply the morepowervega64 registry edit by hellm on OC. I'm good, but if I try to apply oldcomer's modified version I get a black screen and the gpu fan at 100% when I try to restart. I reboot in safe mode and DDU and reinstall blockchain driver. Please help me obi wan. Which do a modify to what to reduce my power usage? 0.4 eth guys, sorry )))))))))))))))))))) |
|
|
|
Check for SmartCash coin, guys. It is on Cryptopia ))
Thanks for information. It is the place where I get tips. It's my pleasure. Just want to get rid of some miners from the shit coin I'm mining currently )) |
|
|
|
you are unhappy to not have sell your secret guide for vega? ...
I'm silently crying in the corner )) |
|
|
|
Also, has anyone tried setting 56 memory voltage to 1350mv, does it work without bios mod? Would be nice to be able to run mem at 1100mhz as I can do with 64 bios, but without voiding the warranty by swapping bios (though I think in the eu you can basically change software in your electronics without voiding warranty by law, it seems)
Im talking about changing 0xE42 (1250mv) to 0x546 (1350mv)
Only bios flash currently ... And don't mess with air-Vega64 bios ... go for Liquid one )) Why liquid one? What are the pros of using that instead of the air bios? /J Don't want to type a lot ... just take your time and try different settings for your cards. Nobody has to do this work for you. And yes ... this thread will be buried with this stupid big tables from newbies ... time to leave ... |
|
|
|
Also, has anyone tried setting 56 memory voltage to 1350mv, does it work without bios mod? Would be nice to be able to run mem at 1100mhz as I can do with 64 bios, but without voiding the warranty by swapping bios (though I think in the eu you can basically change software in your electronics without voiding warranty by law, it seems)
Im talking about changing 0xE42 (1250mv) to 0x546 (1350mv)
Only bios flash currently ... And don't mess with air-Vega64 bios ... go for Liquid one )) |
|
|
|
|
Guess we need some tool (utility) for reg-modding or this thread will be flooded with regfiles ))
And yes - putting random clock-values to P2-P5 states is not a good idea ))
|
|
|
|
Here's my settings on a Powercolor Vega 56 flashed with the Vega 64 BIOS, Blockchain Driver, v10 claymore doing ETH/DCR to get 37Mh ETH/2150 Mh DCR: https://imgur.com/a/gHxXSbad settings and speed |
|
|
|
I have a feeling that you cannot enable or disable HBCC with blockchain drivers. It is enabled or disabled automatically depending on driver or motherboard/cpu settings. When you play with HBCC slider (switch) you just reboot some driver logic that causes the speed back to normal (high) if it went slow before for some reason ))). Hope you catch what I'm trying to say )) Just look to release notes for more fresh 17.8.2 driver )) Fixed Issues
- The "Reset" option in Radeon Settings Gaming tab may enable the "HBCC Memory Segment" feature instead of setting it to the default disabled state.
- Radeon WattMan may not reach applied overclock states on Radeon RX Vega series graphics.
|
|
|
|
Nice rednoW! Glad you got it working.
I made this little cheat sheet to help me tweaking the .reg file, going to publish below to possibly help other people. Below are the settings I'm using to achieve 1990 H/s @ 0.875. Custom values are highlighted in square brackets.
What are xmr-stak-amd's dev-branch improvements over the current released one, do you know?
No need to mod powerplay such hard, it can cause some glitches )) As for dev-branch they have several commits since master branch, you can track it on github ... but no speed increase )) I actually don't know from what sources they made windows binary they released. |
|
|
|
|
Check for SmartCash coin, guys. It is on Cryptopia ))
|
|
|
|
|
Try to increase your Virtual memory size in windows settings. Are you using blockchain drivers?
As for the brand - Vega cards are all reference now (except for asus strix crap) and are made in one factory I think. So choose with better warranty and customer service brand. Or simply the one you can get cheap ))
|
|
|
|
BTW, I was able to compile dev-branch of xmr-stak-amd on windows ... they have one-letter bug in config that makes an error ... but I found it ))
You do not mean the platform which is supposed to be 0, do you? No, it was Winbuild problem with cmake )) |
|
|
|
Highly doubt if it is stable.
One of my cards needs 910mV voltage (gpu-z) to run 1408/1100 stable, other can handle 900mV. If yours is stable - you are the silicon lottery winner ))
It still running in the same session and I don't see any speed fluctuations, it seems stable. As a matter of fact the pool is reflecting my hashrate very well too. Try lowering the HBM voltage to the same voltage as Vega 56 version. I think this is what did the trick. Well, I tried and it seems to work ... miracle ))  BTW, I was able to compile dev-branch of xmr-stak-amd on windows ... they have one-letter bug in config that makes an error ... but I found it )) |
|
|
|
there is a cuda-9 branch on github
I mean: I already cloned your 2.2.1 sources and I compiled them against Cuda 8. I have to keep Cuda 8 in order to compile for my customers with old NVidia GPU which do not have required drivers for Cuda 9. At the same time I have some Pascal GPUs which I'd like to test against Cuda 9 final. Solution? No problem to have different CUDA SDK versions on one developer machine. Then just clone needed branch from github - it should have proper setting for cuda version. |
|
|
|
I got it running at 1600x 2 . Getting 10k total.
Will push it more tomorrow, wanna see how stable that goes, as I am with 8GB RAM only.
A thing of note to our previous discussion with rednow: Monero seems to be using way less power, and cards are cooler. This is drawing now 1200W, and the hottest card is the unmodded one, but HMB2 is not that hot as it was with claymore's ETH miner. The difference here seems to be only 6-7C, not the 15+ as with claymore's miner.
Any idea how to safely keep track of temps, without the need to push buttons? GPU-Z indeed dropped my hashrate significantly.
I'm using latest hwinfo64 beta for monitoring, but I was needed to disable GPU I2C support in HWINFO settings. It works fine without it. With this setting enabled one of my cards was starting fan on max speed and hangs so only full power off and then reboot helped. |
|
|
|
No idea what the mem voltage does in that software. I think vega 64 bumps voltage up to 1.35v. I would be careful doing that though and make sure you get more than adequate cooling. edit: had some time to tinker, and got it working with the blockchain drivers. very nice speeds, very nice wattage. just a reminder that your platform isnt necessary 0 or 1  I have intel and nvidia and amd gpus - so my platform in xmr-stak-amd config is 2. |
|
|
|
Thanks for this. I've been playing with the power settings with a Sapphire RX Vega 64 Liquid Cooled and got 1990.7 H/s stable @ 0.875 VDDC. Couldn't get power draw at the wall because I need a kill-a-watt thing.
About 145W. More details in the next video this weekend. Highly doubt if it is stable. One of my cards needs 910mV voltage (gpu-z) to run 1408/1100 stable, other can handle 900mV. If yours is stable - you are the silicon lottery winner )) It still running in the same session and I don't see any speed fluctuations, it seems stable. As a matter of fact the pool is reflecting my hashrate very well too. Try lowering the HBM voltage to the same voltage as Vega 56 version. I think this is what did the trick. True HBM2 voltage can be changed only via bios - it is 1.25 for Vega56 and 1.3+ (don't remember exactly) for Vega64. So called memory voltage in Wattman and OverdriveNtool memorу profiles can be either mem controller voltage or some other staff voltage or even can mean nothing )) |
|
|
|
Thanks for this. I've been playing with the power settings with a Sapphire RX Vega 64 Liquid Cooled and got 1990.7 H/s stable @ 0.875 VDDC. Couldn't get power draw at the wall because I need a kill-a-watt thing.  About 145W. More details in the next video this weekend. Highly doubt if it is stable. One of my cards needs 910mV voltage (gpu-z) to run 1408/1100 stable, other can handle 900mV. If yours is stable - you are the silicon lottery winner )) |
|
|
|
XMR-Stak-AMD 1030 H/s "gpu_thread_num" : 2
"gpu_threads_conf" : [ { "index" : 0, "intensity" : 1728, "worksize" : 8, "affine_to_cpu" : false }
{ "index" : 0, "intensity" : 1728, "worksize" : 8, "affine_to_cpu" : false } ] 1728 is indeed the best intensity for 480 cards with xmr stak. Lol, i never tried to run 2 threads with xmr stak this way  Because you ignore Vega thread ))) |
|
|
|
|
Show Posts
