![]() ProcVersionSign ature: Ubuntu 5.3.0-62.56-generic 5.3. So the bug is just that fancontrol and pwmconfig scripts are not able to read the FCFANS value they generated in case of more than one fan by "pwm" ! I checked what I have under "/sys/class/ hwmon/", everything is fine: I can find all hwmon/fan and pwm items formerly detected by pwmconfig. The generated path with '+' doesn't exist, hence pwmconfig test scripts and fancontrol service should split the path using '+' as separator char to recover right paths to fanX_input files. On my computer, hwmon2 is coretemp-related, and hwmon2/pwm2 is controlling 4 fans. This kind of value is generated when more than one fan is found on the same hwmonX/pwmY. The error occurring during PWM value test is due to this wrong path value with '+' sign. ![]() ![]() "FCFANS= hwmon2/ pwm2=hwmon2/ fan4_input+ hwmon2/ fan3_input+ hwmon2/ fan2_input hwmon2/ pwm1=hwmon2/ fan1_input" which is exactly the FCFANS value in /etc/fancontrol: If you ask pwmconfig to show the generated config, you can readĬontrols hwmon2/ fan4_input+ hwmon2/ fan3_input+ hwmon2/ fan2_input" usr/sbin/ pwmconfig: ligne 717 : [: -gt : opérateur unaire attendu" "cat: hwmon2/ fan4_input+ hwmon2/ fan3_input+ hwmon2/ fan2_input: Aucun fichier ou dossier de ce type ![]() 5 thoughts on LM sensors on a Gigabyte H97-D3H motherboard Aug 05. If you answer 't' when promptedĪt which the fan STOPS spinning (press t to test) (100):" Location of temp sensor X570 Aorus pro wifi Im trying to set up the fans in my. When running pwmconfig, after the detection step you can configure min/max temp. WARNING, the package reported by ubuntu-bug is "lm-sensors", but pwmconfig and fancontrol are installed by "fancontrol" package. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |