zeef
Newbie
Offline
Activity: 296
Merit: 0
|
 |
July 09, 2018, 07:38:54 PM |
|
If you have a Vega, and want to mine V7 algos, use Adrenaline 18.6.1 drivers, if you want to mine Heavy algos, use Adrenaline 18.3.4
will try 
|
|
|
|
|
|
|
|
Whoever mines the block which ends up containing your transaction will get its fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
LeonManveli
Newbie
Offline
Activity: 23
Merit: 0
|
 |
July 09, 2018, 08:39:24 PM |
|
If you have a Vega, and want to mine V7 algos, use Adrenaline 18.6.1 drivers, if you want to mine Heavy algos, use Adrenaline 18.3.4
And what about RX580 driver version to mine heavy and V7? Thank you Doktor83 for your work 
|
|
|
|
fellowbeing
Newbie
Offline
Activity: 15
Merit: 0
|
 |
July 09, 2018, 09:05:57 PM |
|
vega got more hash on 1.6.2, rx series maybe a little less, but next version should get things back on track.
I have a rig of 5 Vega Frontier Editions. I have not tried on heavy algo but the CN7 is giving me about 100 less. Intensity is set to 120 with double threads. I am very happy with SRB Miner. with XMR STAK, if I set intensity to 2048 for each thread then I would get closer to the hashrate of SRB but still 100 or so less. With SRB 1.6.1 I am getting a stable 10.9 KH/s, if I added another Vega FE card it would be 13 KH/s. You can see photos of my rig and its making here: https://postimg.cc/gallery/ivrtjh24/As you know Vega FE cards have 16 GB of HBM2. Is it possible to run more threads on these GPUs ? It would be awesome if there was a way to utilize this memory. I would appreciate if you could provide an answer to this question, as you are writing the code for SRB Miner and you know better how much memory can be used. Thanks for the awesome SRB Miner I don't have FE vega, but try this for V7 algo: "gpu_conf" : [ { "id" : 0, "intensity" : 126, "worksize" : 8, "threads" : 2} ] Thanks, but it appears that doesn't help Vega FE cards. I tried 1.6.3 but it is the same so I am using 1.6.1 again. I'll mess around with it again and will update. Edited: If I have to give up on Blockchain drivers for Adrenalin 18.6.1 to see these changes, then it will be a dead end for me, Vega FEs can't be overclocked on those drivers.
|
|
|
|
doktor83 (OP)
|
 |
July 09, 2018, 09:12:19 PM |
|
Thanks, but it appears that doesn't help Vega FE cards. I tried 1.6.3 but it is the same so I am using 1.6.1 again. I'll mess around with it again and will update.
if you copied newer version of miner over old one, make sure you delete .srb files before running the miner it has to create new .srb files.
|
|
|
|
UnclWish
|
 |
July 09, 2018, 09:50:49 PM |
|
If you have a Vega, and want to mine V7 algos, use Adrenaline 18.6.1 drivers, if you want to mine Heavy algos, use Adrenaline 18.3.4
And what about RX580 driver version to mine heavy and V7? Thank you Doktor83 for your work  On latest 18.6.1 Windows 10 driver cn-v7 and heavy on my RX 580 works good! Speed is not lower than on 18.3.4.
|
|
|
|
henri2018
Newbie
Offline
Activity: 46
Merit: 0
|
 |
