Your message dated Mon, 11 Aug 2008 21:28:16 -0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#486022: acpi: Wrongly displaying thermal 0 temperature
has caused the Debian Bug report #486022,
regarding acpi: Wrongly displaying thermal 0 temperature
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
486022: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486022
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: acpi
Version: 0.09-7
Severity: normal
Hi!
acpi is having a strange behavior here; it seems that it only updates
the thermal 0 info after I do a cat to
/proc/acpi/thermal_zone/THM/temperature
See:
$ acpi -V
Battery 1: Full, 100%
Thermal 0: ok, 64.5 degrees C
AC Adapter 1: on-line
$ cat /proc/acpi/thermal_zone/THM/temperature
temperature: 41 C
$ acpi -V
Battery 1: Full, 100%
Thermal 0: ok, 40.5 degrees C
AC Adapter 1: on-line
If I start some heavy jobs and wait a little to raise the temperature,
it isn't updated unless I do another cat.
It also is displaying the temp as a real number, and not as an integer
(40.5 instead 41, for example).
What can I do to help, please?
Thanl you!
Best regards,
Nelson
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-naoliv1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages acpi depends on:
ii libc6 2.7-12 GNU C Library: Shared libraries
acpi recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
I was almost forgetting about this. Sorry.
It has been fixed with Kernel 2.6.26, so I am closing this bug.
Thank you very much!
Best regards,
Nelson
--- End Message ---
