public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Capello <luca-wlebWZzHoyE@public.gmane.org>
To: ML ACPI-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Unable to turn fan on - Asus M3N - 2.6.0-test9bk4
Date: Sun, 02 Nov 2003 20:58:47 +0100	[thread overview]
Message-ID: <3FA561F7.5030706@pca.it> (raw)
In-Reply-To: <20031102174730.GB2819-duT3ICHXG/I@public.gmane.org>

Hello,

on 11/02/03 18:47, Robert Vollmert wrote:
> are you sure the fan doesn't turn on? What kind of temperatures have
> you been seing? As Karol noted, the fan isn't controlled the way the
> spec intends (which would require implementing n fan devices for an
> n-level fan, I think). Instead, TCHG is called every time the
> temperature changes, which sets the fan speed directly based on some
> threshold temperatures which vary based on cooling mode
> (active/passive). That's the only place you can take influence wihtout
> modifying the DSDT, though changing the mode to passive will increase
> the thresholds. IIRC, these temperatures are quite high, though I don't
> remember exact values. In the region of 70°C, for the lowest, I think.
I think the fan is correctly managed, as you can see from my attached:
=====
luca@gismo:~$ cat /proc/acpi/thermal_zone/THRM/temperature
temperature:             68 C
luca@gismo:~$ date
Sun Nov  2 20:50:06 CET 2003
luca@gismo:~$ cat /proc/acpi/thermal_zone/THRM/temperature
temperature:             55 C
luca@gismo:~$ date
Sun Nov  2 20:52:44 CET 2003
luca@gismo:~$ cat /proc/acpi/fan/FN00/state
status:                  on
luca@gismo:~$ cat /proc/acpi/fan/FN00/state
status:                  off
luca@gismo:~$
=====

The temperature went high compiling the kernel, but suddenly the fan 
went on and at high RPM (I could hear it), just for 5min and then it 
went normal again.

I have always the 'os_wait_semaphore' problem, but, as Karol said in 
another post, this doens't cause any big problems, just the already 
reported keyboard bug (for less than 5min you can't type anything or if 
you were typing sometimes it's as if you go on typing the last character).

Thx, bye,
Gismo / Luca



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

  parent reply	other threads:[~2003-11-02 19:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-01 19:38 Unable to turn fan on - Asus M3N - 2.6.0-test9bk4 Lindsey Simon
     [not found] ` <20031101193817.GA19198-lfYnT2qr6k+7/ODoCphcOEEOCMrvLtNR@public.gmane.org>
2003-11-02 17:47   ` Robert Vollmert
     [not found]     ` <20031102174730.GB2819-duT3ICHXG/I@public.gmane.org>
2003-11-02 19:58       ` Luca Capello [this message]
     [not found]         ` <3FA561F7.5030706-wlebWZzHoyE@public.gmane.org>
2003-11-04 17:32           ` Lindsey Simon
     [not found]             ` <20031104173216.GH26114-lfYnT2qr6k+7/ODoCphcOEEOCMrvLtNR@public.gmane.org>
2003-11-13 17:36               ` Luca Capello

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=3FA561F7.5030706@pca.it \
    --to=luca-wlebwzzhoye@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