Thinkpads Forum

comps wrote:First, the fan speed control should be automatic. My R60 used to run on high fan RPM because of the GPU had improper drivers and was overheating.

As for ecdump, it was removed - http://lkml.org/lkml/2010/7/1/206 . The entire /proc interface has been obsolete for a long time and it's scheduled for removal at some point in the future.

ThinkRob wrote:

comps wrote:First, the fan speed control should be automatic. My R60 used to run on high fan RPM because of the GPU had improper drivers and was overheating.

Agreed. I only use tp-fancontrol for my machine because the automatic fan control won't shut off the fan even if the CPU is plenty cool.

As for ecdump, it was removed - http://lkml.org/lkml/2010/7/1/206 . The entire /proc interface has been obsolete for a long time and it's scheduled for removal at some point in the future.

Yep. My script checks for its existence, but I just realized that on kernels older than, say, Lenny's (which I tested it on) that check is useless.

Ah well. I suppose I should revise that script anyways...

Niila wrote:

Code: Select all

# sh fancontrolscript
: not found
: not found
: not found

gzip -d tpfanctl.sh.gz
chmod +x tpfanctl.sh

Niila wrote:

Code: Select all

: Directory nonexistente /sys/devices/platform/thinkpad_hwmon/pwm1_enable

options thinkpad_acpi experimental=1 fan_control=1

modprobe -r thinkpad_acpi
modprobe thinkpad_acpi

ThinkRob wrote:Alright, comps, you've convinced me: I think I'm going to update fanctrld to use the sysfs interface. I prefer small C daemons to shell scripts anyways, and it's only a couple hundred lines. Plus I should have a bit more control over how many wakeups it generates...

Niila wrote:One more thing, any idea how to show current fan level in my conky?

Fan level: ${execi 5 sh -c "echo $(( ($(cat /sys/devices/platform/thinkpad_hwmon/pwm1) >> 5) & 0x07 ))"}

Fan level: ${execi 5 $(( ($(cat /sys/devices/platform/thinkpad_hwmon/pwm1) >> 5) & 0x07 ))}

Niila wrote:Is there a way specify fan speeds for each level? Like say level 1 would be 2500 and level 2 3000? I noticed that fan1_input shows the speed..

 *      Bits
 *       7      automatic mode engaged;
 *              (default operation mode of the ThinkPad)
 *              fan level is ignored in this mode.
 *       6      full speed mode (takes precedence over bit 7);
 *              not available on all thinkpads.  May disable
 *              the tachometer while the fan controller ramps up
 *              the speed (which can take up to a few *minutes*).
 *              Speeds up fan to 100% duty-cycle, which is far above
 *              the standard RPM levels.  It is not impossible that
 *              it could cause hardware damage.
 *      5-3     unused in some models.  Extra bits for fan level
 *              in others, but still useless as all values above
 *              7 map to the same speed as level 7 in these models.
 *      2-0     fan level (0..7 usually)
 *                      0x00 = stop
 *                      0x07 = max (set when temperatures critical)
 *              Some ThinkPads may have other levels, see
 *              TPACPI_FAN_WR_ACPI_FANS (X31/X40/X41)

comps wrote: Sure, there are many ways to make the script/daemon more efficient, like using poll()/select() or even *notify kernel subsystem. ... or hacking thinkpad_acpi.c

ThinkRob wrote:Currently fanctrld wakes once every couple seconds, which isn't a big deal. I'm not sure inotify would help that actually, as I'm not sure how often the sysfs interface gets updated.

The path instability isn't a big deal, as it'd be trivial to change that as required (provided the format doesn't bounce around too.)

And I'm resisting the urge to mess with thinkpad_acpi.c. Kernel hacking is fun, and I love doing it, but userspace<->kernel coupling is bad, and IMHO fan control is definitely something that should be done out-of-kernel.