More
referral
Increase your income with Hive. Invite your friends and earn real cryptocurrency!

Vega 56 and Vega 64 guide

Uploading: Ekran Resmi 2021-05-14 22.58.44.png…

can you show me a way I need help.

from the mem info it looks like the vbios might be wrong one xxx.xxx.xxx. Maybe if u doubble check that its the right vbios and try to reflash the card? …remember that flashing can brick your gpu :wink:

The MSI Airboost vbios gives this xxx-xxx-xxx version so it might be correct.

How did you apply the straps? By the looks of it it wasn’t in the Tweak section of the OC window; did you add them to the command line or in the old xinit.user.sh?
I see you have very high RCDRD of 22; is that the lowest you can get it without loosing stability?
I have this strap on my MSI Airboost:
amdmemtweak --CL 20 --RC 36 --RP 13 --WR 13 --CWL 7 --FAW 12 --RAS 23 --REF 65535 --RFC 248 --RTP 6 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 18 --RCDWR 11
Make RCDRD higher or lower according to long term stability

1 Like

I see you’ve got them running allright :smiley:
Now you should play a bit with the OC’s and straps to get the GPU’s stable and/or the hashrate higher.

New to HiveOS but has been troubleshooting this for a few days now.

My Vega 64 FE is working well, but regular Vega 64 is reporting the following

May 14 12:18:06 CF002 kernel: [   31.259832][  T948] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing D7E2 (len 279, WS 16, PS 4) @ 0xD8E6
May 14 12:18:06 CF002 kernel: [   31.260645][  T948] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing A7FA (len 219, WS 8, PS 4) @ 0xA8C5
May 14 12:18:06 CF002 kernel: [   31.261482][  T948] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck executing 9BB6 (len 381, WS 0, PS 8) @ 0x9C3B
May 14 12:18:06 CF002 kernel: [   31.262343][  T948] amdgpu 0000:00:0a.0: amdgpu: gpu post error!
May 14 12:18:06 CF002 kernel: [   31.262871][  T948] amdgpu 0000:00:0a.0: amdgpu: Fatal error during GPU init
May 14 12:18:06 CF002 kernel: [   31.278891][  T948] amdgpu: probe of 0000:00:0a.0 failed with error -22
May 14 12:18:06 CF002 hive[851]: Saving /sys/class/drm/card1/device/pp_table
May 14 12:18:06 CF002 kernel: [   31.302693][ T1009] pci 0000:00:0a.0: No more image in the PCI ROM
May 14 12:18:06 CF002 kernel: [   31.308347][ T1009] pci 0000:00:0a.0: No more image in the PCI ROM
May 14 12:18:06 CF002 systemd[1]: Started Hive Watchdog Service.
May 14 12:18:06 CF002 hive-watchdog[1021]: Watchdog disabled in config (/hive-config/rig.conf)
May 14 12:18:06 CF002 hive-watchdog[1021]: MINER RESTART:      minutes
May 14 12:18:06 CF002 hive-watchdog[1021]: REBOOT:             minutes
May 14 12:18:06 CF002 hive-watchdog[1021]: MAX LOAD AVERAGE:  .0 (min 13.0, def 28.0)
May 14 12:18:06 CF002 hive-watchdog[1021]: OK LA(5m): 0.34 < 28.0, LA(1m): 1.40 < 56.0
May 14 12:18:07 CF002 hive[851]: Cannot find DRI instance for pci:0000:00:0a.0
May 14 12:18:07 CF002 hive[851]: Cannot find DRI instance for pci:0000:00:0a.0
May 14 12:18:07 CF002 hive[851]: ERROR: can not match card id for GPU 00:0a.0

Also, i see people refering to an “Vega HiveOS”, is there a seperate place to pick up that image?

Looks like you guys here are flashing your VEGA 64’s with 56 ? Should i try and do that to resolve above issue?

Also, should i flash my Frontier Edition Vega 64 with 56 as well?

So original question, I have bought many (15) Vega cards and none get over 960 mem, can you enlighten me on what I am missing? Above 960 they drop to 8-9mh

