From: Danny Kukawka <dkukawka-l3A5Bk7waGM@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: hp omnibook xe4500 fan control
Date: Mon, 27 Jun 2005 11:41:44 +0200 [thread overview]
Message-ID: <200506271141.45275.dkukawka@suse.de> (raw)
In-Reply-To: <42BE53EB.5050601-MhksZLCqGG5eoWH0uzbU5w@public.gmane.org>
On Sunday 26 June 2005 09:06, Thomas Perl wrote:
> I'm having a problem with HP's Omnibook XE4500.
>
> I cannot control the fan using its /proc/acpi interface. There is a fan
> entry and I can try to set some options, however - they are not set
> effectively (seems like Linux isn't in control of the fan). 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?
>
> There is a fan.exe on the diagnostic partition which switches the fan on
> and then off for diagnose purposes, so it _should_ be possible to
> control the fan by software.
Did you tried the omnibook kernel modules [1] ? They should also support the
XE4500.
Danny
[1] http://sourceforge.net/projects/omke/
--
Danny Kukawka
dkukawka-l3A5Bk7waGM@public.gmane.org
Mobile Devices
SUSE LINUX a Novell Business
Maxfeldstr. 5, D-90409 Nuernberg, Germany
-------------------------------------------------------
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 9:41 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
2005-06-27 9:41 ` Danny Kukawka [this message]
-- 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=200506271141.45275.dkukawka@suse.de \
--to=dkukawka-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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