From: Martin Suchanek <martin.suc@googlemail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
Date: Sat, 28 Apr 2012 10:48:37 +0000 [thread overview]
Message-ID: <CAGqf2iJjfzYN2UbRnicf=_8Nf22x0Y6YSAUeHr4hCm4bUVjSNg@mail.gmail.com> (raw)
In-Reply-To: <CAGqf2i+bMvvWyELKn5ApTL+XUQ_s7x-eMCSV4DdNGhpfuHy6nA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1250 bytes --]
On Sat, Apr 28, 2012 at 11:22 AM, Jean Delvare <khali@linux-fr.org> wrote:
> On Sat, 28 Apr 2012 11:08:23 +0100, Martin Suchanek wrote:
> > On Sat, Apr 28, 2012 at 5:30 AM, Guenter Roeck
> > <guenter.roeck@ericsson.com>wrote:
> > > The answer is quite simple - the board get the CPU temperature using
> PECI,
> > > which the w83627ehf/nct67765 driver reports is as "PECI Agent 0".
> > > Open Hardware Monitor maps that temperature into the CPU temperature
> > > display
> > > and ignores CPUTIN. Which makes sense, since the purpose of PECI is to
> > > report
> > > the CPU temperature.
> > >
> > > So all you need to do is to ignore the value of CPUTIN and use the
> "PECI
> > > Agent 0"
> > > temperature instead.
> >
> > I am now confused ?
> > I do not know technical details but according to ASUS technical support
> > CPUTIN is temperature of motherboard (not cpu socket , not cpu yourself )
> > what exactly this temperature means ?
>
> Labels are suggestions from the chip maker, unfortunately board vendors
> are free to not follow these suggestions and wire the inputs
> differently. Confusion ensues...
>
> :-) ok ,so now I am definitely confused. From now I do not know how is it
on my motherboard in real ? :-)
> --
> Jean Delvare
>
[-- Attachment #1.2: Type: text/html, Size: 2041 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2012-04-28 10:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 13:09 [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus iv e Martin Suchanek
2012-04-14 21:58 ` [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus Guenter Roeck
2012-04-20 10:47 ` Martin Suchanek
2012-04-20 15:22 ` Guenter Roeck
2012-04-21 9:38 ` Martin Suchanek
2012-04-21 14:49 ` Guenter Roeck
2012-04-21 15:04 ` Martin Suchanek
2012-04-28 4:30 ` Guenter Roeck
2012-04-28 6:43 ` P.B. V
2012-04-28 8:55 ` Jean Delvare
2012-04-28 10:08 ` Martin Suchanek
2012-04-28 10:22 ` Jean Delvare
2012-04-28 10:48 ` Martin Suchanek [this message]
2012-04-28 14:43 ` Guenter Roeck
2012-04-28 15:00 ` Guenter Roeck
2012-04-28 15:36 ` Guenter Roeck
2012-04-28 19:30 ` Guenter Roeck
2012-04-28 23:18 ` Martin Suchanek
2012-04-28 23:41 ` Guenter Roeck
2012-04-29 9:42 ` Martin Suchanek
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='CAGqf2iJjfzYN2UbRnicf=_8Nf22x0Y6YSAUeHr4hCm4bUVjSNg@mail.gmail.com' \
--to=martin.suc@googlemail.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.