Re: [ACPI-sppt] fan speed control techniques (again)
Ducrot Bruno <[email protected]>
| Newsgroups | gmane.linux.acpi.support |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Jul 08, 2003 at 05:11:42PM -0400, Emma Jane Hogbin wrote: > http://www.analog.com/library/analogDialogue/archives/34-04/fan/ > I thought this was an interesting article. I'm not sure how much of it has > been implemented in the Linux stuff, but it was pretty easy to read. (Yes, > it's old.) I noticed that it said my fan shouldn't be turned on until 60C, > but the fan is currently on at: > > emmajane@debian:~$ acpi -t > Thermal 1: ok, 54.0 degrees C > Thermal 2: ok, 49.0 degrees C > > I noticed in a patch changelog that I found that: > <[email protected]> > ACPI: Fix thermal management and make trip points R/W (Pavel Machek > http://www.linuxhq.com/kernel/changelog/v2.5/42/ > Does this mean that the "trip points" don't work with the 2.4.20 patched > kernel and that's why the fan is on at the wrong time? > > Related acpi-support threads: > http://sourceforge.net/mailarchive/forum.php?thread_id=2725927&forum_id=7803 > having the BIOS control the fan Ah, the asus. I just got one asl btw. Seems to be interresting... > > http://sourceforge.net/mailarchive/forum.php?thread_id=2713262&forum_id=7803 > SpeedStep settings > My system was configured to "automatic" but is now configured to use > "battery". The fan is still on at the following temperatures: > > emmajane@debian:~$ acpi -t > Thermal 1: ok, 51.0 degrees C > Thermal 2: ok, 46.0 degrees C > > Does anyone know if this is because I'm using an old kernel + patch? Or is > there something else I've missed? > > thanks, > emma :) > > emmajane@debian:~$ cat /proc/acpi/processor/CPU0/info > processor id: 0 > acpi id: 1 > bus mastering control: yes > power management: yes > throttling control: yes > performance management: yes > limit interface: yes > emmajane@debian:~$ cat /proc/acpi/processor/CPU0/limit > active limit: P0:T0 > platform limit: P0:T0 > user limit: P0:T0 > thermal limit: P0:T0 > emmajane@debian:~$ cat /proc/acpi/processor/CPU0/performance > state count: 2 > active state: P0 > states: > *P0: 1800 MHz, 0 mW, 250 uS > P1: 1200 MHz, 0 mW, 250 uS > emmajane@debian:~$ cat /proc/acpi/processor/CPU0/ > info limit performance power throttling > emmajane@debian:~$ cat /proc/acpi/processor/CPU0/power > active state: C2 > default state: C1 > bus master activity: ffffffff > states: > C1: promotion[C2] demotion[--] latency[000] > usage[00025440] > *C2: promotion[C3] demotion[C1] latency[020] > usage[00794979] > C3: promotion[--] demotion[C2] latency[200] > usage[00000000] > emmajane@debian:~$ cat /proc/acpi/processor/CPU0/throttling > state count: 8 > active state: T0 > states: > *T0: 00% > T1: 12% > T2: 25% > T3: 37% > T4: 50% > T5: 62% > T6: 75% > T7: 87% > > > > emmajane@debian:~$ cat /proc/acpi/thermal_zone/THRS/cooling_mode > cooling mode: active > > emmajane@debian:~$ cat /proc/acpi/thermal_zone/THRS/polling_frequency > <polling disabled> Try to echo 300 > polling_frequency Then passvie via polling will be *really* activated. > > emmajane@debian:~$ cat /proc/acpi/thermal_zone/THRS/state > state: ok > > emmajane@debian:~$ cat /proc/acpi/thermal_zone/THRS/temperature > temperature: 48 C > > emmajane@debian:~$ cat /proc/acpi/thermal_zone/THRS/trip_points > critical (S5): 92 C > passive: 80 C: tc1=2 tc2=5 tsp=300 devices=0xc12c5a40 There is a 'magical' thing in order to change the 80C, but I do not remember the exact syntax. Should be documented somewhere (at least in the source :) > > (all THRC values are the same except the following) > emmajane@debian:~$ cat /proc/acpi/thermal_zone/THRC/temperature > temperature: 45 C Same. You may want to really activate passive mode via polling by echoing to polling_frequency. Cheers, -- Ducrot Bruno -- Which is worse: ignorance or apathy? -- Don't know. Don't care. ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps