public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Vollmert <rvollmert-hi6Y0CQ0nG0@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: digitale-eFwX6J65rk/J8bqQQ1YlwQ@public.gmane.org
Subject: Re: Shuttle SB61G2 fan speed
Date: Wed, 8 Oct 2003 11:25:21 +0200	[thread overview]
Message-ID: <20031008092521.GA994@krikkit> (raw)
In-Reply-To: <E1A73Nv-0001M5-68-6vcCkRnH9/iXl4vLVl4uKAC/G2K4zDHf@public.gmane.org>

Hello,

On Tue, Oct 07, 2003 at 09:45:03PM -0400, Eric Northup wrote:
> I have a Shuttle mini-PC currently running linux 2.6-test6 (but I have
> seen this issue w/all kernels I've tried, 2.4.x and 2.5.x).  It has a
> "smart" fan control, which regulates the speed of the system fan
> according to the temperature (a Thermal Zone in ACPI terms, yes?).  The
> problem is: as soon as Linux gets control from GRUB, the fan goes to
> full speed and stays there.

I assume you've enabled ACPI? To what extent does it work? I.e. are
there errors in dmesg (try compiling with debug support?), what parts
of /proc/acpi appear functional (temperature, fan)?

If it sort of works, it could be an issue with the DSDT. Check
acpi.sf.net for information on how to extract this.

There might also be some BIOS options that affect this. In particular,
a few sites seem to suggest problems with certain APIC options.

> I have flashed the BIOS to the latest (which claimed to fix a fan speed
> problem with Windows), but the problem persists.  So I don't know if it
> is a case of pilot error, a Linux bug, or a BIOS bug.  Any help sorting
> this out would be much appreciated :)

Shuttle seem to be quite supportive of Linux from what I can tell by
checking their web site. So if this turns out to be a BIOS/DSDT
problem, maybe you could get them to update it.

Cheers
Robert


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  parent reply	other threads:[~2003-10-08  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08  1:45 Shuttle SB61G2 fan speed Eric Northup
     [not found] ` <E1A73Nv-0001M5-68-6vcCkRnH9/iXl4vLVl4uKAC/G2K4zDHf@public.gmane.org>
2003-10-08  8:58   ` Ducrot Bruno
2003-10-08  9:25   ` Robert Vollmert [this message]
2003-10-09 20:10   ` =?unknown-8bit?Q?=C9ric?= Brunet
  -- strict thread matches above, loose matches on Subject: below --
2003-10-08 18:09 Eric Northup
     [not found] ` <E1A7IkI-0004qc-8W-6vcCkRnH9/iXl4vLVl4uKAC/G2K4zDHf@public.gmane.org>
2003-10-08 22:55   ` Robert Vollmert
2003-10-09 19:03   ` Ducrot Bruno

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=20031008092521.GA994@krikkit \
    --to=rvollmert-hi6y0cq0ng0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=digitale-eFwX6J65rk/J8bqQQ1YlwQ@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