Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor (-m) flag modifies fan speed on exit #29

Closed
koitsu opened this issue Dec 21, 2020 · 5 comments
Closed

Monitor (-m) flag modifies fan speed on exit #29

koitsu opened this issue Dec 21, 2020 · 5 comments
Labels

Comments

@koitsu
Copy link

koitsu commented Dec 21, 2020

When using -m -j on Windows, upon exiting the program (Ctrl-C), the fan speeds are reset to 0. In other words: -m isn't just "pure monitoring". When using -d, I can clearly see at the end the message Resetting fan control (I suspect this is the cause).

I'm using the version provided here since I have an RTX GPU (in contrast, 0.5.0 crashes).

Testing methodology:

  1. Launch EVGA Precision X1 and set fan speed to 44%. Verify fan RPMs are around 1674 or so.
  2. Run nvcontrol -m -j -- fan speeds look fine (still 44%).
  3. SIGINT/Ctrl-C nvcontrol -- instantly fan speeds drop to 0 and stasy that way until Precision X1 is re-run. (This EVGA card's BIOS, by default, actually turns off the fans entirely if a certain load isn't met)

System details: Windows 7 SP1 x64 with an NVIDIA RTX 2060 SUPER (EVGA RTX 2060 Super SC Ultra Black Gaming, model 08G-P4-3065-KR).

@foucault foucault changed the title Windows: Monitor (-m) flag modifies fan speed on exit Monitor (-m) flag modifies fan speed on exit Dec 21, 2020
@foucault foucault added the bug label Dec 21, 2020
@foucault
Copy link
Owner

Hello! This seems common to windows and linux so I removed windows from title. I suspect this happens because nvfancontrol will put the fan back to automatic control when exiting. Since your fans are managed by an external tool (which uses manual control too) setting it back to automatic will revert to the default behaviour of the GPU's firmware, which is probably to turn off the fan under some load/temperature combination. Can you confirm that by loading the GPU enough to trigger the fan without using X1 and then using monitor mode? It should not affect the automatic operation at all.

I believe a better solution would be not to touch anything related to the fans if running in monitor mode. Should be relatively straightforward.

@koitsu
Copy link
Author

koitsu commented Dec 21, 2020

I suspect this happens because nvfancontrol will put the fan back to automatic control when exiting. Since your fans are managed by an external tool (which uses manual control too) setting it back to automatic will revert to the default behaviour of the GPU's firmware, which is probably to turn off the fan under some load/temperature combination. Can you confirm that by loading the GPU enough to trigger the fan without using X1 and then using monitor mode? It should not affect the automatic operation at all.

I did exactly as you've asked -- your theory is correct.

I believe a better solution would be not to touch anything related to the fans if running in monitor mode. Should be relatively straightforward.

I concur that this would be the correct solution. I suspect the code for this should be quite easy. Thank you!

@foucault
Copy link
Owner

I think I fixed it. Give it a try!

nvfancontrol-rtx.zip

@koitsu
Copy link
Author

koitsu commented Dec 22, 2020

I can confirm this fixes the problem. Thank you so much!

@foucault
Copy link
Owner

The fix is now in master, will be in the new release whenever that happens.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants