Thanks for the suggestion Oni.
I tried those straps but card comes up as ‘dead’ crashes after a couple minutes.
Tried your suggestion on upping/lowering RCDRD and gave up at 20/10. In total around 50 (i’m not joking) combinations of straps and core/vdd/mem without success as the card keeps crashing in minutes. Nothing on, the card runs without crashes.
This POS is about to get binned lol.
@cuthy2k I have a couple suggestions. First I would suggest updating to the latest version of hiveos and using teamredminer version 0.10.0 if you haven’t already. You should also enable r-mode. You’ll use less power and generate less heat. To do that, add the following to the miner section of your flight sheet in the extra config arguments:
–kernel_vm_mode=RR
Also delete these options from the config if they’re in there:
–eth_big_mode_adjust=64
–eth_config=A
–eth_config=B
You’ll need to reboot the rig once the config is set in the flight sheet, if it doesn’t reboot on its own. And if it doesn’t start hashing after the reboot, you may need to manually select TRM version 0.10.0 in the flight sheet instead of “the latest”.
Read the tuning guide here:
Reduce the core clock to 900-950. Reduce the VDD to 750-800. Maybe start on the high end and reduce core/VDD by 5-10 until you lose stability. The guide says 925-950 should be enough. I’m currently running at 965 core and 800 VDD on my Vega 56s / 1020 core and 820 VDD on my Vega 64s, but I’m dual mining Eth+Ton which requires a higher core/VDD.
For the straps, I always start with the following:
amdmemtweak --CL 20 --RC 36 --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 you get reboots or invalids, increase the RC by 1 and restart. If you’re still getting reboots or invalids, increase the RCDRD by 1. All of my Vegas (with the exception of two) are running with RC 37 and RCDRD 13. I’ve gone up to RC 38 and RCDRD 14, but I think you get a better hashrate if you reduce the memory clock instead of going above 37/13. But it’s also fine to use 38/14 if you’re having significant problems with a GPU.
Edit:
After messing around with my config a bit more, I’m getting the best hashrate keeping the RCDRD at 12 and the RC at 36-37. Start with RC at 36, if you get invalids or reboots, increase to 37. If you still get invalids or reboots, reduce the memory clock (as opposed to increasing the RCDRD). With r-mode: for Vega 64s I’m using 1020 core and 820 VDD, starting at 1060 memory clock. For Vega 56s, I’m using 965 core and 800 VDD, starting at 950 memory clock. I’ve found that some GPUs need a higher core clock and VDD, so if these settings don’t work try increasing each by 10 until it starts hashing. With these settings I’m averaging 51 MH/s with my Vega 56s, and 55 MH/s with my Vega 64s (which are all flashed with a Vega 56 bios). Again, this is dual mining Eth+Ton (with the max_dual_impact setting at 0.5), so you may be able to go lower on core/VDD, and you may also get a better hashrate.
After much mucking about I’ve got RR mode to load. Now I just need to play with the settings… I’m too tired lol as Vega’s really take it out of you! Will try another night and see how I get on!
Thanks for the help so far guys, will keep you posted.
so complicated.
Obviously you start with higher VDD and higher CORE.
The only values I need to change is RP and RCDRD.
I would start with RP 12-13 and RCDRD 15. If card works with RCDRD 12, then you can reduce RP to 11.
Also use --high_sample_mode=8 argument - this will show invalids much faster.
I also noticed that you can achieve same hashrate by many many different cores and straps, but you will not be able to stay stable over the card limit.
hi,
I have some vegas, and I wanted to try R-mode on them and bring the power even more lower but if I bring the core voltage under 760mV, the power goes up rly high. I guess it is some kinda limit. Any idea how could I bring it down?
original setup core:1000/760mV/960mem
new setup core:925/760mV/960mem
the power draw on wall is the same 141W
I’ve never messed with RP before. I’ll have to give this a shot.
Gone with RR mode and GPU3 continued to be a b!tch. GPU 3 is Gigashyte Gaming OC.
Took a few goes but running stable for 2hr 30min so far and counting.
amdmemtweak --CL 20 --RC 38 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 21 --REF 65000 --RFC 216 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 14 --RCDWR 12
Now to tackle the 5600XT! 
Glad you were able to get it working. Also looks like you brought your power usage down quite a bit with r-mode.
managed over 5hrs stable before GPU1 went dead. Some would dive right into fixing that but after 2 days of tackling one Vega 56 appearing dead every 2-3minutes I’m happy with 5hrs and 8min of uptime! Thanks for helpl!
if one goes dead; upp that one’s vdd by 5 and see if it helps; if crash again; upp again by 5 until stable 
Hello everyone,
share my vega’s for R mode
For the straps, someone RC 38
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
I will try more low power
That’s great power usage. Are these 64s or 56s?
Sorry, I am late
Some are vega 64, some are vega 56
I was able to tweak a bit more, 36+ hours running up with those settings:
0 - gigabyte ref
1 - sapphire nitro+
2 - gigabyte gaming oc
3 - sapphire pulse
I would like to know if anyone has implemented STABLE TeamRedMiner RMode for AMD Vega FE with 16GB HBM2 .
i have 2 x AMD Vega FE 16GB HBM2 cards with Samsung Memory. One card (GPU3) is stable so far but one (GPU0) keeps crashing every 45 mins to 1 hr . Here is what i tried so far in RMODE:
System type: HiveOS Linux 0.6-217@220522
Kernel: 5.10.0-hiveos #110
AMD OpenCL Driver: 21.40.1 (5.13.0201)
Miner : TeamRedMiner 0.10.0
RMode Flightsheet Settings under extra settings: --kernel_vm_mode=RR
unstable GPU = GPU 0
GPU 0 Clock settings: Core = 1000 , VDD = 820 , MEM = 1028
AMDTweak Straps:
amdmemtweak --CL 19 --RC 44 --RP 14 --WR 14 --CWL 8 --FAW 18 --RAS 28 --REF 65535 --RFC 300 --RTP 5 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 10
Average ETH Hashrate = 42.5 MH/s
Tried the following Core, VDD, Mem settings with same straps but those were worse and very unstable:
Test 1: 925, 820, 1025 – crashed
Test 2: 925, 800, 1025 – crashed
Test 3: 900, 780, 1025 – crashed
Test 4: 900, 820, 1025 – crashed
Test 5: 800, 800, 1025 – crashed
Test 6: 800, 820, 1025 – crashed
Test 7: 1000, 820, 1025 – crashed
Any Help or suggestion is well appreciated
Hi,
I think the best is to begin with lower memory and increased if stable.
could you please share you amdmemtweak for the Asus vega please ? thanks
and increse the VDD also
Straps for ASUS Vega 56
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 13 --RCDWR 12
Hi,
This is what I am running in R-Mode. I am running a little less MH to save power.
Super stable for me. Let me know your thoughts. GPU 0 is ASUS.
Straps the same for all.
amdmemtweak --CL 20 --RC 36 --RP 14 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65000 --RFC 249 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 14 --RCDWR 12
My thoughts on Vega FE and Vega Gigabyte cards. They are shit! Impossible to get over 45-48 M/h. SELL as quick as possible and avoid HOURS of headaches. I have almost all Sapphire and XFX cards…no issues generally…
Alan
i agree the Vega FE cards are a nightmare to configure and get running stable.