1 Like

some more info about your cards would be apprciated as requested before…

indeed; which straps have you applied on those?
straps and clocks go hand in hand; some straps work better with lower clocks, some straps work better with higher clocks

I have had best luck with amdmemtweak --CL 20 --RC 36 --RP 12 --WR 13 --CWL 6 --FAW 12 --RAS 22 --REF 65000 --RFC 249 --RTP 4 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 11 --RCDWR 5

I tried 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

but just got lower hashrate and still go down to 8 mh at anything above 960 mem

What Pool is best with Teamredminer runing vega 56 & 64, I have been using Hiveon but is there a more profitable setup.

Hi,

Is mining on egpu slower than direct on the mobo? My guess is it shouldn’t be but the highest I could get is 31Mh/s for my gigabyte vega 56 reference. The pool hashrate is higher though. Using team red miner.

I have oc the card to 1030 core, 960 mem. Tried all different straps too and currently using:
–CL 19 --RAS 22 --RCDRD 9 --RC 36 --RP 14 --RRDS 3 --RRDL 3 --RTP 6 --REF 17000 --RFC 249

The miner is set to eth_config=B mode.

Am I missing something?

Oh and compute mode is set already. Power draw is about 110W.

It’s a MUST to flash your vega 64 to 56 no questions asked.
See my vega 64s flashed by vega 56 bios.

start

core 1020 dpm 0 vdd 830 mdpm 0 mem 960 pl 150

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

If that works, with one card, try to increase mem by 5 if no luck, go up with RCDRD to13 and try again.
If 960 is max mem, back to RCDRD 12 and try to go up with core by 10 at the time and give gpu some time in between with new core value and see if u start to get invalids, if not, another 5-10 until its crash or gives invalids.
My 64 flashed to 56 is maxed out on mem 980

I have had good luck with these straps on 56, but not with same brand gpu, these allows me to go mem 1045 that is unusual, some say its likely that this card is actually running with 1028 that is “max” for 56… core 1130 +56mh.
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

Here is many guys with same brand 56 vega´s, im sure they can be more help to u with strap´s&oc´s.

good luck

Thank you for the help, I started to buy your straps 48,77. How can I push it further?
What should I do with my frequency values?
the one you are using now
CORE 1010
VDD: 830
MEM:950

I’m determined with these issues, but I couldn’t see 50mh / s :slight_smile: (:slight_smile: amdmemtweak --gpu 0,1 --RAS 26 --RCDRD 12 --RCDWR 12 --RC 38 --RP 12 --RRDS 3 --RRDL 5 --RTP 6 --FAW 12 --CWL 8 - WTRS 4 --WTRL 9 --WR 13 --REF 24000 --RFC 239
amdmemtweak --gpu 2 --RAS 23 --RCDRD 18 --RCDWR 12 --RC 36 --RP 13 --RRDS 2 --RRDL 3 --RTP 6 --FAW 12 --CWL 8 --WTRS 4 --WTRL 6 --WR 13 --REF 20600 --RFC 244

hi. i on my 56 hynix: 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 14 --RCDWR 12
With mem 965 vdd 830 core 1020 these gives +52mh. These are powercolor and Sappphire. They can go above 53mh, but in the long run there will be issues with higher oc´s.

1 Like

Best bios for this card? image

Has a switch near ports labeled silent, standard, and oc, also has a switch near 8pin outlet, is that the dusl bios switch?

1 Like

Found a Wikipedia with some info on memory timings but there are some equations that don’t seem to apply on the stock Vega memory timings, mainly RAS = RCD + WR
I assume this is meaning the max of rcdrd or rcdwr when it mentions RCD, but the stock settings for the Samsung and Hynix don’t add up to the RAS.

I did notice that the RC = RP + RAS for the stock Samsung and Hynix Settings you posted, so I’m going to test out RAS 26 on those two cards throwing invalids to see if it helps.

VDD 812 on the reference Vegas IS very stable, as long as the mem & rcdrd are at stable levels.

2 Likes