From: Gabriel C <nix.or.die@googlemail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Gabriel C <crazy@frugalware.org>,
Maxim Levitsky <maximlevitsky@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>,
Andriy Gapon <avg@icyb.net.ua>
Subject: Re: [lm-sensors] Status/support for Linux HECI from Intel? (for temp/voltage monitoring)
Date: Mon, 4 Jan 2010 15:43:55 +0100 [thread overview]
Message-ID: <1820d69d1001040643h5e2f383bo7e077cbc2d2af554@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1001040921000.29475@p34.internal.lan>
2010/1/4 Justin Piszcz <jpiszcz@lucidpixels.com>:
>
>
> On Mon, 4 Jan 2010, Gabriel C wrote:
>
>>>>
>>>> Today I'm out from hospital so I've decided to quick hack this tool
>>>> and make it work on Linux.
>>>>
>>>> Here the output from my DQ45CB mobo:
>>>>
>>>> crazy@thor:~/INTEL/QST/Li$ sudo ./heci-qst
>>>> CPU Temp: 56.00 °C
>>>> MB Temp: 31.14 °C
>>>> ICH Temp: 67.37 °C
>>>> MCH Temp: 66.00 °C
>>>> CPU Fan: 1080 RPM
>>>> INL Fan: 1202 RPM
>>>> OUTL Fan: 288 RPM
>>>> +12 Volts: 11.965 V
>>>> +5 Volts: 5.021 V
>>>> +3.3 Volts: 3.316 V
>>>> MCH Vccp: 1.122 V
>>>> CPU1 Vccp: 1.125 V
>>>>
>>>> Justin I know is not based on released SDK of Intel but maybe you
>>>> still want to do some tests ?:)
>
> DMI Info:
>
> Handle 0x0004, DMI type 0, 24 bytes
> BIOS Information
> Vendor: Intel Corp.
> Version: MQ96510J.86A.1754.2008.1117.0002
>
> Handle 0x0006, DMI type 2, 20 bytes
> Base Board Information
> Manufacturer: Intel Corporation
> Product Name: DG965WH
> Version: AAD41692-304
>
> Cool, first time I have ever seen this =)
>
> # ./heci-qst-linux CPU Temp: 36.55 °C
> MB Temp: 38.75 °C
> MCH Temp: 33.89 °C
> 04: 64.90 °C
> 05: 46.25 °C
> CPU Fan: 836 RPM
> INL Fan: 1362 RPM
> OUTL Fan: 836 RPM
> AUX Fan: 2600 RPM
> +12 Volts: 12.029 V
> +5 Volts: 4.949 V
> +3.3 Volts: 3.247 V
> MCH Vccp: 1.260 V
> CPU1 Vccp: 1.180 V
>
> It appears to work.
>
> Thanks,
NP :)
Anyway It seems like ICH8* has some different output .. can't tell yet
without docs =)
Please open heci-qst-linux.c and find :
const char * const temp_names[THERM_SENSOR_COUNT] = {
...
Change to look like this :
const char * const temp_names[THERM_SENSOR_COUNT] = {
"CPU Temp",
"MB1 Temp",
NULL,
"MB2 Temp",
"ICH Temp",
"MCH Temp",
NULL,
NULL,
NULL,
NULL,
NULL,
NULL,
};
Also can you post a lspci -nn please :)
>
> Justin.
>
Gabriel
next prev parent reply other threads:[~2010-01-04 14:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 12:26 Justin Piszcz
2009-01-07 16:41 ` Dan Williams
2009-01-07 16:42 ` Justin Piszcz
2009-01-07 19:21 ` Maxim Levitsky
2009-02-12 1:35 ` [lm-sensors] " Gabriel C
2009-02-12 2:36 ` Joshua D Doll
2009-02-12 17:39 ` Justin Piszcz
2010-01-04 13:51 ` Gabriel C
2010-01-04 13:54 ` Justin Piszcz
2010-01-04 14:09 ` Gabriel C
2010-01-04 14:22 ` Justin Piszcz
2010-01-04 14:43 ` Gabriel C [this message]
2010-01-04 14:55 ` Justin Piszcz
2010-01-04 15:07 ` Gabriel C
2010-01-13 8:19 ` Andriy Gapon
2010-02-23 17:56 ` Gabriel C
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=1820d69d1001040643h5e2f383bo7e077cbc2d2af554@mail.gmail.com \
--to=nix.or.die@googlemail.com \
--cc=avg@icyb.net.ua \
--cc=crazy@frugalware.org \
--cc=dan.j.williams@intel.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=maximlevitsky@gmail.com \
/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
Powered by JetHome