Vega 56 and Vega 64 guide

[hohey22]

Really dumb issue here. I can’t manage to get over a 44-45 MH/s for each my 3 VEGA 56s Samsung HMB2. I see many here mining around 51-55 MH/s.

My cards (all original VEGA 56, no 64s):
0: Gigabyte OC RX VEGA 56 (Samsung HMB2)
1: PowerColor RX VEGA 56 (Samsung HMB2)
2: MSI Air Boost RX VEGA 56 (Samsung HMB2)
^I flashed these all over to the ASUS ROM since I heard they needed 2018 firmware for best performance, and that ASUS & MSI ROMs were the most stable.

-HiveOS latest beta (hiveos-0.6-200-beta@210303)
-Same effect on Hive and ViaBTC pools
-Flashed all to VEGA 56 (2018) ASUS ROM “Asus.RXVega56.8192.180418.rom”
-Teamredminer v.0.8.2.1
-No difference with and without this TRM config:
–eth_config=B
-2 Different MOBOs tried, everything is in x1 PCIe mode/speed
EDIT: Forgot to mention I get this yellow warning on the web interface: Got unknown command "tweakers"

My best stable & performance settings rn:
-FAN 70
-CORE 1000
-VDD 870
-MEM 950
-amdmemtweak strap: amdmemtweak --CL 20 --RC 37 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12

Can’t go for:
-FAN 80
-CORE 1070
-VDD 812
-MEM 1020

Issue: Miner doesn’t start at all beyond initializing and going into OpenCL mode. If I connect any card to a monitor it gets distorted with white rectangles until I revert those OC settings to my working ones.

[ss-silver]

I bet we can get those over 50
Im guessing issue is:

1. Asus cant run at 812, my limit for my Asus Strix 56 is 838. Try VDD 850 while figuring out the other OCs, then you can try dropping to 838 once its run for a day @ 100%.

2. RCDRD 12 is too tight for that OC setting. Change RCDRD to 18, and keep all the other values the same with that starp and try to boot at 1020 mem
   This is the strap I have on my 64 running at 1050 mem
   amdmemtweak --CL 20 --RC 37 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 18 --RCDWR 12
   also
   –enable _compute doesn’t work anymore.

Couple questions:
Did you include the xxx or put numbers there? just “–eth_config=B” works fine.

@hohey22

–eth_config=Bxxx

What kind of cards did you have 64 Rog Strix? 64 Arez Strix? I had to flash bios on a different Rog Strix a while ago and the 2017 Strix Bios worked just fine.

@hohey22

-Flashed all to VEGA 56 (2018) ASUS ROM “Asus.RXVega56.8192.180418.rom”

[ss-silver]

its pretty easy for fix the bricked bios if you do it form the rig and have a bios switch, I bricked one of my 5700s two weeks ago and fixed it.
Note: I have Nvidia card on one rig so have a browser on that rig which makes it easier to flash bios, not sure how you use hiveOS to flash if you dont have a Nvidia card??

but basic process was

1. Plug in the card with bios switch on the working side, boot and make sure HiveOS recognizes it.

2. Stop the miner, download the bios you want and goto The https://the.hiveos.farm/ from the browser on the rig.

3. Under the worker’s over clock settings click flash bios, select the right card, remember the force it toggle…

4. then FLIP THE BIOS SWITCH TO THE BAD BIOS, choose the file from downloads and click update then reboot after it flashes.

mine started mining on the new bios right after reboot.

[Smining570]

so u can flip the switch when gpu is powered? I have the card mining with other bios so wouldnt want to risk bricking that one too, cause after that, hive wont recognize card on either switch position…can u please confirm so ill give it a try, would be great to get a vbios working

[hohey22]

My cards (all original VEGA 56, no 64s):
0: Gigabyte OC RX VEGA 56 (Samsung HMB2)
1: PowerColor RX VEGA 56 (Samsung HMB2)
2: MSI Air Boost RX VEGA 56 (Samsung HMB2)
^I flashed these all over to the ASUS ROM since I heard they needed 2018 firmware for best performance, and that ASUS & MSI ROMs were the most stable. What ROM do you recommend?

Switched only to “–eth_config=B” instead of “–eth_config=Bxxx” (with x’s) and that didn’t make a difference.

Also forgot to mention I get this yellow warning on the web interface: Got unknown command "tweakers"

[ss-silver]

Ya for sure, I was very nervous on my 5700, bricked it they day I bought it for $840 lol but ya i flipped the switch right before I clicked flash and it worked, it flashed the correct bios and have never flipped that switch back
youtube proof

[Smining570]

ill try it now then!

[ss-silver]

Ahh thats the issue, unless they are reference cards (single fan blower model) only flash the same card’s bios, even for reference only do one of the reference bios. I use Sapphires, but performance is exactly same as when I used the 2017 AMD bios.

Can you flash them all back to original bios or get the originals for those cards from techpowerup?

I only flash bios if its a 64 or previous owner put a different bios on it (2 of my 56s are on stock bios and 2 came with a 64 bios from gamers so flashed the reference bios on those) they are all reference cards except my Asus, on stock bios.

