Talk:NVIDIA/Tips and tricks
Set fan speed at login
Shouldn't this section be changed to use GPUTargetFanSpeed instead of GPUCurrentFanSpeed as this is the current working method? The note that is currently present explaining the change is very easy to miss.
Allow change to highest Performance Mode
Any other way of "overclocking" won't change the Memory Transfer Rate offset (it has no effect in nvidia-settings).
see https://devtalk.nvidia.com/default/topic/1010856/linux/how-to-force-performance-level-3-driver-381-22-with-gtx-1080-ti-/ and https://devtalk.nvidia.com/default/topic/977467/cuda-setup-and-installation/having-trouble-overclocking-gtx-1070/ and also https://devtalk.nvidia.com/default/topic/1014710/linux/understanding-weirdness-with-gpumemorytransferrateoffset-/
Setting the clockspeed rates in nvidia-settings without prior adjusting the rates in nvidia-smi crashes really hard, because it tries to overclock max. performance mode which only is active when the card is idle (i.e. just after exiting a game or a miner...).
default clock speed + overclocking = max. default clock speed or crash
"set" clock speed + overclocking = more than max. default clock speed and memory transfer rate tunable
This is a bug.
Pointing out the fact that this is not my website, why did you delete the Watt-Limiting Section? (My) GTX 960 is not kepler, changing wattage works though? Man pages lie!
- In the threads you've linked, these two posts support the claim that setting application clocks (with
nvidia-smi -ac) is not available on "ordinary" GPUs. So how do you make a general section out of this?
- Setting the application clocks to something listed in
nvidia-smi -q -d SUPPORTED_CLOCKSis not an overclocking. If there is a bug in the performance modes, the section should properly explain it and provide all references.
- -- Lahwaacz (talk) 09:22, 23 August 2017 (UTC)