From: enlight1 <enlight1-H+0wwilmMs3R7s880joybQ@public.gmane.org>
To: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Help with thermal
Date: Mon, 16 Aug 2004 21:42:35 -0700 [thread overview]
Message-ID: <1092717755.4491.18.camel@localhost.localdomain> (raw)
In-Reply-To: <20040816073231.GB2861@fuchi>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
On Mon, 2004-08-16 at 00:32, Sebastian Henschel wrote:
> > The thermal_zone directory is empty.
> >
> > How do I read temperatures? I have been reading the howto's but I am
> > missing something here. Thermal is compiled into kernel, not a module.
>
> it might be that your DSDT does not define a thermal_zone. you can send
> it to the list if you like to, or better send a link to it. check
> http://acpi.sf.net/dsdt/index.php to learn how to extract that table.
> or your DSDT is faulty which should be shown in the output of "dmesg".
> are there any AE_* messages or similar errors which point to ACPI?
> or the ACPI implementation of Lіnux is at fault.
> which machine are you running, btw?
I am running an Intel D865GLC motherboard. Fedora Core 2 distribution.
Kernel 2.6.8.1. No errors indicating a DSDT problem in DMESG. I am
running this in SMP mode. I found this line in DMESG.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel P4/Xeon Extended MCE MSRs (12) available
>>> CPU1: Thermal monitoring enabled
CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
The attached dsdt file was in /proc/acpi directory.
Jerry
[-- Attachment #2: dsdt --]
[-- Type: application/octet-stream, Size: 16855 bytes --]
prev parent reply other threads:[~2004-08-17 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 23:40 Help with thermal Jerry DeLisle
[not found] ` <1092613221.10652.9.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2004-08-16 7:32 ` Sebastian Henschel
2004-08-17 4:42 ` enlight1 [this message]
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=1092717755.4491.18.camel@localhost.localdomain \
--to=enlight1-h+0wwilmms3r7s880joybq@public.gmane.org \
--cc=acpi-1rjuZeEg9oEb1SvskN2V4Q@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