Again & again. Some clarifications for AMD drivers that used in Hive
AMD drivers consist of two parts:
OpenCL is a CUDA-like library used in Nvidia GPUs. Unfortunately, starting from version 20.45 and higher, the library is unbalanced and some cards lost support (for example Vega), others did not win in any way in terms of hashrate. Therefore, many mining systems and Hive also use the 20.40
On the other hand, support directly at a low level (consider overclocking) is provided by the kernel-level driver, and it is almost identical to latest in the official package from AMD.
FYI, I made an upgrade on ver.@211030 and set up SoC VDDmax for all RX6800 cards at 800mV. In the result, -15W / card on power usage (real consumption ‘from the wall’), it’s a VERY pleasant change :]. Everything is rock stable, after few days I will try to go lower. Hashrate is ± the same, I lost approx. 0.1Mhs per card in the result.
I don’t think he’s referring to the 20.40 vs 20.45 difference, but thanks for this info anyway!
@esoooo
.0701 is hiveos stable
.0825 is hiveos beta
You can go from stable to beta and vice versa with hive-replace. Go to root commando line and type: hive-replace -y --list
and choose between versions.
Warning, your rig password will be reset with this so you need to set it up again!
with my oc settings it didnt worth on 0.6-211 after this update it fluctuates between 57 and 61mhs, i get 63mh/s on Hiveos ver 0.6-210 with f state tweak
Registers for GDDR6 memory on read-only state. So you can’t change timings on the fly.
Anyway, it would be good to view your code modification and verify it with memory timings.
But this is happening only when new dag is generated for short time. Also in NiceHash. And maybe the reason is infinity cache because when new dag is generated you use light dag.
This works so well for me - thanks for the share!
Tried it on both my XFX and my AMD/ATI cards and its works with no significant diff in hashrate. Let us know how it goes at lower mV