From: Robert Kaiser <kairo@kairo.at>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] RFC: nct6776f support in the w83627ehf and fan
Date: Fri, 11 Mar 2011 00:04:55 +0000 [thread overview]
Message-ID: <ilbov7$95f$1@dough.gmane.org> (raw)
In-Reply-To: <BE6F61DB46364D4B839ED3F50CDFDFAB@portable2>
Guenter Roeck schrieb:
> Agreed. But you might be able to see the DIMM temperatures (if you have DDR3)
> by loading the "jc42" module.
Hmm, doesn't seem to work, after loading jc43, I don't see anything new
appearing in sensors output.
> Actually, I just had a look at the code again. Turns out there is a bug; you see
> the labels associated with NCT6776F, not NCT6775F. Real values should be "PECI Agent 0"
> instead of "SMBUSMASTER 1", "PECI Agent 1" instead of "SMBUSMASTER 2",
> and "PCH_CHIP_TEMP" instead of "PCH_CHIP_CPU_MAX_TEMP". I'll fix that immediately.
Ah, that makes sense, even if it's interesting that the PCH Chip is so
much hotter than the CPU, but then it doesn't have a fan attached to it
and still enough work, so sounds reasonable. And "PECI Agent 0" being
similar to the values from coretemp is also probably reasonable, as IIRC
PECI means something similar to that, right?
> So the temperatures you see as "SMBUSxxx" are really temperatures reported by the CPU.
> Just don't ask me why the CPU would report 0 degrees C ;).
The i7-2600K is just an incredibly cool CPU, I guess. ;-)
Robert Kaiser
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2011-03-11 0:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-06 12:38 [lm-sensors] RFC: nct6776f support in the w83627ehf and fan RPM Ian Dobson
2011-03-06 17:07 ` Guenter Roeck
2011-03-06 17:21 ` Ian Dobson
2011-03-06 18:47 ` Guenter Roeck
2011-03-06 19:40 ` Ian Dobson
2011-03-06 20:05 ` Guenter Roeck
2011-03-07 2:50 ` Robert Kaiser
2011-03-07 5:21 ` Guenter Roeck
2011-03-07 14:59 ` Robert Kaiser
2011-03-07 16:03 ` Guenter Roeck
2011-03-10 0:25 ` Robert Kaiser
2011-03-10 3:45 ` Guenter Roeck
2011-03-10 5:06 ` Guenter Roeck
2011-03-10 5:20 ` [lm-sensors] RFC: nct6776f support in the w83627ehf and fan Ian Dobson
2011-03-10 11:35 ` Guenter Roeck
2011-03-10 11:53 ` Guenter Roeck
2011-03-10 11:57 ` I.dobson
2011-03-10 13:10 ` I.dobson
2011-03-10 17:32 ` Guenter Roeck
2011-03-10 20:05 ` Robert Kaiser
2011-03-10 20:08 ` [lm-sensors] RFC: nct6776f support in the w83627ehf and fan RPM Robert Kaiser
2011-03-10 20:27 ` [lm-sensors] RFC: nct6776f support in the w83627ehf and fan Ian Dobson
2011-03-10 21:03 ` Robert Kaiser
2011-03-10 22:11 ` Guenter Roeck
2011-03-10 22:15 ` Guenter Roeck
2011-03-10 23:17 ` Robert Kaiser
2011-03-10 23:38 ` Guenter Roeck
2011-03-11 0:04 ` Robert Kaiser [this message]
2011-03-11 0:29 ` Guenter Roeck
2011-03-11 0:58 ` Robert Kaiser
2011-03-11 1:07 ` Guenter Roeck
2011-03-11 17:09 ` Robert Kaiser
2011-03-11 17:47 ` Guenter Roeck
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='ilbov7$95f$1@dough.gmane.org' \
--to=kairo@kairo.at \
--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.