search

hirschmann / nbfc

NoteBook FanControl
Other
2.89k stars 487 forks source link

ec-probe write doesn't change the value of a register #921

Closed ghost closed 3 years ago

ghost commented 4 years ago

Describe the bug Running any ec-probe write command seems to fail as a subsequent ec-probe read doesn't show the new value for some (but not all) registers.

To Reproduce On a Lenovo Legion Y530 with Windows 10 run ec-probe read 0xFE && ec-probe.exe write 0xFE 0x17 -v && ec-probe.exe read 0xFE (i.e. read, write, and read again) Expected output:

0 (0x00)
Writing at 254: 23 (0x17)
Current value at 254: 23 (0x17)
0 (0x00)

Expected behavior Expected output:

0 (0x00)
Writing at 254: 23 (0x17)
Current value at 254: 23 (0x17)
23 (0x17)

but instead getting Expected output:

0 (0x00)
Writing at 254: 23 (0x17)
Current value at 254: 23 (0x17)
0 (0x00)                                           <- this line here

System information

Additional context This seems to only be happening with registers 0x06 and 0xFE which I believe are the ones related to the fan speed (they are the only 2 registers to consistently change when the fan changes speed). Other registers seem to be okay with being written to. This leads me to believe that the registers are being affected by some other process on my machine, but I don't know what it could be. The CPU is an Intel i7-8750H and the laptop has a dedicated Nvidia GTX-1050Ti (mobile) as well as the onboard Intel UHD 630 graphics, so there's possibly something going on with those? I've read that Nvidia Optimus can mess with settings, but I am not currently running any games or other graphically intensive background tasks so this seems unlikely. I've additionally turned the preferred GPU to the Intel builtin one but that didn't change the results. None of the other common incompatibility programs are installed on my machine either.

Lamb3 commented 4 years ago

Curious. Why are you using NBFC? I don't recommend using it when you have those CPU and GPU. Also, I thought fan speeds for GTX Titan 10 series can be controlled via MSI Afterburner.

My guts say you're resorting to NBFC for lower temperatures but again, this software is not at all user-friendly and poses instability issues/risks to your laptop ie. sudden shutdown.

My solution and recommendations to you are to:

  1. Undervolt your CPU with Throttlestop under FIVR options.
  2. Undervolt GPU with MSI AB(as mentioned earlier). Fan controls (only for the GPU if you have independent fans for both CPU and GPU) can also be configured there if I'm not mistaken.

Those two combined will yield you 15 degrees Celcius drop in temperatures easily. I'm only resorting to NBFC because my GPU is a Maxwell GTX 980m in which the fan control is hard locked in the vBIOS even if I use Maxwell BIOS Tweaker to try and access it. So I can really only rely on the CPU fan to do the extra cooling (at least on the CPU side).

ghost commented 4 years ago

My issue isn't with temperatures - they seem to be mostly fine. The problem I have is that the fan curve is silly and I want to change it. When the temperature of the CPU rises rapidly (e.g. turboing when a new application is opened) the fan goes all the way up to 75% (which is annoyingly loud) and then drops down to a more sensible level around 30%. I'd like to change this behaviour to so that the fan doesn't spike so annoyingly high at first. This is something that I thought NBFC would be perfect for "fixing". Do you think this is something that undervolting would achieve?

I'm very new to this side of computing, so I'll have a proper look into MSI AB and Maxwell BIOS Tweaker. From what I gather, MSI AB is for GPU control rather than CPU so I don't think it will help with what I'm currently dealing with as my issue seems to be the CPU fans. The Maxwell BIOS Tweaker could unlock some CPU fan curves which aren't in the BIOS by default (even the advanced/secret BIOS doesn't seem to have proper fan controls which is a pain) so I will look into that and let you know findings.

github-actions[bot] commented 3 years ago

This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed