| 1 |
On 9/16/06, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
> Hi All, |
| 3 |
> |
| 4 |
> Every time the fan on my laptop starts I get this in the log: |
| 5 |
> |
| 6 |
> ACPI event unhandled: thermal_zone TZ1 00000081 00000000 |
| 7 |
> |
| 8 |
> The fan works fine with respect to automatically switching on at two different |
| 9 |
> speeds when the CPU gets hot/hotter and switching down/off when the CPU cools |
| 10 |
> down enough. |
| 11 |
> |
| 12 |
> How is the thermal_zone message explained - why is it there? |
| 13 |
|
| 14 |
Thermal zone events are caused when one of the temperature monitors in |
| 15 |
the system notices that its temp has crossed some threshold. In your |
| 16 |
case, the reaction to this event is to turn on (or speed up) a fan, |
| 17 |
but you also get notified of this through the acpi event reporting |
| 18 |
mechanism in acpid. |
| 19 |
|
| 20 |
So this is exactly the same problem/solution as your power button |
| 21 |
issue. In /etc/acpi/default.sh, you have an etry: |
| 22 |
|
| 23 |
*) log_unhandled $* ;; |
| 24 |
|
| 25 |
This causes anything that is not "button" or "ac_adapter" to log an |
| 26 |
event unhandled message. So here again, add a case _above_ this for |
| 27 |
what you want to happen when thermal_zone events occur. In this case, |
| 28 |
maybe just: |
| 29 |
|
| 30 |
thermal_zone) |
| 31 |
;; # don't care..fan seems to work |
| 32 |
|
| 33 |
Of course, you could get fancy. Looks like the first argument might |
| 34 |
be the temperature at which the event occurs, so you could for example |
| 35 |
compare that to some value (>100?) and do something like go ahead and |
| 36 |
log the event as overtemp. You could even do an automatic shutdown if |
| 37 |
it gets too hot. But that probably isn't necessary, as thermal |
| 38 |
throttling should kick in before any damage can occur to the CPU. |
| 39 |
|
| 40 |
-Richard |
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives