Showing posts with label fancontrol. Show all posts
Showing posts with label fancontrol. Show all posts

2011-09-02

Loud fans...again

Configuring fan speed using pwmconfig and fancontrol is not a big deal, normally. However, some problem can arise (see: "Loud fans...WHAT?"). Now it was running smoothly on my machine, but was not always working after a reboot.

Running sudo fancontrol brings up no noise reduction, but following message:

Not starting fancontrol, outdated configuration file; please re-run pwmconfig.
Running and restarting fancontrol helps, but it will eventually fail later, after some reboot.
A closer look to the /etc/fancontrol config file shows following (on my system):
INTERVAL=10
DEVPATH=hwmon0=devices/platform/w83627ehf.656
DEVNAME=hwmon0=w83627dhg
FCTEMPS=hwmon0/device/pwm2=hwmon0/device/temp2_input
FCFANS=hwmon0/device/pwm2=hwmon0/device/fan2_input
MINTEMP=hwmon0/device/pwm2=35
MAXTEMP=hwmon0/device/pwm2=65
MINSTART=hwmon0/device/pwm2=135
MINSTOP=hwmon0/device/pwm2=90
MINPWM=hwmon0/device/pwm2=90
MAXPWM=hwmon0/device/pwm2=255
When I run again pwmconfig, what I missed first was the number behind hwmon. This number changed, being sometime 0, sometime 1 after rebooting. Searching for this kind of problem brought up this interesting page with the solution.
This seems to happen quite often in relation with the k8temp module. Anyway, removing this module from /etc/modules and black-listing it in the file /etc/modprobe.d/blacklist.conf adding blacklist k8temp did the trick, and I can listen to music without vacuum cleaner noise in background.

2011-02-03

Loud fans... WHAT?


Before becoming deaf, I thought it would be a nice idea to check what can be done to slow down the fans. The good keywords are 'fancontrol' and 'pwmconfig'. With these, plenty of setup descriptions can be found.


To resume quickly:
  1. check what sensors you can use: sudo sensors-detect
  2. copy the drivers like indicated. A manual copy is better to avoid duplicate entries in your /etc/modules
  3. (optional) Some sudo modprobe work can be necessary if the drivers are not loaded
  4. now, a call to sudo pwmconfig will configure the fan speeds. Follow the proposed steps, it is well explained
  5. now the /etc/fancontrol file was created
  6. running sudo fancontrol & activates the fan speed regulation based on the settings made with pwmconfig

Unfortunately, executing the command sudo fancontrol & got me an error in /usr/sbin/fancontrol at line 402... Looking there, I was middle in a UpdateFanSpeed function, and one the the variables got invalid value. Since this section looks like it reads the settings made in the /etc/fancontrol file, I looked there. The problem could be solved easily using information from pwmconfig about what temperature sensor name to use, since this was missing.

The fan control worked once I corrected the /etc/fancontrol from
FCTEMPS= hwmon0/device/pwm2=
to
FCTEMPS= hwmon0/device/pwm2=hwmon0/device/temp1_input

Note that hwmon0/device/temp1_input was my preferred sensor, chosen based on the measured temperatures shown during pwnconfig set-up. This is probably only valid for my box.