July 09, 2018, 10:11:59 PM Last edit: July 09, 2018, 10:40:58 PM by henri2018 |
|
V1.6.3 - More speed on Vega56 cards on every algo (probably on Vega64 and VegaFE too, i don't have them to test) - Added parameter --enableduplicategpuid (used in start.bat), that enables to use the same gpu id in gpu_conf multiple times - Removed useless kernels 3 and 4 - Removed useless CPU opencl support ... Don't copy new version of miner over old one, or if you do make sure you delete .srb files before running it!
Great update, dok. I am mining bittube. Vega56 increased minimum 30 h/s, some got 40 and 50 h/s. RX580 increased about 5-10 h/s. Need to monitor it within few hours to get it stable hashrate.
|
|
|
|
mrsimit
Newbie
Offline
Activity: 3
Merit: 0
|
 |
July 10, 2018, 08:57:10 AM |
|
Great job! Thanks, Doc!  1.6.2 was worse for me, now 1.6.3 is better than 1.6.1, especially on Vega64. 8 cards give 17320 vs 17076 on 1.6.1, CNv7 Can you please share your Overdrivetool settings for V7 algo and your intensity thanks a lot
|
|
|
|
duyquang06
Newbie
Offline
Activity: 154
Merit: 0
|
 |
July 10, 2018, 10:18:33 AM |
|
Anyone can share the devcon file config reset for vega, please.
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
 |
July 10, 2018, 10:26:04 AM |
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10
|
|
|
|
lebuawu2
Jr. Member
Offline
Activity: 176
Merit: 2
|
 |
July 10, 2018, 10:35:46 AM |
|
Anyone can share the devcon file config reset for vega, please.
new driver doesn't need to disable and enable RX Vega anymore. you should try new driver the hash rate I believe also the same or maybe better.
|
|
|
|
fellowbeing
Newbie
Offline
Activity: 15
Merit: 0
|
 |
July 10, 2018, 10:39:38 AM |
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10 This works for my Vega FEs @echo off cd %~dp0 devcon.exe disable "PCI\VEN_1002&DEV_6863" timeout /t 3 devcon.exe enable "PCI\VEN_1002&DEV_6863" timeout /t 3 pause
|
|
|
|
fellowbeing
Newbie
Offline
Activity: 15
Merit: 0
|
 |
July 10, 2018, 10:46:17 AM |
|
So based on what I have read here: On SRB 1.6.3 with Vega 64s, people are getting about 2165 H/s a bit more or less. I have been getting ~2180 H/s on each Vega FE with blockchain driver since SRB 1.5.4 or so.... If I cool them even better, I'd get 2200 on them too. So this all means as a Vega FE owner I should stick with my 1.6.1 and still have 5 or 10 H/s more than Vega 64 with the latest driver, not that it matters. But I am sure if ever they make another proper blockchain driver these cards can do much more.
|
|
|
|
dragonmike
|
 |
July 10, 2018, 10:49:23 AM |
|
Great job! Thanks, Doc!  1.6.2 was worse for me, now 1.6.3 is better than 1.6.1, especially on Vega64. 8 cards give 17320 vs 17076 on 1.6.1, CNv7 Can you please share your Overdrivetool settings for V7 algo and your intensity thanks a lot Yes please. I've got six Vega 64's hashing at around 2075 h/s each. 1428 core clock, 112 intensity.
|
|
|
|
duyquang06
Newbie
Offline
Activity: 154
Merit: 0
|
 |
July 10, 2018, 11:02:46 AM |
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10 This works for my Vega FEs @echo off cd %~dp0 devcon.exe disable "PCI\VEN_1002&DEV_6863" timeout /t 3 devcon.exe enable "PCI\VEN_1002&DEV_6863" timeout /t 3 pause thank you so much So based on what I have read here: On SRB 1.6.3 with Vega 64s, people are getting about 2165 H/s a bit more or less. I have been getting ~2180 H/s on each Vega FE with blockchain driver since SRB 1.5.4 or so.... If I cool them even better, I'd get 2200 on them too. So this all means as a Vega FE owner I should stick with my 1.6.1 and still have 5 or 10 H/s more than Vega 64 with the latest driver, not that it matters. But I am sure if ever they make another proper blockchain driver these cards can do much more.
i know that feel. Make the fan run 3500rpm minimum. Doc, i love u, my vega56 ref even reach 2000h/s with powersaving profile [2018-07-10 18:03:24] GPU3 : 2001 H/s [T: 69c, RPM: 4303, CC: 1400 MHz, MC: 950 MHz][BUS:3] intensity 120/ dual_threads true
|
|
|
|
doktor83 (OP)
|
 |
July 10, 2018, 11:39:44 AM |
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10 This works for my Vega FEs @echo off cd %~dp0 devcon.exe disable "PCI\VEN_1002&DEV_6863" timeout /t 3 devcon.exe enable "PCI\VEN_1002&DEV_6863" timeout /t 3 pause You dont need reset scripts, why not use the builtin "restart_devices_on_startup" ? Put in config.txt : "restart_devices_on_startup" : true
|
|
|
|
livada
Newbie
Offline
Activity: 417
Merit: 0
|
 |
July 10, 2018, 04:58:57 PM Last edit: July 10, 2018, 05:12:13 PM by livada |
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10 This works for my Vega FEs @echo off cd %~dp0 devcon.exe disable "PCI\VEN_1002&DEV_6863" timeout /t 3 devcon.exe enable "PCI\VEN_1002&DEV_6863" timeout /t 3 pause You dont need reset scripts, why not use the builtin "restart_devices_on_startup" ? Put in config.txt : "restart_devices_on_startup" : trueif put in config resets vega permanently (chg coin) and if you put the script reset only when the computer is turned on i neeed only one enable/disable and one heavy with 60 intensitiy when turn on computer. and script work fine.
|
|
|
|
hesido
Jr. Member
Offline
Activity: 157
Merit: 5
|
 |
July 10, 2018, 06:11:03 PM |
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10 This works for my Vega FEs @echo off cd %~dp0 devcon.exe disable "PCI\VEN_1002&DEV_6863" timeout /t 3 devcon.exe enable "PCI\VEN_1002&DEV_6863" timeout /t 3 pause You dont need reset scripts, why not use the builtin "restart_devices_on_startup" ? Put in config.txt : "restart_devices_on_startup" : trueif put in config resets vega permanently (chg coin) and if you put the script reset only when the computer is turned on i neeed only one enable/disable and one heavy with 60 intensitiy when turn on computer. and script work fine. Oh boy.. Working with Vega sounds more like voodoo magic / art than science.
|
|
|
|
treanski
Full Member
 
Offline
Activity: 364
Merit: 106
ONe Social Network.
|
 |
July 10, 2018, 07:33:13 PM |
|
Anyone can share the devcon file config reset for vega, please.
.reset.bat cd %~dp0 timeout /t 10 devcon.exe disable "PCI\VEN_1002&DEV_687F" timeout /t 10 devcon.exe enable "PCI\VEN_1002&DEV_687F" timeout /t 10 This works for my Vega FEs @echo off cd %~dp0 devcon.exe disable "PCI\VEN_1002&DEV_6863" timeout /t 3 devcon.exe enable "PCI\VEN_1002&DEV_6863" timeout /t 3 pause You dont need reset scripts, why not use the builtin "restart_devices_on_startup" ? Put in config.txt : "restart_devices_on_startup" : trueif put in config resets vega permanently (chg coin) and if you put the script reset only when the computer is turned on i neeed only one enable/disable and one heavy with 60 intensitiy when turn on computer. and script work fine. Oh boy.. Working with Vega sounds more like voodoo magic / art than science. no its much easier than working with polaris gpus you dont need to modify bios/memory timings...with vega you just need to learn how you do a powerplay mod, how you do a batchfile for overdriventool and thats it read this carefully -> http://vega.miningguides.com/if you dont understand it read again
|
|
|
|
fellowbeing
Newbie
Offline
Activity: 15
Merit: 0
|
 |
July 10, 2018, 07:59:11 PM |
|
[2018-07-10 18:03:24] GPU3 : 2001 H/s [T: 69c, RPM: 4303, CC: 1400 MHz, MC: 950 MHz][BUS:3] My Vega FEs are set to CC: 1550MHz | CV: 890mV & MC: 1100MHz | MV: 880mV, their fans are running above 4800 RPM and temperatures are between 65 to 68; also for me the bios switch won't make a difference.
|
|
|
|
roma__11
Newbie
Offline
Activity: 115
Merit: 0
|
 |
July 10, 2018, 08:17:46 PM |
|
what motherboard you use for connecting all the vegas?  Gigabyte GA-B250-FinTech
|
|
|
|
|