Airboost has a 2018 bios on techpowerup that is good, I don’t own Gigbyte cards so not 100% sure if they have different models or just the reference, and for Powercolor use the bios from the same card as they have different models.

[Smining570]

##removed##

[Smining570]

###edit#### understood …and it worked…lets see what hash i can get out from this one now .thanks Silver

Looks like mem 1020 is max. I leave it for now and try up with core later.
Good increase in hash with new vbios

Had 7hrs run with these settings, one invalid. Confirmed today that mem 1020 is max for this card.
Went up to 1130 with core, dont want to even try higher… got 55.45mh @ 122W, so i changed straps to get lower consumption.

New starps;
amdmemtweak --RC 37 --RP 12 --WR 13 --CWL 8 --FAW 12 --RAS 22 --REF 65535 --RFC 239 --RTP 6 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12

Thanks once again for all the info that is shared on this thread.

[TCLL]

About your reboot issues, it’s probably because you are using and slow/old usb drive for Hive os right ? Try with an SSD, it’s a lot more reliable : )

[TCLL]

@hohey22

Also forgot to mention I get this yellow warning on the web interface: Got unknown command "tweakers"

Update Hive os

[hohey22]

Hey, so I initially forgot to mention I get this yellow warning on the web interface: Got unknown command “tweakers”. I always apply the strap from “Default Config” (Used by default. Can be overridden by the algorithm’s configuration) in the Overclocking (worker) tab. I had to use the “Run Command” button to manually apply the strap. Any ideas why it doesn’t apply to begin with? It’ll be so annoying having to manually put in the strap code every boot, any workaround? Im now above 50 MH/s applying the strap manually to a single GPU!. Also flashed the 2018 MSI ROM onto my ‘generic’ Reference Samsung VEGA 56 Cards (1 is a PowerColor but is ok), works great.

Someone else here has the same “tweakers” command issue: https://www.reddit.com/r/HiveOS/comments/mqv5j2/what_does_got_unknown_command_tweakers41m_27s_mean

I can’t use the stable HiveOS version since it just crashes a lot. I’m on beta “hiveos-0.6-200-beta@210303”.

[TCLL]

What do you mean with it crashes a lot ? What exactly happens ?

[Smining570]

brand new kingston 128gb ssd, when i started with hive…with usb, i learned that lesson quite fast
I think i found the solution. I had before another ssd, with a bit higher reading/writing speed, a small portable 128gb drive. It was geting quite warm when in use and i had few issues with reboots, so i changed that to this “proper” kingston ssd with usb 3 adapter casing.
What i noticed was that ssd with usb3 adapter took a sec to power up and that was the reason for this bios boot issue. Before i did set a delay in MB bios to give few sec to ssd start reading, that worked every now and then but i changed back to this portable usb ssd when i found the solution to the issue that made me chage the drive.
Now my H110 board is booting fine every time so boot issue case closed thanks for the suggestion, i do belive that usb drive or old ssd is a common reason for boot issues, usb flasdrive for sure anyways

[hohey22]

Doesn’t seem to like my integrated Intel UHD GPU or LAN, kernel panics. I’m on a Sandy Bridge MOBO.

[oni]

@hohey22

Hey, so I initially forgot to mention I get this yellow warning on the web interface: Got unknown command “tweakers”.
…
I can’t use the stable HiveOS version since it just crashes a lot. I’m on beta “hiveos-0.6-200-beta@210303”.

I think Tweakers is not yet on the 200 version but only on later versions. 203 for sure.
And stable means that it’s … well… more stable than beta… I have no idea what you’re doing wrong in stable for it not to work.
On 200 version you could try the older xinit.user.sh or similar. Search the forum for more info on that.

[oni]

@Smining570

so u can flip the switch when gpu is powered? I have the card mining with other bios so wouldnt want to risk bricking that one too, cause after that, hive wont recognize card on either switch position…can u please confirm so ill give it a try, would be great to get a vbios working

Yes, you can flip it while running.
And the bios with the switch flipped away from the HDMI/DVI connectors is write protected, so even if you would want to flash a bios over it, it is not possible. It’s the backup bios that can save lives (or gpu’s anyway )
You can thus only overwrite the bios with the switch flipped towards the connectors.

Not all Vega’s have this dual bios, so be careful when flashing those who have only 1 bios as if it goes wrong there it’s game over. That’s why I don’t flash my Gigabyte 8G OC’s.

[Iska]

@Smining570

shy 52

If it is not difficult, you can help with the search, I have already planned everything, the maximum result is 45 Mh/s on the Sapphire Vega 56 hynix. Thank you in advance

[Smining570]

Okay. When i got this card i had switch flipped towards power connectors “performance mode” and tried to flash that bios, it got bricked and hive didnt even boot when switch on that position after flash. Now with ss Silver´s guide i reflashed that side bios again and got that one back to live with vbios from tech power up.
Maybe it was something else that happened here, but this was the way it went for me.
I do remember now that u have mentioned about locked bios before, naturally i didn´t remembered that when i was flashing the card… in future i must think a bit more ahead before i make any critical changes to hardware