From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Capello Subject: Re: Unable to turn fan on - Asus M3N - 2.6.0-test9bk4 Date: Sun, 02 Nov 2003 20:58:47 +0100 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <3FA561F7.5030706@pca.it> References: <20031101193817.GA19198@austinchronicle.com> <20031102174730.GB2819@krikkit> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20031102174730.GB2819-duT3ICHXG/I@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: ML ACPI-devel List-Id: linux-acpi@vger.kernel.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/