From: Ian Pilcher <arequipeno@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Temperature sensors changed by BIOS update
Date: Thu, 11 Oct 2012 00:46:01 +0000 [thread overview]
Message-ID: <k554s3$g79$1@ger.gmane.org> (raw)
At least I think that the BIOS update is the cause. (I'm not willing
to risk downgrading my BIOS to be absolutely sure.)
The system in question is an Intel DQ67SW board, using the lm_sensors
configuration file here:
http://lm-sensors.org/wiki/Configurations/Intel/DQ67SW
Today, I noticed that gkrellm was reporting my CPU temperature as
-128°C. The temperature mappings in that file (which I created about
18 months ago) are:
temp1: Memory DIMM Temperature
temp2: VR Temperature
temp3: Processor Temperature
temp4: PCH Temperature
It seems that the correct mappings are now:
temp1 (SYSTIN) : Memory DIMM Temperature (no change)
temp2 (CPUTIN) : VR Temperature (no change)
temp3 (AUXTIN) : (always reports -128°C)
temp6 (PECI Agent 0) : Processor Temperature
temp7 (PCH_CHIP_TEMP): PCH Temperature
temp8 (PECI Agent 1) : (always reports 0.0°C)
temp4 and temp5 don't exist at all!
Does it make sense that a BIOS update could have this effect? If so, I
guess I'll submit an updated configuration file that's only applicable
to boards with more recent BIOS revs.
Thanks!
--
========================================================================
Ian Pilcher arequipeno@gmail.com
"Sometimes there's nothing left to do but crash and burn, or die trying"
========================================================================
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2012-10-11 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 0:46 Ian Pilcher [this message]
2012-10-11 3:27 ` [lm-sensors] Temperature sensors changed by BIOS update Guenter Roeck
2012-10-11 5:56 ` Ian Pilcher
2012-10-11 8:33 ` Guenter Roeck
2012-11-03 18:23 ` Ian Pilcher
2012-11-18 10:48 ` Jean Delvare
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='k554s3$g79$1@ger.gmane.org' \
--to=arequipeno@gmail.com \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.