What setting in TRM did you use?
Navi 23 isn’t listed on R mode instructions
What setting in TRM did you use?
Navi 23 isn’t listed on R mode instructions
In “Extra config arguments” I only have this:
–eth_config=R512
But if you use auto-tuning, then I’d use “–kernel_vm_mode=RR” instead.
very good
nice
Also, Did anyone here have to upgrade from the stock AMD Driver 20.40 to the latest for better results?
@m2internet To be perfectly honest I had the best performance with older editions of HiveOS, with older drivers (5-6 months old). At least 3 times I noticed a slight drop in MH/s after updating Hive. The only improvements in hashrate I ever had in the last 6 months were after updating the miner, not the drivers.
@catfish Drop mem clock on GPU7 to 1140 or even 1130. Clearly 1150 is too much for it. Once you clock memory too fast, hashrate drops sharply.
Firstly, Your comments on this thread on overclocking are much appreciated…have been extremely helpful getting my 6600xt’s tuned in. Thx
Second, whats your procedure for HiveOS when resetting/recovering from a “bad” overclock/underclock after a gpu crash?
@m2internet If we’re talking specifically 6600 XT and ETH, my procedure (if I start the OC from scratch) is always the same:
At this point you end up with a 6600 XT which will be pulling around 67W and do about 32MH. Any GPU crash will almost certainly be due to core voltage being set too low to accommodate occasional power spikes. This is where the R-mode in TRM comes handy, it really minimizes these spikes.
Wow, again … I can’t thank you enough for your time and detail in these posts. Truly helpful.
See my biggest problem I have is getting that old hashrate consistency back once I go back to a “working” overclock set/version (I write them all down, and version them in “Overclocking templates”). See you reboot your rig 15-20 times, guess my procedure isn’t so nuts.
Once a GPU crashes from a “bad” overclock my concern is getting the GPU’s back to a stable setting for their speed & voltages. On crash I would:
I figured this was overkill but I definitely noticed it took the GPU’s sometimes even pulling the power cords to get them to reset properly. I thought I was doing too much, but youre restarting 15-20 times in a row to do reset the GPU’s off a “bad” overclock as well.
Wish there was a more sidelined procedure tbh. So helpful to see how others are doing it. Thx again
@m2internet Interesting how different our approaches are. I never had to do any of the things you did. I’ve never used Maintenance mode, etc. My OC template for a 6600 XT literally just has 901 core clock and 418 SoC frequancy, that’s it. I set all other settings manually for each card. Whenever I had a mystery crash (as in, after days/weeks of stable work, GPU suddenly crashes out of nowhere), it was always a case of changing one of two values in the OC section. It was either:
I updated my AMD drivers and manually changed my tuning configs to “R”, but r-mode is not working.
What am I missing?
You’re missing the equal sign “=” after the word “eth_config”.
Do you make changes to your OC’s with the miner running? I have been trying both, but am accustomed to shutting down the miner first before my OC’s since using LOLminer. I do think you can perform the OC’s with the miner running, then it run stable for over 24hrs, but then on restart/reboot it would crash. So I’ve been performing the OC’s after i shutdown the miner…its more procedure, but def more accdurate/efficient.
You don’t actually need the"="
But I tried that too, no change.
It works fine with my “A” settings, but when I change "A"s to "R"s it auto-tunes. No errors, it just ignores all tuning configs.
Try setting “–kernel_vm_mode=RR” in the miner config, instead of “–eth_config” and see what happens
I got that working. So it’s now working in R mode with auto tuning. I think the rig had to reboot or something. Thank you!
Actually what was missing was almost certainly the entry “amdgpu.vm_block_size=11 amdgpu.vm_size=2048” in grub.custom file. This is described in the R-Mode tuning guide, line 70. What you needed to do, is issue this command in the shell:
echo -e “amdgpu.vm_block_size=11\namdgpu.vm_size=2048” > /hive/etc/grub.custom && selfupgrade --force -g && sreboot
But when you run TRM with “–kernel_vm_mode=RR” once, it does that change for you.
Either way, you can now use your previous “–eth_config=R480…” line.
Yes, you are correct. As always, thank you for the help.