From: Andrew Haninger <ahaning-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: thp-MhksZLCqGG5eoWH0uzbU5w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: hp omnibook xe4500 fan control
Date: Sun, 26 Jun 2005 22:52:18 -0400 [thread overview]
Message-ID: <105c793f050626195219bb787c@mail.gmail.com> (raw)
In-Reply-To: <42BE53EB.5050601-MhksZLCqGG5eoWH0uzbU5w@public.gmane.org>
On 6/26/05, Thomas Perl <thp-MhksZLCqGG5eoWH0uzbU5w@public.gmane.org> wrote:
> I'd like to set the trip_points to some values so that the fan doesn't
> come on so often. Any hints on where to start? Or it is not possible
> on Linux anyway?
FWIW, here are the lines I use to turn the fan on and off on my
Gateway SOLO 2500 (~5-6 years old so it requires acpi=force in the
boot parameters):
This one makes the fan turn on when the CPU is at 20degC (so, all the
time since it idles around 30degC):
echo "80:0:70:20:0" > /proc/acpi/thermal_zone/THRM/trip_points
This one makes the fan turn on when the CPU is at 60degC; so only
under with long CPU-intensive stuff (default):
echo "80:0:70:60:0" > /proc/acpi/thermal_zone/THRM/trip_points
This turns on the fan immediately:
echo 0 > /proc/acpi/fan/FAN/state
This turns off the fan immediately:
echo 3 > /proc/acpi/fan/FAN/state
I don't know why you echo 3 to turn off the fan and 0 to turn on the
fan and not 0 to turn off the fan and 1 to turn on the fan; or, better
"on" and "off". That's what works for me. I have these in tiny scripts
so I don't have to remember them.
They don't always work, though, so sometimes I have to run my script
to turn on the fan, then the one to turn off the fan, and then the one
to turn on the fan to get the fan to turn on. Very confusing, but it
works.
Hope this helps.
-Andy
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
next prev parent reply other threads:[~2005-06-27 2:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 7:06 hp omnibook xe4500 fan control Thomas Perl
[not found] ` <42BE53EB.5050601-MhksZLCqGG5eoWH0uzbU5w@public.gmane.org>
2005-06-27 2:52 ` Andrew Haninger [this message]
2005-06-27 9:41 ` Danny Kukawka
-- strict thread matches above, loose matches on Subject: below --
2005-06-27 1:35 Li, Shaohua
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=105c793f050626195219bb787c@mail.gmail.com \
--to=ahaning-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=thp-MhksZLCqGG5eoWH0uzbU5w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox