search

Lurkki14 / tuxclocker

Qt overclocking tool for GNU/Linux
GNU General Public License v3.0
776 stars 31 forks source link

Memory clock keeps setting to +1000 and fan speed does not climb or drop #34

Open alexboutros opened 4 years ago

alexboutros commented 4 years ago

I'm currently using a fan profile to go from 0% speed at 0C to 100% speed at 80C. Fan mode in the dropdown is set to custom. When I watch the monitor tab the fan speed never changes from 23%. Also when I enter the fan curve editor and press save it changes my Memory Clock Offset from +500 to +1000.

Why is this happening?

Lurkki14 commented 4 years ago

Are you on the latest version on git?

theschoolmaster commented 3 years ago

I'm seeing the same issue with the memory clocks. I'm not using the fan speed settings so no idea there.

This happens with both current git master and the last release 0.1.1. I think I know what's happening. You're storing the Memory Clock Offset in .config/tuxclocker.conf as the raw offset (2x what's shown on the slider). And when switching back to the card it loads this 2x version instead of the 1/2 raw offset. I tested by setting my offsets to 400 (instead of 650) and it reports 800 on switch back.

Let me know if you'd like me to test anything else out. This is on Debian with nvidia driver 460.32 and 4 GTX 1070's.

Dal78 commented 2 years ago

Yeah i get this doubling too.

Does anyone know the nvidia-smi method to set the voltage offsets? This is the only too i can find to apply my +112 mv voltage offset to reach parity with my windows setup so i can carry my settings over?

Tried to also use the cli version of this but didnt get any life out of it