Open hitmangk opened 1 year ago
I got the same issue with previous releases (my rig is off for now as i am moving house), but from i guessed/understood, it seems to be linked with power limit applied. Are you also using a power limit ? If yes, try to increase or remove it to test if your gpu(s) are following the offset you're requesting 🤷🏻♂️
Thank you for the suggestion, but I do not use power limit at all. Using the identical settings with version 1.9z5b works fine, but not with any version of 2.0x I would like to switch to the latest version to add some Zil mining, but as the core offsets are not applied, Flux mining is not efficient with those versions.
Hi hitmangk, thaneb, It is best not to mix the --gpuclock/memclock options (absolute value options) with the offset options. In any case we see that there is an issue with Ocs options, these don't seem to be applied. We only observe this with v2.0c4, though. We're having a look and working to fix this asap. Thank you for your feedback! Cheers
Thank you for looking into that topic. Only combination of gouclock and gpuoffset actually makes mining efficient. With the fixed gpuclock the offset changes the related voltage - so the higher offset can be set at a fixed gpuclock, the less power consumption the card achieves. I would really apprechiate, if it would work again like that
Since miniZ 2.0x version the gpuoffset does not apply on my 30XX series cards in windows, when mining FLUX , Only gpuclock and memclock do still apply.
Version 1.9z5b was able to set gpuoffset properly - why not anymore ?
Example from config: --gpuclock=1500 --gpuoffset=+300 --memclock=5001