9/28/2023 0 Comments Linux fancontrol fails to startWhich will reload the nf's set variables. You have to figure out for yourself which one it is, but it's probably 1, 2 or 3. Replace the X with the number of your CPU fan's, for me that was 2. Add the line fanX_div 4 near the start of your chipset config. The names all look alike, so make sure the one you are editing is yours. $ sudo cp /etc/nf /etc/nf_originalĪnd look up your exact chipset. The first line of the sensors output is the chipset your motherboard uses to read the speeds/temps/voltages. If your fan speed is shown and higher than 0, skip the next step. If your output does not display an RPM for your CPU fan, and you are positive it is running, you need to increase the fan divisor. The fan can run so slowly and quietly, because it's a large 12 cm fan made by Zalman (it's the 7000B AlCu). The CPU temp is a little high, so I need to do some tweaking of the config there. Notice that my CPU fan is running really slowly, only 1100 RPM. Once you have lm-sensors installed, you should have a readout with 'sensors' That's for Warty, but still works under Dapper (and Hoary). If you are not comfortable with doing this, don't!įirst, you need to set up lm-sensors. A CPU fan is needed to cool your CPU and in this howto it will be turned off for a couple of seconds. This is the updated, new and improved version!)Ĭontrolling the speed (and sound!) of your CPU fan is easy!ĭisclaimer: this can ruin your hardware. There still seems to be one problem: when fancontrol was unable to start up (due to the missing modules or the incorrect device number), it displayed "" instead of "".(Original thread is here (), but it got snowed under. I reran pwmconfig to generate a new /etc/fancontrol file, and now fancontrol starts up correctly. The /etc/fancontrol configuration file that pwmconfig generated was configured to use the hwmon1 device, which formerly was the real device "platform/w83627ehf.656", but now was the real device "platform/coretemp.0". Lrwxrwxrwx 1 root root 0 21:56 hwmon3 -> ~]$ /devices/platform/coretemp.1/hwmon/hwmon2 Lrwxrwxrwx 1 root root 0 21:56 hwmon2 ->. /devices/platform/coretemp.0/hwmon/hwmon1 Lrwxrwxrwx 1 root root 0 21:56 hwmon1 ->. Lrwxrwxrwx 1 root root 0 21:56 hwmon0 ->. When they were loaded from rc.local, the devices were numbered this ~]$ ls -alt /sys/class/hwmon/ Lrwxrwxrwx 1 root root 0 22:12 hwmon0 -> ~]$ Lrwxrwxrwx 1 root root 0 22:12 hwmon1 ->. /devices/platform/coretemp.1/hwmon/hwmon3 Lrwxrwxrwx 1 root root 0 22:12 hwmon3 ->. /devices/platform/coretemp.0/hwmon/hwmon2 Lrwxrwxrwx 1 root root 0 22:12 hwmon2 ->. When the modules were loaded from rc.local, the hwmon devices were numbered this ~]$ ls -alt /sys/class/hwmon/ The problem when loading modules from rc.conf was that the hwmon devices were numbered differently in sysfs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |