* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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 ` Guenter Roeck
2012-04-20 10:47 ` Martin Suchanek
` (17 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-14 21:58 UTC (permalink / raw)
To: lm-sensors
On Sat, Apr 14, 2012 at 09:09:59AM -0400, Martin Suchanek wrote:
> Hi,
>
> I have found for long time ago that CPUTIN temperature is not showed correctly
> by sensors command:
>
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0: +34.0°C (high = +80.0°C, crit = +98.0°C)
> Core 0: +30.0°C (high = +80.0°C, crit = +98.0°C)
> ...
> nct6776-isa-0290
> Adapter: ISA adapter
> ...
> CPUTIN: -60.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
> ...
>
> I have cheked it in BIOS and in AI Suite in windows 7 64 bit and consulted it
> with ASUS technical support and everything is working properly.
> So , hardware is fine. Software in windows is fine. Only linux software is not
> correct.
> I have tried to detect-sensor many times and it is still the same.
> If there is some kind of tweak in config please let me know but it seems to me
> there is something wrong with lm-sensors 3.3.1.
>
> ...
> Intel digital thermal sensor... Success!
> (driver `coretemp')
> ...
> Found `Nuvoton NCT6776F Super IO Sensors' Success!
> ...
> Driver `w83627ehf':
> * ISA bus, address 0x290
> Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
>
> Driver `coretemp':
> * Chip `Intel digital thermal sensor' (confidence: 9)
> ...
>
> my /etc/modules:
> ...
> coretemp
> w83627ehf
> ...
>
> This error have appeared on maximus iv extreme motherboard Revision 3 , BIOS
> from 1404 to 3202 (latest)
> linux ubuntu natty -> oneiric 64 bit kernel from 2.6.39 up to 3.0.0-19
> commercial version (tested on 3.3.1 compiled by me)
>
> Could you please help me to solve it ?
>
CPUTIN with NCT6776F is kind of problematic. It shows up wrong on many (but not all) boards.
On some boards, the displayed temperature even decreases as the CPU temperature increases.
There may be some magic configuration setting which need to be fixed, but I have not been
able to find out what those would be.
I have a new experimental driver for NCT6775F and NCT6776F at https://github.com/groeck/nct6775,
in case you want to give it a try. With this driver, it is possible to set the temperature sensor type
(1, 3, or 4). It doesn't help with my P8H67-V board for any of the possible settings, but maybe
you are more lucky.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (16 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Martin Suchanek @ 2012-04-20 10:47 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 2341 bytes --]
Hi,
Add info:
I have found software called open hardware monitor. I have been testing it
in windows for couple of days and it works properly with Nuvoton NST6776F
chip. I have been comparing results with AI Suite software coming from ASUS
and results are corresponding and measuring is with big precise. So , you
can have a look to source code and compare with your driver. This software
should work on linux as well but I did not try it yet but I will.
(I did not tried your experimental driver yet but I will)
Regards,
Martin
On Sat, Apr 14, 2012 at 2:09 PM, Martin Suchanek
<martin.suc@googlemail.com>wrote:
> Hi,
>
> I have found for long time ago that CPUTIN temperature is not showed
> correctly by sensors command:
>
> coretemp-isa-0000
> Adapter: ISA adapter
> Physical id 0: +34.0°C (high = +80.0°C, crit = +98.0°C)
> Core 0: +30.0°C (high = +80.0°C, crit = +98.0°C)
> ...
> nct6776-isa-0290
> Adapter: ISA adapter
> ...
> CPUTIN: -60.0°C (high = +80.0°C, hyst = +75.0°C) sensor = diode
> ...
>
> I have cheked it in BIOS and in AI Suite in windows 7 64 bit and consulted
> it with ASUS technical support and everything is working properly.
> So , hardware is fine. Software in windows is fine. Only linux software is
> not correct.
> I have tried to detect-sensor many times and it is still the same.
> If there is some kind of tweak in config please let me know but it seems
> to me there is something wrong with lm-sensors 3.3.1.
>
> ...
> Intel digital thermal sensor... Success!
> (driver `coretemp')
> ...
> Found `Nuvoton NCT6776F Super IO Sensors' Success!
> ...
> Driver `w83627ehf':
> * ISA bus, address 0x290
> Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
>
> Driver `coretemp':
> * Chip `Intel digital thermal sensor' (confidence: 9)
> ...
>
> my /etc/modules:
> ...
> coretemp
> w83627ehf
> ...
>
> This error have appeared on maximus iv extreme motherboard Revision 3 ,
> BIOS from 1404 to 3202 (latest)
> linux ubuntu natty -> oneiric 64 bit kernel from 2.6.39 up to 3.0.0-19
> commercial version (tested on 3.3.1 compiled by me)
>
> Could you please help me to solve it ?
>
> Thank you very much for any clue.
> Kind Regards,
> Martin
>
[-- Attachment #1.2: Type: text/html, Size: 2753 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
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (15 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-20 15:22 UTC (permalink / raw)
To: lm-sensors
T24gRnJpLCAyMDEyLTA0LTIwIGF0IDA2OjQ3IC0wNDAwLCBNYXJ0aW4gU3VjaGFuZWsgd3JvdGU6
Cj4gSGksCj4gCj4gQWRkIGluZm86Cj4gSSBoYXZlIGZvdW5kIHNvZnR3YXJlIGNhbGxlZCBvcGVu
IGhhcmR3YXJlIG1vbml0b3IuIEkgaGF2ZSBiZWVuCj4gdGVzdGluZyBpdCBpbiB3aW5kb3dzIGZv
ciBjb3VwbGUgb2YgZGF5cyBhbmQgaXQgd29ya3MgcHJvcGVybHkgd2l0aAo+IE51dm90b24gTlNU
Njc3NkYgY2hpcC4gSSBoYXZlIGJlZW4gY29tcGFyaW5nIHJlc3VsdHMgd2l0aCBBSSBTdWl0ZQo+
IHNvZnR3YXJlIGNvbWluZyBmcm9tIEFTVVMgYW5kIHJlc3VsdHMgYXJlIGNvcnJlc3BvbmRpbmcg
YW5kIG1lYXN1cmluZwo+IGlzIHdpdGggYmlnIHByZWNpc2UuIFNvICwgeW91IGNhbiBoYXZlIGEg
bG9vayB0byBzb3VyY2UgY29kZSBhbmQKPiBjb21wYXJlIHdpdGggeW91ciBkcml2ZXIuIFRoaXMg
c29mdHdhcmUgc2hvdWxkIHdvcmsgb24gbGludXggYXMgd2VsbAo+IGJ1dCBJIGRpZCBub3QgdHJ5
IGl0IHlldCBidXQgSSB3aWxsLgo+IAo+IChJIGRpZCBub3QgdHJpZWQgeW91ciBleHBlcmltZW50
YWwgZHJpdmVyIHlldCBidXQgSSB3aWxsKQo+IApNYXJ0aW4sCgpwbGVhc2UgZG9uJ3QgdG9wLXBv
c3QuCgpXaGF0IGlzIHRoZSBvdXRwdXQgeW91IGdldCB3aXRoIG9wZW4gaGFyZHdhcmUgbW9uaXRv
ciA/IFRoZXkgcmVwb3J0IGZvdXIKdGVtcGVyYXR1cmVzLCBQRUNJXzAsIENQVVRJTiwgQVVYVElO
LCBhbmQgU1lTVElOLgoKVGhhbmtzLApHdWVudGVyCgo+IFJlZ2FyZHMsCj4gTWFydGluCj4gCj4g
Cj4gT24gU2F0LCBBcHIgMTQsIDIwMTIgYXQgMjowOSBQTSwgTWFydGluIFN1Y2hhbmVrCj4gPG1h
cnRpbi5zdWNAZ29vZ2xlbWFpbC5jb20+IHdyb3RlOgo+ICAgICAgICAgSGksCj4gICAgICAgICAK
PiAgICAgICAgIEkgaGF2ZSBmb3VuZCBmb3IgbG9uZyB0aW1lIGFnbyB0aGF0IENQVVRJTiB0ZW1w
ZXJhdHVyZSBpcyBub3QKPiAgICAgICAgIHNob3dlZCBjb3JyZWN0bHkgYnkgc2Vuc29ycyBjb21t
YW5kOgo+ICAgICAgICAgCj4gICAgICAgICBjb3JldGVtcC1pc2EtMDAwMAo+ICAgICAgICAgQWRh
cHRlcjogSVNBIGFkYXB0ZXIKPiAgICAgICAgIFBoeXNpY2FsIGlkIDA6ICArMzQuMMKwQyAgKGhp
Z2ggPSArODAuMMKwQywgY3JpdCA9ICs5OC4wwrBDKQo+ICAgICAgICAgQ29yZSAwOiAgICAgICAg
ICszMC4wwrBDICAoaGlnaCA9ICs4MC4wwrBDLCBjcml0ID0gKzk4LjDCsEMpCj4gICAgICAgICAu
Li4KPiAgICAgICAgIG5jdDY3NzYtaXNhLTAyOTAKPiAgICAgICAgIEFkYXB0ZXI6IElTQSBhZGFw
dGVyCj4gICAgICAgICAuLi4KPiAgICAgICAgIENQVVRJTjogICAgICAgIC02MC4wwrBDICAoaGln
aCA9ICs4MC4wwrBDLCBoeXN0ID0gKzc1LjDCsEMpCj4gICAgICAgICBzZW5zb3IgPSBkaW9kZQo+
ICAgICAgICAgLi4uCj4gICAgICAgICAKPiAgICAgICAgIEkgaGF2ZSBjaGVrZWQgaXQgaW4gQklP
UyBhbmQgaW4gQUkgU3VpdGUgaW4gd2luZG93cyA3IDY0IGJpdAo+ICAgICAgICAgYW5kIGNvbnN1
bHRlZCBpdCB3aXRoIEFTVVMgdGVjaG5pY2FsIHN1cHBvcnQgYW5kIGV2ZXJ5dGhpbmcgaXMKPiAg
ICAgICAgIHdvcmtpbmcgcHJvcGVybHkuIAo+ICAgICAgICAgU28gLCBoYXJkd2FyZSBpcyBmaW5l
LiBTb2Z0d2FyZSBpbiB3aW5kb3dzIGlzIGZpbmUuIE9ubHkgbGludXgKPiAgICAgICAgIHNvZnR3
YXJlIGlzIG5vdCBjb3JyZWN0Lgo+ICAgICAgICAgSSBoYXZlIHRyaWVkIHRvIGRldGVjdC1zZW5z
b3IgbWFueSB0aW1lcyBhbmQgaXQgaXMgc3RpbGwgdGhlCj4gICAgICAgICBzYW1lLgo+ICAgICAg
ICAgSWYgdGhlcmUgaXMgc29tZSBraW5kIG9mIHR3ZWFrIGluIGNvbmZpZyBwbGVhc2UgbGV0IG1l
IGtub3cKPiAgICAgICAgIGJ1dCBpdCBzZWVtcyB0byBtZSB0aGVyZSBpcyBzb21ldGhpbmcgd3Jv
bmcgd2l0aCBsbS1zZW5zb3JzCj4gICAgICAgICAzLjMuMS4KPiAgICAgICAgIAo+ICAgICAgICAg
Li4uCj4gICAgICAgICBJbnRlbCBkaWdpdGFsIHRoZXJtYWwgc2Vuc29yLi4uCj4gICAgICAgICBT
dWNjZXNzIQo+ICAgICAgICAgICAgIChkcml2ZXIgYGNvcmV0ZW1wJykKPiAgICAgICAgIC4uLgo+
ICAgICAgICAgRm91bmQgYE51dm90b24gTkNUNjc3NkYgU3VwZXIgSU8gU2Vuc29ycycKPiAgICAg
ICAgIFN1Y2Nlc3MhCj4gICAgICAgICAuLi4KPiAgICAgICAgIERyaXZlciBgdzgzNjI3ZWhmJzoK
PiAgICAgICAgICAgKiBJU0EgYnVzLCBhZGRyZXNzIDB4MjkwCj4gICAgICAgICAgICAgQ2hpcCBg
TnV2b3RvbiBOQ1Q2Nzc2RiBTdXBlciBJTyBTZW5zb3JzJyAoY29uZmlkZW5jZTogOSkKPiAgICAg
ICAgIAo+ICAgICAgICAgRHJpdmVyIGBjb3JldGVtcCc6Cj4gICAgICAgICAgICogQ2hpcCBgSW50
ZWwgZGlnaXRhbCB0aGVybWFsIHNlbnNvcicgKGNvbmZpZGVuY2U6IDkpCj4gICAgICAgICAuLi4K
PiAgICAgICAgIAo+ICAgICAgICAgbXkgL2V0Yy9tb2R1bGVzOgo+ICAgICAgICAgLi4uCj4gICAg
ICAgICBjb3JldGVtcAo+ICAgICAgICAgdzgzNjI3ZWhmCj4gICAgICAgICAuLi4KPiAgICAgICAg
IAo+ICAgICAgICAgVGhpcyBlcnJvciBoYXZlIGFwcGVhcmVkIG9uIG1heGltdXMgaXYgZXh0cmVt
ZSBtb3RoZXJib2FyZAo+ICAgICAgICAgUmV2aXNpb24gMyAsIEJJT1MgZnJvbSAxNDA0IHRvIDMy
MDIgKGxhdGVzdCkKPiAgICAgICAgIGxpbnV4IHVidW50dSBuYXR0eSAtPiBvbmVpcmljIDY0IGJp
dCBrZXJuZWwgZnJvbSAyLjYuMzkgdXAgdG8KPiAgICAgICAgIDMuMC4wLTE5IGNvbW1lcmNpYWwg
dmVyc2lvbiAodGVzdGVkIG9uIDMuMy4xIGNvbXBpbGVkIGJ5IG1lKQo+ICAgICAgICAgCj4gICAg
ICAgICBDb3VsZCB5b3UgcGxlYXNlIGhlbHAgbWUgdG8gc29sdmUgaXQgPwo+ICAgICAgICAgCj4g
ICAgICAgICBUaGFuayB5b3UgdmVyeSBtdWNoIGZvciBhbnkgY2x1ZS4KPiAgICAgICAgIEtpbmQg
UmVnYXJkcywKPiAgICAgICAgIE1hcnRpbgo+IAo+IAoKCgpfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXwpsbS1zZW5zb3JzIG1haWxpbmcgbGlzdApsbS1zZW5z
b3JzQGxtLXNlbnNvcnMub3JnCmh0dHA6Ly9saXN0cy5sbS1zZW5zb3JzLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2xtLXNlbnNvcnM
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (2 preceding siblings ...)
2012-04-20 15:22 ` Guenter Roeck
@ 2012-04-21 9:38 ` Martin Suchanek
2012-04-21 14:49 ` Guenter Roeck
` (14 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Martin Suchanek @ 2012-04-21 9:38 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 3429 bytes --]
I have had in mind CPUTIN which is showing in lm-sensors -60 Celsius.
( it is all described more detailed in my previous posts.)
Just small info :-)
On Fri, Apr 20, 2012 at 4:22 PM, Guenter Roeck
<guenter.roeck@ericsson.com>wrote:
> On Fri, 2012-04-20 at 06:47 -0400, Martin Suchanek wrote:
> > Hi,
> >
> > Add info:
> > I have found software called open hardware monitor. I have been
> > testing it in windows for couple of days and it works properly with
> > Nuvoton NST6776F chip. I have been comparing results with AI Suite
> > software coming from ASUS and results are corresponding and measuring
> > is with big precise. So , you can have a look to source code and
> > compare with your driver. This software should work on linux as well
> > but I did not try it yet but I will.
> >
> > (I did not tried your experimental driver yet but I will)
> >
> Martin,
>
> please don't top-post.
>
> What is the output you get with open hardware monitor ? They report four
> temperatures, PECI_0, CPUTIN, AUXTIN, and SYSTIN.
>
> Thanks,
> Guenter
>
> > Regards,
> > Martin
> >
> >
> > On Sat, Apr 14, 2012 at 2:09 PM, Martin Suchanek
> > <martin.suc@googlemail.com> wrote:
> > Hi,
> >
> > I have found for long time ago that CPUTIN temperature is not
> > showed correctly by sensors command:
> >
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Physical id 0: +34.0°C (high = +80.0°C, crit = +98.0°C)
> > Core 0: +30.0°C (high = +80.0°C, crit = +98.0°C)
> > ...
> > nct6776-isa-0290
> > Adapter: ISA adapter
> > ...
> > CPUTIN: -60.0°C (high = +80.0°C, hyst = +75.0°C)
> > sensor = diode
> > ...
> >
> > I have cheked it in BIOS and in AI Suite in windows 7 64 bit
> > and consulted it with ASUS technical support and everything is
> > working properly.
> > So , hardware is fine. Software in windows is fine. Only linux
> > software is not correct.
> > I have tried to detect-sensor many times and it is still the
> > same.
> > If there is some kind of tweak in config please let me know
> > but it seems to me there is something wrong with lm-sensors
> > 3.3.1.
> >
> > ...
> > Intel digital thermal sensor...
> > Success!
> > (driver `coretemp')
> > ...
> > Found `Nuvoton NCT6776F Super IO Sensors'
> > Success!
> > ...
> > Driver `w83627ehf':
> > * ISA bus, address 0x290
> > Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
> >
> > Driver `coretemp':
> > * Chip `Intel digital thermal sensor' (confidence: 9)
> > ...
> >
> > my /etc/modules:
> > ...
> > coretemp
> > w83627ehf
> > ...
> >
> > This error have appeared on maximus iv extreme motherboard
> > Revision 3 , BIOS from 1404 to 3202 (latest)
> > linux ubuntu natty -> oneiric 64 bit kernel from 2.6.39 up to
> > 3.0.0-19 commercial version (tested on 3.3.1 compiled by me)
> >
> > Could you please help me to solve it ?
> >
> > Thank you very much for any clue.
> > Kind Regards,
> > Martin
> >
> >
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 4526 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
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (3 preceding siblings ...)
2012-04-21 9:38 ` Martin Suchanek
@ 2012-04-21 14:49 ` Guenter Roeck
2012-04-21 15:04 ` Martin Suchanek
` (13 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-21 14:49 UTC (permalink / raw)
To: lm-sensors
On Sat, Apr 21, 2012 at 05:38:54AM -0400, Martin Suchanek wrote:
> I have had in mind CPUTIN which is showing in lm-sensors -60 Celsius.
> ( it is all described more detailed in my previous posts.)
> Just small info :-)
>
I understand, but since the chip supports variable sensor mapping it would help
to know the other readings in comparison.
... and please don't top-post.
Thanks,
Guenter
> On Fri, Apr 20, 2012 at 4:22 PM, Guenter Roeck <guenter.roeck@ericsson.com>
> wrote:
>
> On Fri, 2012-04-20 at 06:47 -0400, Martin Suchanek wrote:
> > Hi,
> >
> > Add info:
> > I have found software called open hardware monitor. I have been
> > testing it in windows for couple of days and it works properly with
> > Nuvoton NST6776F chip. I have been comparing results with AI Suite
> > software coming from ASUS and results are corresponding and measuring
> > is with big precise. So , you can have a look to source code and
> > compare with your driver. This software should work on linux as well
> > but I did not try it yet but I will.
> >
> > (I did not tried your experimental driver yet but I will)
> >
> Martin,
>
> please don't top-post.
>
> What is the output you get with open hardware monitor ? They report four
> temperatures, PECI_0, CPUTIN, AUXTIN, and SYSTIN.
>
> Thanks,
> Guenter
>
> > Regards,
> > Martin
> >
> >
> > On Sat, Apr 14, 2012 at 2:09 PM, Martin Suchanek
> > <martin.suc@googlemail.com> wrote:
> > Hi,
> >
> > I have found for long time ago that CPUTIN temperature is not
> > showed correctly by sensors command:
> >
> > coretemp-isa-0000
> > Adapter: ISA adapter
> > Physical id 0: +34.0°C (high = +80.0°C, crit = +98.0°C)
> > Core 0: +30.0°C (high = +80.0°C, crit = +98.0°C)
> > ...
> > nct6776-isa-0290
> > Adapter: ISA adapter
> > ...
> > CPUTIN: -60.0°C (high = +80.0°C, hyst = +75.0°C)
> > sensor = diode
> > ...
> >
> > I have cheked it in BIOS and in AI Suite in windows 7 64 bit
> > and consulted it with ASUS technical support and everything is
> > working properly.
> > So , hardware is fine. Software in windows is fine. Only linux
> > software is not correct.
> > I have tried to detect-sensor many times and it is still the
> > same.
> > If there is some kind of tweak in config please let me know
> > but it seems to me there is something wrong with lm-sensors
> > 3.3.1.
> >
> > ...
> > Intel digital thermal sensor...
> > Success!
> > (driver `coretemp')
> > ...
> > Found `Nuvoton NCT6776F Super IO Sensors'
> > Success!
> > ...
> > Driver `w83627ehf':
> > * ISA bus, address 0x290
> > Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
> >
> > Driver `coretemp':
> > * Chip `Intel digital thermal sensor' (confidence: 9)
> > ...
> >
> > my /etc/modules:
> > ...
> > coretemp
> > w83627ehf
> > ...
> >
> > This error have appeared on maximus iv extreme motherboard
> > Revision 3 , BIOS from 1404 to 3202 (latest)
> > linux ubuntu natty -> oneiric 64 bit kernel from 2.6.39 up to
> > 3.0.0-19 commercial version (tested on 3.3.1 compiled by me)
> >
> > Could you please help me to solve it ?
> >
> > Thank you very much for any clue.
> > Kind Regards,
> > Martin
> >
> >
>
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (4 preceding siblings ...)
2012-04-21 14:49 ` Guenter Roeck
@ 2012-04-21 15:04 ` Martin Suchanek
2012-04-28 4:30 ` Guenter Roeck
` (12 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Martin Suchanek @ 2012-04-21 15:04 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 4756 bytes --]
> On Sat, Apr 21, 2012 at 05:38:54AM -0400, Martin Suchanek wrote:
> > I have had in mind CPUTIN which is showing in lm-sensors -60 Celsius.
> > ( it is all described more detailed in my previous posts.)
> > Just small info :-)
> >
> I understand, but since the chip supports variable sensor mapping it would
> help
> to know the other readings in comparison.
>
Other readings is correct - differencing by max one/two degrees Celsius
depend on measuring frequency. Only CPUTIN has always minus 60 Celsius
(from the May 2011 when I have installed linux with lm-sensors). I compared
those values in windows 7 64 bit by AI Suite with BIOS monitor if you meant
something like this. Or if you have some particular interest - some other
comparisons - let me know I can do it.
>
>
> > On Fri, Apr 20, 2012 at 4:22 PM, Guenter Roeck <
> guenter.roeck@ericsson.com>
> > wrote:
> >
> > On Fri, 2012-04-20 at 06:47 -0400, Martin Suchanek wrote:
> > > Hi,
> > >
> > > Add info:
> > > I have found software called open hardware monitor. I have been
> > > testing it in windows for couple of days and it works properly with
> > > Nuvoton NST6776F chip. I have been comparing results with AI Suite
> > > software coming from ASUS and results are corresponding and
> measuring
> > > is with big precise. So , you can have a look to source code and
> > > compare with your driver. This software should work on linux as
> well
> > > but I did not try it yet but I will.
> > >
> > > (I did not tried your experimental driver yet but I will)
> > >
> > Martin,
> >
> > please don't top-post.
> >
> > What is the output you get with open hardware monitor ? They report
> four
> > temperatures, PECI_0, CPUTIN, AUXTIN, and SYSTIN.
> >
> > Thanks,
> > Guenter
> >
> > > Regards,
> > > Martin
> > >
> > >
> > > On Sat, Apr 14, 2012 at 2:09 PM, Martin Suchanek
> > > <martin.suc@googlemail.com> wrote:
> > > Hi,
> > >
> > > I have found for long time ago that CPUTIN temperature is
> not
> > > showed correctly by sensors command:
> > >
> > > coretemp-isa-0000
> > > Adapter: ISA adapter
> > > Physical id 0: +34.0°C (high = +80.0°C, crit = +98.0°C)
> > > Core 0: +30.0°C (high = +80.0°C, crit = +98.0°C)
> > > ...
> > > nct6776-isa-0290
> > > Adapter: ISA adapter
> > > ...
> > > CPUTIN: -60.0°C (high = +80.0°C, hyst = +75.0°C)
> > > sensor = diode
> > > ...
> > >
> > > I have cheked it in BIOS and in AI Suite in windows 7 64
> bit
> > > and consulted it with ASUS technical support and
> everything is
> > > working properly.
> > > So , hardware is fine. Software in windows is fine. Only
> linux
> > > software is not correct.
> > > I have tried to detect-sensor many times and it is still
> the
> > > same.
> > > If there is some kind of tweak in config please let me know
> > > but it seems to me there is something wrong with lm-sensors
> > > 3.3.1.
> > >
> > > ...
> > > Intel digital thermal sensor...
> > > Success!
> > > (driver `coretemp')
> > > ...
> > > Found `Nuvoton NCT6776F Super IO Sensors'
> > > Success!
> > > ...
> > > Driver `w83627ehf':
> > > * ISA bus, address 0x290
> > > Chip `Nuvoton NCT6776F Super IO Sensors' (confidence:
> 9)
> > >
> > > Driver `coretemp':
> > > * Chip `Intel digital thermal sensor' (confidence: 9)
> > > ...
> > >
> > > my /etc/modules:
> > > ...
> > > coretemp
> > > w83627ehf
> > > ...
> > >
> > > This error have appeared on maximus iv extreme motherboard
> > > Revision 3 , BIOS from 1404 to 3202 (latest)
> > > linux ubuntu natty -> oneiric 64 bit kernel from 2.6.39 up
> to
> > > 3.0.0-19 commercial version (tested on 3.3.1 compiled by
> me)
> > >
> > > Could you please help me to solve it ?
> > >
> > > Thank you very much for any clue.
> > > Kind Regards,
> > > Martin
> > >
> > >
> >
> >
> >
> >
>
On Sat, Apr 21, 2012 at 3:49 PM, Guenter Roeck
<guenter.roeck@ericsson.com>wrote:
[-- Attachment #1.2: Type: text/html, Size: 6561 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
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (5 preceding siblings ...)
2012-04-21 15:04 ` Martin Suchanek
@ 2012-04-28 4:30 ` Guenter Roeck
2012-04-28 6:43 ` P.B. V
` (11 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-28 4:30 UTC (permalink / raw)
To: lm-sensors
On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek wrote:
> Hi,
>
> Add info:
> I have found software called open hardware monitor. I have been testing it
> in windows for couple of days and it works properly with Nuvoton NST6776F
> chip. I have been comparing results with AI Suite software coming from ASUS
> and results are corresponding and measuring is with big precise. So , you
> can have a look to source code and compare with your driver. This software
> should work on linux as well but I did not try it yet but I will.
>
I finally had time to look into the open hardware monitor code.
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.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (6 preceding siblings ...)
2012-04-28 4:30 ` Guenter Roeck
@ 2012-04-28 6:43 ` P.B. V
2012-04-28 8:55 ` Jean Delvare
` (10 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: P.B. V @ 2012-04-28 6:43 UTC (permalink / raw)
To: lm-sensors
> On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek wrote:
> > Hi,
> >
> > Add info:
> > I have found software called open hardware monitor. I have been testing it
> > in windows for couple of days and it works properly with Nuvoton NST6776F
> > chip. I have been comparing results with AI Suite software coming from ASUS
> > and results are corresponding and measuring is with big precise. So , you
> > can have a look to source code and compare with your driver. This software
> > should work on linux as well but I did not try it yet but I will.
> >
> I finally had time to look into the open hardware monitor code.
>
> 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.
>
> Guenter
This is a bad idea! I was about to report this.
w83627ehf and nct6775 (Apr 27, 2012) driver modules both show a
seemingly incorrect value for PECI. I am running a Maximus IV Extreme
Revision 1.0 motherboard (NCT6776F), with an i5-2550K CPU, on kernel
3.3.
The coretemp module and my BIOS reports my idle temperatures at around
33-35C, while PECI in Linux reports in at 23-25. It looks to be 10
degrees off. Under load it scales with coretemp, always staying 10
degrees under the average coretemp values.
Unless I'm not understanding something correctly, PECI should not be
used and doing so may lead to hardware damage.
coretemp:
Physical id 0: +36.0 C (high = +80.0 C, crit = +101.0 C)
Core 0: +36.0 C (high = +80.0 C, crit = +101.0 C)
Core 1: +32.0 C (high = +80.0 C, crit = +101.0 C)
Core 2: +34.0 C (high = +80.0 C, crit = +101.0 C)
Core 3: +30.0 C (high = +80.0 C, crit = +101.0 C)
w83627ehf: (nct6775 values are identical)
PECI Agent 0: +24.0 C
Also, I attempted to change the sensor type for CPUTIN using the
nct6775 module with no effect. All that changed was -60 went to -62.5
when changed to 'thermistor'.
- P.K.Y.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (7 preceding siblings ...)
2012-04-28 6:43 ` P.B. V
@ 2012-04-28 8:55 ` Jean Delvare
2012-04-28 10:08 ` Martin Suchanek
` (9 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jean Delvare @ 2012-04-28 8:55 UTC (permalink / raw)
To: lm-sensors
T24gU2F0LCAyOCBBcHIgMjAxMiAwNjo0Mzo1MyArMDAwMCwgUC5CLiBWIHdyb3RlOgo+IHc4MzYy
N2VoZiBhbmQgbmN0Njc3NSAoQXByIDI3LCAyMDEyKSBkcml2ZXIgbW9kdWxlcyBib3RoIHNob3cg
YQo+IHNlZW1pbmdseSBpbmNvcnJlY3QgdmFsdWUgZm9yIFBFQ0kuIEkgYW0gcnVubmluZyBhIE1h
eGltdXMgSVYgRXh0cmVtZQo+IFJldmlzaW9uIDEuMCBtb3RoZXJib2FyZCAoTkNUNjc3NkYpLCB3
aXRoIGFuIGk1LTI1NTBLIENQVSwgb24ga2VybmVsCj4gMy4zLgo+IAo+IFRoZSBjb3JldGVtcCBt
b2R1bGUgYW5kIG15IEJJT1MgcmVwb3J0cyBteSBpZGxlIHRlbXBlcmF0dXJlcyBhdCBhcm91bmQK
PiAzMy0zNUMsIHdoaWxlIFBFQ0kgaW4gTGludXggcmVwb3J0cyBpbiBhdCAyMy0yNS4gSXQgbG9v
a3MgdG8gYmUgMTAKPiBkZWdyZWVzIG9mZi4gVW5kZXIgbG9hZCBpdCBzY2FsZXMgd2l0aCBjb3Jl
dGVtcCwgYWx3YXlzIHN0YXlpbmcgMTAKPiBkZWdyZWVzIHVuZGVyIHRoZSBhdmVyYWdlIGNvcmV0
ZW1wIHZhbHVlcy4KPiAKPiBVbmxlc3MgSSdtIG5vdCB1bmRlcnN0YW5kaW5nIHNvbWV0aGluZyBj
b3JyZWN0bHksIFBFQ0kgc2hvdWxkIG5vdCBiZQo+IHVzZWQgYW5kIGRvaW5nIHNvIG1heSBsZWFk
IHRvIGhhcmR3YXJlIGRhbWFnZS4KPiAKPiBjb3JldGVtcDoKPiAgUGh5c2ljYWwgaWQgMDogICsz
Ni4wIEMgIChoaWdoID0gKzgwLjAgQywgY3JpdCA9ICsxMDEuMCBDKQo+ICBDb3JlIDA6ICAgICAg
ICAgKzM2LjAgQyAgKGhpZ2ggPSArODAuMCBDLCBjcml0ID0gKzEwMS4wIEMpCj4gIENvcmUgMTog
ICAgICAgICArMzIuMCBDICAoaGlnaCA9ICs4MC4wIEMsIGNyaXQgPSArMTAxLjAgQykKPiAgQ29y
ZSAyOiAgICAgICAgICszNC4wIEMgIChoaWdoID0gKzgwLjAgQywgY3JpdCA9ICsxMDEuMCBDKQo+
ICBDb3JlIDM6ICAgICAgICAgKzMwLjAgQyAgKGhpZ2ggPSArODAuMCBDLCBjcml0ID0gKzEwMS4w
IEMpCj4gCj4gdzgzNjI3ZWhmOiAobmN0Njc3NSB2YWx1ZXMgYXJlIGlkZW50aWNhbCkKPiAgUEVD
SSBBZ2VudCAwOiAgKzI0LjAgQwoKUEVDSSB2YWx1ZXMgYXJlIHJlcG9ydGVkIChhdCB0aGUgaGFy
ZHdhcmUgbGV2ZWwpIHJlbGF0aXZlIGZyb20gYW4KYXJiaXRyYXJ5IG1heGltdW0uIFRoZSBjb3Jl
dGVtcCBkcml2ZXIgdXNlcyAxMDHCsEMgYXMgdGhlIG1heGltdW0sIHlvdXIKcmVzdWx0cyBzdWdn
ZXN0cyB0aGF0IHRoZSB3ODM2MjdlaGYgYW5kIG5jdDY3NzUgZHJpdmVycyB1c2UgOTHCsEMgKG9y
Cm1heWJlIDkwwrBDKSBpbnN0ZWFkLiBUaGlzIGlzbid0IGdvaW5nIHRvIGNhdXNlIGFueSBoYXJk
d2FyZSBkYW1hZ2UsIGFuZAp5b3UgY2FuIGV2ZW4gZml4IHRoZSBwcm9ibGVtIGluIHVzZXItc3Bh
Y2Ugd2l0aCBhIGNvbXB1dGUgZm9ybXVsYSBsaWtlOgoKY2hpcCAibmN0Njc3Ni0qIgoKICAgY29t
cHV0ZSB0ZW1wTiBAICsgMTAsIEAgLSAxMAoKR3VlbnRlciwgaXMgdGhlcmUgYSB3YXkgdG8ga25v
dyB3aGF0IHRoZSBOQ1Q2Nzc2RiB0aGlua3MgdGhlIG1heGltdW0KdGVtcGVyYXR1cmUgaXM/IE1h
eWJlIHdlIGNhbiByZWFkIGl0IGZyb20gcmVnaXN0ZXJzIDB4NzA5IG9yIDB4NzBBPyBJZgp3ZSBj
b3VsZCBwcmVzZW50IHRoaXMgdmFsdWUgYXMgdGVtcE5fY3JpdCwgdGhpcyB3b3VsZCBoZWxwIHVu
ZGVyc3RhbmQKdGhlIGRpZmZlcmVuY2Ugb2YgYWJzb2x1dGUgdGVtcGVyYXR1cmVzIGJldHdlZW4g
Y29yZXRlbXAgYW5kIG5jdDY3NzYuCgotLSAKSmVhbiBEZWx2YXJlCgpfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpsbS1zZW5zb3JzIG1haWxpbmcgbGlzdAps
bS1zZW5zb3JzQGxtLXNlbnNvcnMub3JnCmh0dHA6Ly9saXN0cy5sbS1zZW5zb3JzLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2xtLXNlbnNvcnM
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (8 preceding siblings ...)
2012-04-28 8:55 ` Jean Delvare
@ 2012-04-28 10:08 ` Martin Suchanek
2012-04-28 10:22 ` Jean Delvare
` (8 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Martin Suchanek @ 2012-04-28 10:08 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 1376 bytes --]
On Sat, Apr 28, 2012 at 5:30 AM, Guenter Roeck
<guenter.roeck@ericsson.com>wrote:
> On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek wrote:
> > Hi,
> >
> > Add info:
> > I have found software called open hardware monitor. I have been testing
> it
> > in windows for couple of days and it works properly with Nuvoton NST6776F
> > chip. I have been comparing results with AI Suite software coming from
> ASUS
> > and results are corresponding and measuring is with big precise. So , you
> > can have a look to source code and compare with your driver. This
> software
> > should work on linux as well but I did not try it yet but I will.
> >
> I finally had time to look into the open hardware monitor code.
>
> 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 ?
Martin
[-- Attachment #1.2: Type: text/html, Size: 1941 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
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (9 preceding siblings ...)
2012-04-28 10:08 ` Martin Suchanek
@ 2012-04-28 10:22 ` Jean Delvare
2012-04-28 10:48 ` Martin Suchanek
` (7 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Jean Delvare @ 2012-04-28 10:22 UTC (permalink / raw)
To: lm-sensors
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...
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (10 preceding siblings ...)
2012-04-28 10:22 ` Jean Delvare
@ 2012-04-28 10:48 ` Martin Suchanek
2012-04-28 14:43 ` Guenter Roeck
` (6 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Martin Suchanek @ 2012-04-28 10:48 UTC (permalink / raw)
To: lm-sensors
[-- 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
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (11 preceding siblings ...)
2012-04-28 10:48 ` Martin Suchanek
@ 2012-04-28 14:43 ` Guenter Roeck
2012-04-28 15:00 ` Guenter Roeck
` (5 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-28 14:43 UTC (permalink / raw)
To: lm-sensors
On Sat, Apr 28, 2012 at 04:55:09AM -0400, Jean Delvare wrote:
> On Sat, 28 Apr 2012 06:43:53 +0000, P.B. V wrote:
> > w83627ehf and nct6775 (Apr 27, 2012) driver modules both show a
> > seemingly incorrect value for PECI. I am running a Maximus IV Extreme
> > Revision 1.0 motherboard (NCT6776F), with an i5-2550K CPU, on kernel
> > 3.3.
> >
> > The coretemp module and my BIOS reports my idle temperatures at around
> > 33-35C, while PECI in Linux reports in at 23-25. It looks to be 10
> > degrees off. Under load it scales with coretemp, always staying 10
> > degrees under the average coretemp values.
> >
> > Unless I'm not understanding something correctly, PECI should not be
> > used and doing so may lead to hardware damage.
> >
> > coretemp:
> > Physical id 0: +36.0 C (high = +80.0 C, crit = +101.0 C)
> > Core 0: +36.0 C (high = +80.0 C, crit = +101.0 C)
> > Core 1: +32.0 C (high = +80.0 C, crit = +101.0 C)
> > Core 2: +34.0 C (high = +80.0 C, crit = +101.0 C)
> > Core 3: +30.0 C (high = +80.0 C, crit = +101.0 C)
> >
> > w83627ehf: (nct6775 values are identical)
> > PECI Agent 0: +24.0 C
>
> PECI values are reported (at the hardware level) relative from an
> arbitrary maximum. The coretemp driver uses 101°C as the maximum, your
> results suggests that the w83627ehf and nct6775 drivers use 91°C (or
> maybe 90°C) instead. This isn't going to cause any hardware damage, and
> you can even fix the problem in user-space with a compute formula like:
>
The maximum should be set by the BIOS. On my system (ASUS mainboard) it
is correctly set to the critical CPU temperature (99 degrees C in my case).
Guess the Maximum board doesn't do that.
> chip "nct6776-*"
>
> compute tempN @ + 10, @ - 10
>
> Guenter, is there a way to know what the NCT6776F thinks the maximum
> temperature is? Maybe we can read it from registers 0x709 or 0x70A? If
> we could present this value as tempN_crit, this would help understand
> the difference of absolute temperatures between coretemp and nct6776.
>
Good idea. I added that to the nct6775 driver (I don't really want to mess
with the w83627ehf driver - it is getting too complicated).
Output for NCT6776F on my board (i5-2400) is now:
PECI Agent 0: +39.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +99.0°C)
and for NCT6775F (i7-2600):
PECI Agent 0: +32.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +98.0°C)
The attribute is writable.
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (12 preceding siblings ...)
2012-04-28 14:43 ` Guenter Roeck
@ 2012-04-28 15:00 ` Guenter Roeck
2012-04-28 15:36 ` Guenter Roeck
` (4 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-28 15:00 UTC (permalink / raw)
To: lm-sensors
On Sat, Apr 28, 2012 at 02:43:53AM -0400, P.B. V wrote:
[ ... ]
>
> Also, I attempted to change the sensor type for CPUTIN using the
> nct6775 module with no effect. All that changed was -60 went to -62.5
> when changed to 'thermistor'.
>
From what I have seen, temperature values around -60 on the NCT677X means
that nothing is connected to the respective pin, so it is not surprising
that the value does not change much if you change the sensor type.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (13 preceding siblings ...)
2012-04-28 15:00 ` Guenter Roeck
@ 2012-04-28 15:36 ` Guenter Roeck
2012-04-28 19:30 ` Guenter Roeck
` (3 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-28 15:36 UTC (permalink / raw)
To: lm-sensors
On Sat, Apr 28, 2012 at 06:08:23AM -0400, Martin Suchanek wrote:
>
>
> On Sat, Apr 28, 2012 at 5:30 AM, Guenter Roeck <guenter.roeck@ericsson.com>
> wrote:
>
> On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek wrote:
> > Hi,
> >
> > Add info:
> > I have found software called open hardware monitor. I have been testing
> it
> > in windows for couple of days and it works properly with Nuvoton NST6776F
> > chip. I have been comparing results with AI Suite software coming from
> ASUS
> > and results are corresponding and measuring is with big precise. So , you
> > can have a look to source code and compare with your driver. This
> software
> > should work on linux as well but I did not try it yet but I will.
> >
> I finally had time to look into the open hardware monitor code.
>
> 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 ?
>
From looking into the OHM source, motherboard temperature is SYSTIN, not CPUTIN.
Some but not all boards have AUXTIN connected as well. CPUTIN does not seem
to be used at all on ASUS boards as far as I can see.
From a board manufacturer perspective, that makes a lot of sense. PECI
provides the temperature from the CPU on-board sensor, making it more reliable
(since it reports the the difference to the maximum temperature) and cheaper
than an external sensor.
To know for sure what is connected to what one would need board schematics.
I would take statements from tech support with a grain (or two) of salt.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (14 preceding siblings ...)
2012-04-28 15:36 ` Guenter Roeck
@ 2012-04-28 19:30 ` Guenter Roeck
2012-04-28 23:18 ` Martin Suchanek
` (2 subsequent siblings)
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-28 19:30 UTC (permalink / raw)
To: lm-sensors
On Sat, Apr 28, 2012 at 03:04:51PM -0400, Martin Suchanek wrote:
>
>
> On Sat, Apr 28, 2012 at 4:36 PM, Guenter Roeck <guenter.roeck@ericsson.com>
> wrote:
>
> On Sat, Apr 28, 2012 at 06:08:23AM -0400, Martin Suchanek wrote:
> >
> >
> > On Sat, Apr 28, 2012 at 5:30 AM, Guenter Roeck <
> guenter.roeck@ericsson.com>
> > wrote:
> >
> > On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek wrote:
> > > Hi,
> > >
> > > Add info:
> > > I have found software called open hardware monitor. I have been
> testing
> > it
> > > in windows for couple of days and it works properly with Nuvoton
> NST6776F
> > > chip. I have been comparing results with AI Suite software coming
> from
> > ASUS
> > > and results are corresponding and measuring is with big precise. So
> , you
> > > can have a look to source code and compare with your driver. This
> > software
> > > should work on linux as well but I did not try it yet but I will.
> > >
> > I finally had time to look into the open hardware monitor code.
> >
> > 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 ?
> >
> From looking into the OHM source, motherboard temperature is SYSTIN, not
> CPUTIN.
> Some but not all boards have AUXTIN connected as well. CPUTIN does not seem
> to be used at all on ASUS boards as far as I can see.
>
>
>
> I am sorry but when I compare my AI Suite monitor (I attached picture) (- 60
> Celsius) with psensor ( - 60 Celsius) => CPUTIN correspond with motherboard
> temperature and technical support saying the same thing (even if I have to
> admit that according to name convention it should be as you said). And AUXTIN
> has asus motherboard maximus iv extreme - psensor is showing 33.5 Celsius - no
> problem with that.
Judging from the OHM source, it looks like some Asus boards have AUXTIN connected,
others don't. -60 degrees C suggests that there is nothing connected to the sensor pin.
> where did you get exactly those information about what is what ? Could you put
> some URL or documentation ?
Open Hardware Monitor source code, http://open-hardware-monitor.googlecode.com/svn.
I don't see CPUTIN on your screen shot. I only see "CPU" and "CPU socket", but I don't see
anything suggesting that those report the temperature as measured on the CPUTIN pin
of the NCT6776F. To know how the values reported by the AI suite map to board sensors,
it would be necessary to see its source code and/or configuration files.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (15 preceding siblings ...)
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
18 siblings, 0 replies; 20+ messages in thread
From: Martin Suchanek @ 2012-04-28 23:18 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 6433 bytes --]
On Sat, Apr 28, 2012 at 8:30 PM, Guenter Roeck
<guenter.roeck@ericsson.com>wrote:
> On Sat, Apr 28, 2012 at 03:04:51PM -0400, Martin Suchanek wrote:
> >
> >
> > On Sat, Apr 28, 2012 at 4:36 PM, Guenter Roeck <
> guenter.roeck@ericsson.com>
> > wrote:
> >
> > On Sat, Apr 28, 2012 at 06:08:23AM -0400, Martin Suchanek wrote:
> > >
> > >
> > > On Sat, Apr 28, 2012 at 5:30 AM, Guenter Roeck <
> > guenter.roeck@ericsson.com>
> > > wrote:
> > >
> > > On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek
> wrote:
> > > > Hi,
> > > >
> > > > Add info:
> > > > I have found software called open hardware monitor. I have
> been
> > testing
> > > it
> > > > in windows for couple of days and it works properly with
> Nuvoton
> > NST6776F
> > > > chip. I have been comparing results with AI Suite software
> coming
> > from
> > > ASUS
> > > > and results are corresponding and measuring is with big
> precise. So
> > , you
> > > > can have a look to source code and compare with your driver.
> This
> > > software
> > > > should work on linux as well but I did not try it yet but I
> will.
> > > >
> > > I finally had time to look into the open hardware monitor code.
> > >
> > > 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 ?
> > >
> > From looking into the OHM source, motherboard temperature is SYSTIN,
> not
> > CPUTIN.
> > Some but not all boards have AUXTIN connected as well. CPUTIN does
> not seem
> > to be used at all on ASUS boards as far as I can see.
> >
> >
> >
> > I am sorry but when I compare my AI Suite monitor (I attached picture)
> (- 60
> > Celsius) with psensor ( - 60 Celsius) => CPUTIN correspond with
> motherboard
> > temperature and technical support saying the same thing (even if I have
> to
> > admit that according to name convention it should be as you said). And
> AUXTIN
> > has asus motherboard maximus iv extreme - psensor is showing 33.5
> Celsius - no
> > problem with that.
>
> Judging from the OHM source, it looks like some Asus boards have AUXTIN
> connected,
> others don't. -60 degrees C suggests that there is nothing connected to
> the sensor pin.
>
> > where did you get exactly those information about what is what ? Could
> you put
> > some URL or documentation ?
>
> Open Hardware Monitor source code,
> http://open-hardware-monitor.googlecode.com/svn.
>
> I don't see CPUTIN on your screen shot. I only see "CPU" and "CPU socket",
> but I don't see
> anything suggesting that those report the temperature as measured on the
> CPUTIN pin
> of the NCT6776F. To know how the values reported by the AI suite map to
> board sensors,
> it would be necessary to see its source code and/or configuration files.
>
> Guenter
>
Oh, sorry , I did not explain it in all context. Minus 60 Celsius has
motherboard in red colour.
On the screenshot there is - 60 celsius temperature which corresponding
with value as in windows 7 as in linux psensor/lm-sensor as in my bios in
under certain complicated circumstances :-) That's the one for the reasons
why I am arguing due to meaning of CPUTIN.
I try to explain - it is more complex:
Minus 60 Celsius does not mean that sensor is not connected. It is
connected because - In 90 percent of my computer working time it is
properly measuring value by BIOS and AI Suite ... EXCEPT lm-sensor/psensor
in Linux - it is ALWAYS minus 60 Celsius - this is wrong.
What I am trying to say is that the problem is definitely at first with
hardware (this part I am still working on it with asus technical support)
and at second lm-sensor software in Linux. "Normally" , it is working
perfectly fine BUT in some very rarely occasions - when computer is running
much much longer temperature appears as minus 60 Celsius in Windows/BIOS".
BUT In Linux - it is ALWAYS minus 60 Celsius - it never was different value.
Only CPUTIN temperature has such problem in Linux. The other temperatures
- SYSTIN , AUXTIN , PECI Agent 0 have been always correct as in Windows as
in BIOS as in Linux. I have been comparing/inspecting those values more
than half a year so I am sure about those temperature values :-)
What I am totally confused is the meaning of CPUTIN/SYSTIN - from my
point of experience you are first person who is saying that CPUTIN is CPU
temperature and not motherboard temperature which is opposite what ASUS
technical support saying and further reason which I have mentioned before.
( :-) So if ASUS technical support is wrong it would be fun to talk with
ASUS technical support but I have to be absolutely sure about the meaning
of CPUTIN and SYSTIN :-) )
On many forums - owners of this motherboard are confused like me and I
did not find any reliable source of information to be sure how is it in
real ?
If I run open hardware monitor in linux - there is no values for
temperatures - except GPU - but only one instead of two and etc. ... too
many discrepancies within this software on Linux so I do not trust that it
is correct measuring (need to contact author later)
AI Suite is commercial ASUS software for measuring many usefull "bios"
parameters like temperatures/fans/voltages etc. ... but only for windows) -
so no source code at all - I will try to find some config files.
By the way - ASUS is not supporting linux at all and will not be - they
confirmed that.
Please accept my apology If I explained something bad/wrong way - (I am not
good in explaination) - let me know for further information.
Regards,
Martin
[-- Attachment #1.2: Type: text/html, Size: 7899 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
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (16 preceding siblings ...)
2012-04-28 23:18 ` Martin Suchanek
@ 2012-04-28 23:41 ` Guenter Roeck
2012-04-29 9:42 ` Martin Suchanek
18 siblings, 0 replies; 20+ messages in thread
From: Guenter Roeck @ 2012-04-28 23:41 UTC (permalink / raw)
To: lm-sensors
On Sat, Apr 28, 2012 at 07:18:46PM -0400, Martin Suchanek wrote:
>
>
> On Sat, Apr 28, 2012 at 8:30 PM, Guenter Roeck <guenter.roeck@ericsson.com>
> wrote:
>
> On Sat, Apr 28, 2012 at 03:04:51PM -0400, Martin Suchanek wrote:
> >
> >
> > On Sat, Apr 28, 2012 at 4:36 PM, Guenter Roeck <
> guenter.roeck@ericsson.com>
> > wrote:
> >
> > On Sat, Apr 28, 2012 at 06:08:23AM -0400, Martin Suchanek wrote:
> > >
> > >
> > > On Sat, Apr 28, 2012 at 5:30 AM, Guenter Roeck <
> > guenter.roeck@ericsson.com>
> > > wrote:
> > >
> > > On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek
> wrote:
> > > > Hi,
> > > >
> > > > Add info:
> > > > I have found software called open hardware monitor. I have
> been
> > testing
> > > it
> > > > in windows for couple of days and it works properly with
> Nuvoton
> > NST6776F
> > > > chip. I have been comparing results with AI Suite software
> coming
> > from
> > > ASUS
> > > > and results are corresponding and measuring is with big
> precise. So
> > , you
> > > > can have a look to source code and compare with your driver.
> This
> > > software
> > > > should work on linux as well but I did not try it yet but I
> will.
> > > >
> > > I finally had time to look into the open hardware monitor code.
> > >
> > > 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 ?
> > >
> > From looking into the OHM source, motherboard temperature is SYSTIN,
> not
> > CPUTIN.
> > Some but not all boards have AUXTIN connected as well. CPUTIN does
> not seem
> > to be used at all on ASUS boards as far as I can see.
> >
> >
> >
> > I am sorry but when I compare my AI Suite monitor (I attached picture) (-
> 60
> > Celsius) with psensor ( - 60 Celsius) => CPUTIN correspond with
> motherboard
> > temperature and technical support saying the same thing (even if I have
> to
> > admit that according to name convention it should be as you said). And
> AUXTIN
> > has asus motherboard maximus iv extreme - psensor is showing 33.5 Celsius
> - no
> > problem with that.
>
> Judging from the OHM source, it looks like some Asus boards have AUXTIN
> connected,
> others don't. -60 degrees C suggests that there is nothing connected to the
> sensor pin.
>
> > where did you get exactly those information about what is what ? Could
> you put
> > some URL or documentation ?
>
> Open Hardware Monitor source code, http://
> open-hardware-monitor.googlecode.com/svn.
>
> I don't see CPUTIN on your screen shot. I only see "CPU" and "CPU socket",
> but I don't see
> anything suggesting that those report the temperature as measured on the
> CPUTIN pin
> of the NCT6776F. To know how the values reported by the AI suite map to
> board sensors,
> it would be necessary to see its source code and/or configuration files.
>
> Guenter
>
>
>
> Oh, sorry , I did not explain it in all context. Minus 60 Celsius has
> motherboard in red colour.
> On the screenshot there is - 60 celsius temperature which corresponding with
> value as in windows 7 as in linux psensor/lm-sensor as in my bios in under
> certain complicated circumstances :-) That's the one for the reasons why I am
> arguing due to meaning of CPUTIN.
> I try to explain - it is more complex:
> Minus 60 Celsius does not mean that sensor is not connected. It is connected
> because - In 90 percent of my computer working time it is properly measuring
> value by BIOS and AI Suite ... EXCEPT lm-sensor/psensor in Linux - it is ALWAYS
> minus 60 Celsius - this is wrong.
> What I am trying to say is that the problem is definitely at first with
> hardware (this part I am still working on it with asus technical support) and
> at second lm-sensor software in Linux. "Normally" , it is working perfectly
> fine BUT in some very rarely occasions - when computer is running much much
> longer temperature appears as minus 60 Celsius in Windows/BIOS". BUT In Linux -
> it is ALWAYS minus 60 Celsius - it never was different value.
> Only CPUTIN temperature has such problem in Linux. The other temperatures -
> SYSTIN , AUXTIN , PECI Agent 0 have been always correct as in Windows as in
> BIOS as in Linux. I have been comparing/inspecting those values more than half
> a year so I am sure about those temperature values :-)
>
> What I am totally confused is the meaning of CPUTIN/SYSTIN - from my point of
> experience you are first person who is saying that CPUTIN is CPU temperature
> and not motherboard temperature which is opposite what ASUS technical support
> saying and further reason which I have mentioned before.
> ( :-) So if ASUS technical support is wrong it would be fun to talk with ASUS
> technical support but I have to be absolutely sure about the meaning of CPUTIN
> and SYSTIN :-) )
> On many forums - owners of this motherboard are confused like me and I did
> not find any reliable source of information to be sure how is it in real ?
>
> If I run open hardware monitor in linux - there is no values for temperatures -
> except GPU - but only one instead of two and etc. ... too many discrepancies
> within this software on Linux so I do not trust that it is correct measuring
> (need to contact author later)
>
> AI Suite is commercial ASUS software for measuring many usefull "bios"
> parameters like temperatures/fans/voltages etc. ... but only for windows) - so
> no source code at all - I will try to find some config files.
> By the way - ASUS is not supporting linux at all and will not be - they
> confirmed that.
>
> Please accept my apology If I explained something bad/wrong way - (I am not
> good in explaination) - let me know for further information.
>
Well, for my part I don't think I can help you any further. The driver reports
what it gets from the chip. The driver source is public. If you say that the driver
has a bug, feel free to dig through the driver and try to find it. I'll be more
than happy to accept patches.
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 20+ messages in thread* Re: [lm-sensors] sensor 3.3.1 and previous do not properly detect/show CPUTIN temperature - maximus
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
` (17 preceding siblings ...)
2012-04-28 23:41 ` Guenter Roeck
@ 2012-04-29 9:42 ` Martin Suchanek
18 siblings, 0 replies; 20+ messages in thread
From: Martin Suchanek @ 2012-04-29 9:42 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 7989 bytes --]
On Sun, Apr 29, 2012 at 12:41 AM, Guenter Roeck
<guenter.roeck@ericsson.com>wrote:
> On Sat, Apr 28, 2012 at 07:18:46PM -0400, Martin Suchanek wrote:
> >
> >
> > On Sat, Apr 28, 2012 at 8:30 PM, Guenter Roeck <
> guenter.roeck@ericsson.com>
> > wrote:
> >
> > On Sat, Apr 28, 2012 at 03:04:51PM -0400, Martin Suchanek wrote:
> > >
> > >
> > > On Sat, Apr 28, 2012 at 4:36 PM, Guenter Roeck <
> > guenter.roeck@ericsson.com>
> > > wrote:
> > >
> > > On Sat, Apr 28, 2012 at 06:08:23AM -0400, Martin Suchanek
> wrote:
> > > >
> > > >
> > > > On Sat, Apr 28, 2012 at 5:30 AM, Guenter Roeck <
> > > guenter.roeck@ericsson.com>
> > > > wrote:
> > > >
> > > > On Fri, Apr 20, 2012 at 11:47:47AM +0100, Martin Suchanek
> > wrote:
> > > > > Hi,
> > > > >
> > > > > Add info:
> > > > > I have found software called open hardware monitor. I
> have
> > been
> > > testing
> > > > it
> > > > > in windows for couple of days and it works properly
> with
> > Nuvoton
> > > NST6776F
> > > > > chip. I have been comparing results with AI Suite
> software
> > coming
> > > from
> > > > ASUS
> > > > > and results are corresponding and measuring is with big
> > precise. So
> > > , you
> > > > > can have a look to source code and compare with your
> driver.
> > This
> > > > software
> > > > > should work on linux as well but I did not try it yet
> but I
> > will.
> > > > >
> > > > I finally had time to look into the open hardware
> monitor code.
> > > >
> > > > 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 ?
> > > >
> > > From looking into the OHM source, motherboard temperature is
> SYSTIN,
> > not
> > > CPUTIN.
> > > Some but not all boards have AUXTIN connected as well. CPUTIN
> does
> > not seem
> > > to be used at all on ASUS boards as far as I can see.
> > >
> > >
> > >
> > > I am sorry but when I compare my AI Suite monitor (I attached
> picture) (-
> > 60
> > > Celsius) with psensor ( - 60 Celsius) => CPUTIN correspond with
> > motherboard
> > > temperature and technical support saying the same thing (even if I
> have
> > to
> > > admit that according to name convention it should be as you said).
> And
> > AUXTIN
> > > has asus motherboard maximus iv extreme - psensor is showing 33.5
> Celsius
> > - no
> > > problem with that.
> >
> > Judging from the OHM source, it looks like some Asus boards have
> AUXTIN
> > connected,
> > others don't. -60 degrees C suggests that there is nothing connected
> to the
> > sensor pin.
> >
> > > where did you get exactly those information about what is what ?
> Could
> > you put
> > > some URL or documentation ?
> >
> > Open Hardware Monitor source code, http://
> > open-hardware-monitor.googlecode.com/svn.
> >
> > I don't see CPUTIN on your screen shot. I only see "CPU" and "CPU
> socket",
> > but I don't see
> > anything suggesting that those report the temperature as measured on
> the
> > CPUTIN pin
> > of the NCT6776F. To know how the values reported by the AI suite map
> to
> > board sensors,
> > it would be necessary to see its source code and/or configuration
> files.
> >
> > Guenter
> >
> >
> >
> > Oh, sorry , I did not explain it in all context. Minus 60 Celsius has
> > motherboard in red colour.
> > On the screenshot there is - 60 celsius temperature which corresponding
> with
> > value as in windows 7 as in linux psensor/lm-sensor as in my bios in
> under
> > certain complicated circumstances :-) That's the one for the reasons why
> I am
> > arguing due to meaning of CPUTIN.
> > I try to explain - it is more complex:
> > Minus 60 Celsius does not mean that sensor is not connected. It is
> connected
> > because - In 90 percent of my computer working time it is properly
> measuring
> > value by BIOS and AI Suite ... EXCEPT lm-sensor/psensor in Linux - it is
> ALWAYS
> > minus 60 Celsius - this is wrong.
> > What I am trying to say is that the problem is definitely at first with
> > hardware (this part I am still working on it with asus technical
> support) and
> > at second lm-sensor software in Linux. "Normally" , it is working
> perfectly
> > fine BUT in some very rarely occasions - when computer is running much
> much
> > longer temperature appears as minus 60 Celsius in Windows/BIOS". BUT In
> Linux -
> > it is ALWAYS minus 60 Celsius - it never was different value.
> > Only CPUTIN temperature has such problem in Linux. The other
> temperatures -
> > SYSTIN , AUXTIN , PECI Agent 0 have been always correct as in Windows as
> in
> > BIOS as in Linux. I have been comparing/inspecting those values more
> than half
> > a year so I am sure about those temperature values :-)
> >
> > What I am totally confused is the meaning of CPUTIN/SYSTIN - from my
> point of
> > experience you are first person who is saying that CPUTIN is CPU
> temperature
> > and not motherboard temperature which is opposite what ASUS technical
> support
> > saying and further reason which I have mentioned before.
> > ( :-) So if ASUS technical support is wrong it would be fun to talk
> with ASUS
> > technical support but I have to be absolutely sure about the meaning of
> CPUTIN
> > and SYSTIN :-) )
> > On many forums - owners of this motherboard are confused like me and I
> did
> > not find any reliable source of information to be sure how is it in real
> ?
> >
> > If I run open hardware monitor in linux - there is no values for
> temperatures -
> > except GPU - but only one instead of two and etc. ... too many
> discrepancies
> > within this software on Linux so I do not trust that it is correct
> measuring
> > (need to contact author later)
> >
> > AI Suite is commercial ASUS software for measuring many usefull "bios"
> > parameters like temperatures/fans/voltages etc. ... but only for
> windows) - so
> > no source code at all - I will try to find some config files.
> > By the way - ASUS is not supporting linux at all and will not be - they
> > confirmed that.
> >
> > Please accept my apology If I explained something bad/wrong way - (I am
> not
> > good in explaination) - let me know for further information.
> >
> Well, for my part I don't think I can help you any further. The driver
> reports
> what it gets from the chip. The driver source is public. If you say that
> the driver
> has a bug, feel free to dig through the driver and try to find it. I'll be
> more
> than happy to accept patches.
>
> Thanks,
> Guenter
>
:-) ok , that will be too many things for me to learn but I will (I made
for the last time software in assembler and C 20 years ago) :-)
Martin
[-- Attachment #1.2: Type: text/html, Size: 10280 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
^ permalink raw reply [flat|nested] 20+ messages in thread