You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fancontrol-gui APP actually just populates a text file /etc/fancontrol. I've noticed that the fancontrol-gui app has been generating an invalid fancontrol file.
FIRST BE SURE TO FIRST USE THE FANCONTROL-GUI APP to GENERATE A CONFIG.
If done properly you will see something similar to the one I have below.
Check if fancontrol.service is actually enabled and running?
As you can see, it's enabled, but failing to start because of a failed device path. $ sudo systemctl status fancontrol.service
× fancontrol.service - Start fan control, if configured
Loaded: loaded (/usr/lib/systemd/system/fancontrol.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Mon 2023-01-16 10:22:12 MST; 3s ago
Duration: 118ms
Process: 114665 ExecStart=/usr/sbin/fancontrol (code=exited, status=1/FAILURE)
Main PID: 114665 (code=exited, status=1/FAILURE)
CPU: 203ms
Jan 16 10:22:12 arch-workstation fancontrol[114665]: MAXTEMP=47
Jan 16 10:22:12 arch-workstation fancontrol[114665]: MINSTART=255
Jan 16 10:22:12 arch-workstation fancontrol[114665]: MINSTOP=0
Jan 16 10:22:12 arch-workstation fancontrol[114665]: MINPWM=0
Jan 16 10:22:12 arch-workstation fancontrol[114665]: MAXPWM=255
Jan 16 10:22:12 arch-workstation fancontrol[114665]: AVERAGE=1
Jan 16 10:22:12 arch-workstation fancontrol[114665]: Device path of hwmon12 has changed
Jan 16 10:22:12 arch-workstation fancontrol[114665]: Configuration appears to be outdated, please run pwmconfig again
Jan 16 10:22:12 arch-workstation systemd[1]: fancontrol.service: Main process exited, code=exited, status=1/FAILURE
Jan 16 10:22:12 arch-workstation systemd[1]: fancontrol.service: Failed with result 'exit-code'.
Take a look at /etc/fancontrol and see if it is missing the line break:
Fancontrol-gui APP actually just populates a text file
/etc/fancontrol
. I've noticed that the fancontrol-gui app has been generating an invalidfancontrol
file.FIRST BE SURE TO FIRST USE THE FANCONTROL-GUI APP to GENERATE A CONFIG.
If done properly you will see something similar to the one I have below.
Check if fancontrol.service is actually enabled and running?
As you can see, it's enabled, but failing to start because of a failed device path.
$ sudo systemctl status fancontrol.service
Take a look at
/etc/fancontrol
and see if it is missing the line break:Here's the config file fixed:
Restart the service:
$ sudo systemctl restart fancontrol.service
Here it is working:
$ sudo systemctl status fancontrol.service
This fix allows my fan curves to work, but breaks the ability to use the fancontrol-gui app as it will complain the config file is wrong.
The text was updated successfully, but these errors were encountered: