[lm-sensors] A question regarding ASRock H55DE3 motherboard

[lm-sensors] A question regarding ASRock H55DE3 motherboard

[Artem S. Tashkinov]

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Hello,

I've recently become an owner of the aforementioned motherboard and I 
have no idea how to monitor it in Linux.

sensors-detect says that:
--------------------------------------------------------------------
Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `adt7473':
   * Bus `NVIDIA i2c adapter '
     Busdriver `nvidia', I2C address 0x2e
     Chip `Analog Devices ADT7473' (confidence: 5)

Driver `to-be-written':
   * ISA bus, address 0x290
     Chip `Nuvoton W83667HG-B Super IO Sensors' (confidence: 9)

Warning: the required module adt7473 is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.

Note: there is no driver for Nuvoton W83667HG-B Super IO Sensors yet.
Check http://www.lm-sensors.org/wiki/Devices for updates.

No modules to load, skipping modules configuration.
--------------------------------------------------------------------
however what really confuses me is that Windows hwmon115 says that I 
have Winbond W832627DHG monitoring chip which is theoretically supported 
by lm-sensors/i2c. However both w83627ehf.ko and w83627hf.ko modules 
don't load with "No such device" error.

Another question is that hwmon115 detects temperatures and even power 
draw of my Intel Core i5 CPU however sensors-detect doesn't even mention 
this possibility.

I'm now running 2.6.32.8 vanilla kernel.

Best wishes,

Artem

[-- Attachment #2: sensors2.png --]
[-- Type: image/png, Size: 14175 bytes --]

[-- Attachment #3: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] A question regarding ASRock H55DE3 motherboard

[Jean Delvare]

Hi Artem,

On Tue, 16 Feb 2010 11:50:38 +0500, Artem S. Tashkinov wrote:
> I've recently become an owner of the aforementioned motherboard and I 
> have no idea how to monitor it in Linux.
> 
> sensors-detect says that:
> --------------------------------------------------------------------
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
> 
> Driver `adt7473':
>    * Bus `NVIDIA i2c adapter '
>      Busdriver `nvidia', I2C address 0x2e
>      Chip `Analog Devices ADT7473' (confidence: 5)
> 
> Driver `to-be-written':
>    * ISA bus, address 0x290
>      Chip `Nuvoton W83667HG-B Super IO Sensors' (confidence: 9)
> 
> Warning: the required module adt7473 is not currently installed
> on your system. If it is built into the kernel then it's OK.
> Otherwise, check http://www.lm-sensors.org/wiki/Devices for
> driver availability.

This driver should be available. If it's not there, this suggests that
you did not set CONFIG_SENSORS_ADT7473=m when building your kernel. You
should have...

(Note: starting with kernel 2.6.33 you will have to use the adt7475
driver instead.)

> Note: there is no driver for Nuvoton W83667HG-B Super IO Sensors yet.
> Check http://www.lm-sensors.org/wiki/Devices for updates.

We indeed do not support this chip yet. I've added your request to the
list on wiki/Devices.

> No modules to load, skipping modules configuration.
> --------------------------------------------------------------------
> however what really confuses me is that Windows hwmon115 says that I 
> have Winbond W832627DHG monitoring chip which is theoretically supported 
> by lm-sensors/i2c. However both w83627ehf.ko and w83627hf.ko modules 
> don't load with "No such device" error.

I would trust sensors-detect. Maybe that Windows tool has decided that
the chips are compatible enough that the W83667HG-B can be handled as a
W83627DHG, at least for the feature subset it handles. Only a careful
inspection of the datasheets would tell. You may want to try loading
the w83627ehf driver with parameters force_id=0xa020 (to have the
driver treat your chip as a W83627DHG), force_id=0xb070 (to have the
driver treat your chip as a W83627DHG-P) or force_id=0xa510 (to have
the driver treat your chip as a W83667HG). Beware though that this is
untested by definition and we do not make any guarantee. It may
somewhat work for monitoring, but for example I wouldn't dare trying
fan speed control.

> Another question is that hwmon115 detects temperatures and even power 
> draw of my Intel Core i5 CPU however sensors-detect doesn't even mention 
> this possibility.

CPU core temperature support could certainly be added to the coretemp
driver. We are waiting for Intel to help. Huaxu, any progress?

The power draw value is news to me, maybe this is a new feature of the
Core i5 which could be added to the driver as well.

> I'm now running 2.6.32.8 vanilla kernel.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] A question regarding ASRock H55DE3 motherboard

[Artem S. Tashkinov]

On 02/18/2010 12:19 AM, Jean Delvare wrote:

Hello, Jean,

 > Hi Artem,
 >
 > On Tue, 16 Feb 2010 11:50:38 +0500, Artem S. Tashkinov wrote:
 >> I've recently become an owner of the aforementioned motherboard and I
 >> have no idea how to monitor it in Linux.
 >>
 >> sensors-detect says that:
 >> --------------------------------------------------------------------
 >> Now follows a summary of the probes I have just done.
 >> Just press ENTER to continue:
 >>
 >> Driver `adt7473':
 >>     * Bus `NVIDIA i2c adapter '
 >>       Busdriver `nvidia', I2C address 0x2e
 >>       Chip `Analog Devices ADT7473' (confidence: 5)
 >>
 >> Driver `to-be-written':
 >>     * ISA bus, address 0x290
 >>       Chip `Nuvoton W83667HG-B Super IO Sensors' (confidence: 9)
 >>
 >> Warning: the required module adt7473 is not currently installed
 >> on your system. If it is built into the kernel then it's OK.
 >> Otherwise, check http://www.lm-sensors.org/wiki/Devices for
 >> driver availability.
 >
 > This driver should be available. If it's not there, this suggests that
 > you did not set CONFIG_SENSORS_ADT7473=m when building your kernel. You
 > should have...

I will try to build this driver and report if it shows anything.

 >
 > (Note: starting with kernel 2.6.33 you will have to use the adt7475
 > driver instead.)
 >
 >> Note: there is no driver for Nuvoton W83667HG-B Super IO Sensors yet.
 >> Check http://www.lm-sensors.org/wiki/Devices for updates.
 >
 > We indeed do not support this chip yet. I've added your request to the
 > list on wiki/Devices.
 >
 >> No modules to load, skipping modules configuration.
 >> --------------------------------------------------------------------
 >> however what really confuses me is that Windows hwmon115 says that I
 >> have Winbond W832627DHG monitoring chip which is theoretically supported
 >> by lm-sensors/i2c. However both w83627ehf.ko and w83627hf.ko modules
 >> don't load with "No such device" error.
 >
 > I would trust sensors-detect. Maybe that Windows tool has decided that
 > the chips are compatible enough that the W83667HG-B can be handled as a
 > W83627DHG, at least for the feature subset it handles. Only a careful
 > inspection of the datasheets would tell. You may want to try loading
 > the w83627ehf driver with parameters force_id=0xa020 (to have the
 > driver treat your chip as a W83627DHG), force_id=0xb070 (to have the
 > driver treat your chip as a W83627DHG-P) or force_id=0xa510 (to have
 > the driver treat your chip as a W83667HG). Beware though that this is
 > untested by definition and we do not make any guarantee. It may
 > somewhat work for monitoring, but for example I wouldn't dare trying
 > fan speed control.

It looks like it's my own blunder: I have confused w83_2_627 to w83627 
:) and taking into consideration ASRock's documentation my chip is 
indeed made by Nuvoton and it's currently unsupported - I'm eagerly 
awaiting patches to be merged.

 >
 >> Another question is that hwmon115 detects temperatures and even power
 >> draw of my Intel Core i5 CPU however sensors-detect doesn't even mention
 >> this possibility.
 >
 > CPU core temperature support could certainly be added to the coretemp
 > driver. We are waiting for Intel to help. Huaxu, any progress?
 >
 > The power draw value is news to me, maybe this is a new feature of the
 > Core i5 which could be added to the driver as well.
 >
 >> I'm now running 2.6.32.8 vanilla kernel.
 >

-- 

Best wishes,

Artem

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] A question regarding ASRock H55DE3 motherboard

[Jean Delvare]

On Thu, 18 Feb 2010 01:08:04 +0500, Artem S. Tashkinov wrote:
> On 02/18/2010 12:19 AM, Jean Delvare wrote:
>  > This driver should be available. If it's not there, this suggests that
>  > you did not set CONFIG_SENSORS_ADT7473=m when building your kernel. You
>  > should have...
> 
> I will try to build this driver and report if it shows anything.

Note: last time I checked (long ago), the binary nvidia driver which
you appear to be using, did not let hwmon driver probe its I2C buses
for devices. So you might have to instantiate the chip yourself with:

# echo adt7473 0x2e > /sys/class/i2c-adapter/i2c-<N>/device/new_device

where <N> is the bus number of the i2c bus in question.

> (...)
> It looks like it's my own blunder: I have confused w83_2_627 to w83627 
> :) and taking into consideration ASRock's documentation my chip is 
> indeed made by Nuvoton and it's currently unsupported - I'm eagerly 
> awaiting patches to be merged.

Hmm, does the W832627 actually exist? I thought it was a typo.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] A question regarding ASRock H55DE3 motherboard

[Artem S. Tashkinov]

[-- Attachment #1: Type: text/plain, Size: 4373 bytes --]

On 02/18/2010 02:15 AM, Jean Delvare wrote:
> On Thu, 18 Feb 2010 01:08:04 +0500, Artem S. Tashkinov wrote:
>> On 02/18/2010 12:19 AM, Jean Delvare wrote:
>>   >  This driver should be available. If it's not there, this suggests that
>>   >  you did not set CONFIG_SENSORS_ADT7473=m when building your kernel. You
>>   >  should have...
>>
>> I will try to build this driver and report if it shows anything.
>
> Note: last time I checked (long ago), the binary nvidia driver which
> you appear to be using, did not let hwmon driver probe its I2C buses
> for devices. So you might have to instantiate the chip yourself with:
>
> # echo adt7473 0x2e>  /sys/class/i2c-adapter/i2c-<N>/device/new_device
>
> where<N>  is the bus number of the i2c bus in question.

echo adt7473 0x2e > /sys/class/i2c-adapter/i2c-3/new_device produced the 
desired results:

adt7473-i2c-3-2e
Adapter: NVIDIA i2c adapter
in1:         +3.00 V  (min =  +0.00 V, max =  +2.99 V)
+3.3V:       +3.33 V  (min =  +0.00 V, max =  +4.39 V)
fan1:        889 RPM  (min =    0 RPM)
fan2:          0 RPM  (min =    0 RPM)
fan3:          0 RPM  (min =  164 RPM)  ALARM
temp1:       +39.2°C  (low  = +65.0°C, high = +85.0°C)  ALARM
                       (crit = +100.0°C, hyst = +98.0°C)
Board Temp:  +33.8°C  (low  = +20.0°C, high = +60.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)
temp3:       +39.2°C  (low  = +80.0°C, high = +105.0°C)  ALARM
                       (crit = +136.0°C, hyst = +132.0°C)

The output needs to be configured (via /etc/sensors.d/chipname.conf), 
but that's not a problem.

>
>> (...)
>> It looks like it's my own blunder: I have confused w83_2_627 to w83627
>> :) and taking into consideration ASRock's documentation my chip is
>> indeed made by Nuvoton and it's currently unsupported - I'm eagerly
>> awaiting patches to be merged.
>
> Hmm, does the W832627 actually exist? I thought it was a typo.
>

I apologize - it's my double blunder - HWMon shows Winbond W83627DHG 
chip. So I tried w83627dhg driver and it perfectly works on my system 
when loaded this way (as you suggested in a previous letter):

modprobe w83627ehf force_id=0xa020

w83627dhg-isa-0290
Adapter: ISA adapter
Vcore:       +0.82 V  (min =  +0.00 V, max =  +1.74 V)
in1:         +1.85 V  (min =  +0.69 V, max =  +1.91 V)
AVCC:        +3.39 V  (min =  +2.00 V, max =  +0.56 V)   ALARM
VCC:         +3.39 V  (min =  +2.86 V, max =  +1.76 V)   ALARM
in4:         +0.05 V  (min =  +1.53 V, max =  +1.94 V)   ALARM
in5:         +1.71 V  (min =  +1.32 V, max =  +1.86 V)
in6:         +0.05 V  (min =  +1.66 V, max =  +1.90 V)   ALARM
3VSB:        +3.49 V  (min =  +1.50 V, max =  +2.99 V)   ALARM
Vbat:        +3.34 V  (min =  +3.71 V, max =  +3.74 V)   ALARM
fan1:          0 RPM  (min =  217 RPM, div = 64)  ALARM
fan2:       1004 RPM  (min =  397 RPM, div = 32)
fan3:          0 RPM  (min =  357 RPM, div = 64)  ALARM
fan4:          0 RPM  (min =   84 RPM, div = 128)  ALARM
fan5:          0 RPM  (min =  703 RPM, div = 16)  ALARM
temp1:       +33.0°C  (high = -13.0°C, hyst = -46.0°C)  ALARM  sensor = 
thermistor
temp2:       +36.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
temp3:      +127.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor = 
thermistor
cpu0_vid:   +0.000 V

However this means two things, w83627ehf driver needs to be updated to 
work with my PC (I can send any system information if it's required) and 
sensors-detect script should also be modified to correctly identify my 
sensors (it missed coretemp driver altogether).

***

coretemp driver started working after I applied the attached patch, 
however the readings are wrong, so probably this driver is not yet 
capable of monitoring Intel Core i5 650 CPU (temperatures are all wrong, 
there are only two physical CPU cores):

coretemp-isa-0000
Adapter: ISA adapter
Core 0:      +23.0°C  (high = +84.0°C, crit = +100.0°C)

coretemp-isa-0001
Adapter: ISA adapter
Core 1:      +26.0°C  (high = +84.0°C, crit = +100.0°C)

coretemp-isa-0002
Adapter: ISA adapter
Core 2:      +23.0°C  (high = +84.0°C, crit = +100.0°C)

coretemp-isa-0003
Adapter: ISA adapter
Core 3:      +26.0°C  (high = +84.0°C, crit = +100.0°C)

Thank you very much, Jean, for your invaluable help.

-- 

Best wishes,

Artem

[-- Attachment #2: coretemp.intel.core.i5.patch --]
[-- Type: text/plain, Size: 469 bytes --]

--- coretemp.c.default	2010-02-18 16:14:58.517835386 +0500
+++ coretemp.c	2010-02-18 15:54:35.128157728 +0500
@@ -460,7 +460,7 @@
 		    !((c->x86_model == 0xe) || (c->x86_model == 0xf) ||
 			(c->x86_model == 0x16) || (c->x86_model == 0x17) ||
 			(c->x86_model == 0x1a) || (c->x86_model == 0x1c) ||
-			(c->x86_model == 0x1e))) {
+			(c->x86_model == 0x1e) || (c->x86_model == 0x25))) {
 
 			/* supported CPU not found, but report the unknown
 			   family 6 CPU */

[-- Attachment #3: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] A question regarding ASRock H55DE3 motherboard

[Jean Delvare]

Hi Artem,

On Thu, 18 Feb 2010 16:25:48 +0500, Artem S. Tashkinov wrote:
> echo adt7473 0x2e > /sys/class/i2c-adapter/i2c-3/new_device produced the 
> desired results:
> 
> adt7473-i2c-3-2e
> Adapter: NVIDIA i2c adapter
> in1:         +3.00 V  (min =  +0.00 V, max =  +2.99 V)
> +3.3V:       +3.33 V  (min =  +0.00 V, max =  +4.39 V)
> fan1:        889 RPM  (min =    0 RPM)
> fan2:          0 RPM  (min =    0 RPM)
> fan3:          0 RPM  (min =  164 RPM)  ALARM
> temp1:       +39.2°C  (low  = +65.0°C, high = +85.0°C)  ALARM
>                        (crit = +100.0°C, hyst = +98.0°C)
> Board Temp:  +33.8°C  (low  = +20.0°C, high = +60.0°C)
>                        (crit = +100.0°C, hyst = +96.0°C)
> temp3:       +39.2°C  (low  = +80.0°C, high = +105.0°C)  ALARM
>                        (crit = +136.0°C, hyst = +132.0°C)
> 
> The output needs to be configured (via /etc/sensors.d/chipname.conf), 
> but that's not a problem.

Looks good indeed. I'd guess in1, fan2 and fan3 aren't used so you can
add an "ignore" statement for them. The rest looks good, except the low
limits of temp1 and temp3.

> (...)
> I apologize - it's my double blunder - HWMon shows Winbond W83627DHG 
> chip. So I tried w83627dhg driver and it perfectly works on my system 
> when loaded this way (as you suggested in a previous letter):
> 
> modprobe w83627ehf force_id=0xa020
> 
> w83627dhg-isa-0290
> Adapter: ISA adapter
> Vcore:       +0.82 V  (min =  +0.00 V, max =  +1.74 V)
> in1:         +1.85 V  (min =  +0.69 V, max =  +1.91 V)
> AVCC:        +3.39 V  (min =  +2.00 V, max =  +0.56 V)   ALARM
> VCC:         +3.39 V  (min =  +2.86 V, max =  +1.76 V)   ALARM
> in4:         +0.05 V  (min =  +1.53 V, max =  +1.94 V)   ALARM
> in5:         +1.71 V  (min =  +1.32 V, max =  +1.86 V)
> in6:         +0.05 V  (min =  +1.66 V, max =  +1.90 V)   ALARM
> 3VSB:        +3.49 V  (min =  +1.50 V, max =  +2.99 V)   ALARM
> Vbat:        +3.34 V  (min =  +3.71 V, max =  +3.74 V)   ALARM
> fan1:          0 RPM  (min =  217 RPM, div = 64)  ALARM
> fan2:       1004 RPM  (min =  397 RPM, div = 32)
> fan3:          0 RPM  (min =  357 RPM, div = 64)  ALARM
> fan4:          0 RPM  (min =   84 RPM, div = 128)  ALARM
> fan5:          0 RPM  (min =  703 RPM, div = 16)  ALARM
> temp1:       +33.0°C  (high = -13.0°C, hyst = -46.0°C)  ALARM  sensor = 
> thermistor
> temp2:       +36.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> temp3:      +127.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor = 
> thermistor
> cpu0_vid:   +0.000 V

From the above output, it's hard to claim it works "perfectly". Some
values look good, yes, but more careful inspection would be needed to
confirm that all inputs and limits work they way they are supposed to.

> However this means two things, w83627ehf driver needs to be updated to 
> work with my PC (I can send any system information if it's required)

Correct.... We must add support for your chip.

> and  sensors-detect script should also be modified to correctly
> identify my sensors (it missed coretemp driver altogether).

No, sensors-detect does the right thing at the moment. It properly
identifies your Super-I/O chip (which is _not_ a W83627DHG so we just
can't claim it is). As for the coretemp driver, the driver currently
doesn't support your CPU so we can't point the user to it. If we did,
we would receive complaints like "sensors-detect told me to load driver
coretemp but it doesn't work." So we have to do changes in the right
order, that is, first add support to the coretemp driver, and then
change sensors-detect to point to it.

In the meantime, please attach the contents of /proc/cpuinfo for the
records.

> coretemp driver started working after I applied the attached patch, 
> however the readings are wrong, so probably this driver is not yet 
> capable of monitoring Intel Core i5 650 CPU (temperatures are all wrong, 
> there are only two physical CPU cores):
> 
> coretemp-isa-0000
> Adapter: ISA adapter
> Core 0:      +23.0°C  (high = +84.0°C, crit = +100.0°C)
> 
> coretemp-isa-0001
> Adapter: ISA adapter
> Core 1:      +26.0°C  (high = +84.0°C, crit = +100.0°C)
> 
> coretemp-isa-0002
> Adapter: ISA adapter
> Core 2:      +23.0°C  (high = +84.0°C, crit = +100.0°C)
> 
> coretemp-isa-0003
> Adapter: ISA adapter
> Core 3:      +26.0°C  (high = +84.0°C, crit = +100.0°C)

This is the reason why I am waiting for the Intel folks to give us the
details. Apparently your Windows application is reporting temperatures
10 degrees higher, so I would guess that it assumes a critical
temperature limit of 110°C for this CPU model (current temperature is
reported relative to the critical limit.) But I wouldn't really assume
they know it for sure either, given how hard it was to get the
information for the other CPU models.

As for the core count, the coretemp driver will show one device for
each separate CPU entry. If you have 4 entries in /proc/cpuinfo, you
get 4 coretemp devices. If this is a dual core CPU then I have no idea
why you have 4 entries in /proc/cpuinfo.

> Thank you very much, Jean, for your invaluable help.

You're welcome.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] A question regarding ASRock H55DE3 motherboard

[Artem S. Tashkinov]

[-- Attachment #1: Type: text/plain, Size: 8389 bytes --]

Hello Jean,

On 02/19/2010 02:52 PM, Jean Delvare wrote:
 > Hi Artem,
 >
 > On Thu, 18 Feb 2010 16:25:48 +0500, Artem S. Tashkinov wrote:
 >> echo adt7473 0x2e>  /sys/class/i2c-adapter/i2c-3/new_device produced the
 >> desired results:
 >>
 >> adt7473-i2c-3-2e
 >> Adapter: NVIDIA i2c adapter
 >> in1:         +3.00 V  (min =  +0.00 V, max =  +2.99 V)
 >> +3.3V:       +3.33 V  (min =  +0.00 V, max =  +4.39 V)
 >> fan1:        889 RPM  (min =    0 RPM)
 >> fan2:          0 RPM  (min =    0 RPM)
 >> fan3:          0 RPM  (min =  164 RPM)  ALARM
 >> temp1:       +39.2°C  (low  = +65.0°C, high = +85.0°C)  ALARM
 >>                         (crit = +100.0°C, hyst = +98.0°C)
 >> Board Temp:  +33.8°C  (low  = +20.0°C, high = +60.0°C)
 >>                         (crit = +100.0°C, hyst = +96.0°C)
 >> temp3:       +39.2°C  (low  = +80.0°C, high = +105.0°C)  ALARM
 >>                         (crit = +136.0°C, hyst = +132.0°C)
 >>
 >> The output needs to be configured (via /etc/sensors.d/chipname.conf),
 >> but that's not a problem.
 >
 > Looks good indeed. I'd guess in1, fan2 and fan3 aren't used so you can
 > add an "ignore" statement for them. The rest looks good, except the low
 > limits of temp1 and temp3.

I'm attaching my adt7473.conf if anyone needs it - I'm not sure if it's 
suitable for lm-sensors wiki - it's you to decide. Now this sensor 
output looks this way:

adt7473-i2c-3-2e
Adapter: NVIDIA i2c adapter
+3.3V:       +3.32 V  (min =  +2.96 V, max =  +3.61 V)
GPU Fan:     876 RPM  (min =    0 RPM)
GPU Core:    +48.2°C  (low  = +20.5°C, high = +92.5°C)
                       (crit = +107.5°C, hyst = +105.5°C)
GPU Ambient: +35.2°C  (low  = +20.0°C, high = +60.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)

 >
 >> (...)
 >> I apologize - it's my double blunder - HWMon shows Winbond W83627DHG
 >> chip. So I tried w83627dhg driver and it perfectly works on my system
 >> when loaded this way (as you suggested in a previous letter):
 >>
 >> modprobe w83627ehf force_id=0xa020
 >>
 >> w83627dhg-isa-0290
 >> Adapter: ISA adapter
 >> Vcore:       +0.82 V  (min =  +0.00 V, max =  +1.74 V)
 >> in1:         +1.85 V  (min =  +0.69 V, max =  +1.91 V)
 >> AVCC:        +3.39 V  (min =  +2.00 V, max =  +0.56 V)   ALARM
 >> VCC:         +3.39 V  (min =  +2.86 V, max =  +1.76 V)   ALARM
 >> in4:         +0.05 V  (min =  +1.53 V, max =  +1.94 V)   ALARM
 >> in5:         +1.71 V  (min =  +1.32 V, max =  +1.86 V)
 >> in6:         +0.05 V  (min =  +1.66 V, max =  +1.90 V)   ALARM
 >> 3VSB:        +3.49 V  (min =  +1.50 V, max =  +2.99 V)   ALARM
 >> Vbat:        +3.34 V  (min =  +3.71 V, max =  +3.74 V)   ALARM
 >> fan1:          0 RPM  (min =  217 RPM, div = 64)  ALARM
 >> fan2:       1004 RPM  (min =  397 RPM, div = 32)
 >> fan3:          0 RPM  (min =  357 RPM, div = 64)  ALARM
 >> fan4:          0 RPM  (min =   84 RPM, div = 128)  ALARM
 >> fan5:          0 RPM  (min =  703 RPM, div = 16)  ALARM
 >> temp1:       +33.0°C  (high = -13.0°C, hyst = -46.0°C)  ALARM  sensor =
 >> thermistor
 >> temp2:       +36.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = 
thermistor
 >> temp3:      +127.5°C  (high = +80.0°C, hyst = +75.0°C)  ALARM  sensor =
 >> thermistor
 >> cpu0_vid:   +0.000 V
 >
 >  From the above output, it's hard to claim it works "perfectly". Some
 > values look good, yes, but more careful inspection would be needed to
 > confirm that all inputs and limits work they way they are supposed to.

In the meantime I cannot find the right formula for +12V which is shown 
by Windows utilities, so probably I need to wait for a dedicated nuvoton 
driver - alas, it only exists as a patch and I've no idea how to compile 
and test it. The next strange thing is that in this output only VCore, 
in1, in4, in6 and 3VSB change their values, all other sensors remain the 
same no matter what my load is. Temp2 temperature which is theoretically 
a CPU temperature changes much slower than coretemp indicates.

 >
 >> However this means two things, w83627ehf driver needs to be updated to
 >> work with my PC (I can send any system information if it's required)
 >
 > Correct.... We must add support for your chip.
 >
 >> and  sensors-detect script should also be modified to correctly
 >> identify my sensors (it missed coretemp driver altogether).
 >
 > No, sensors-detect does the right thing at the moment. It properly
 > identifies your Super-I/O chip (which is _not_ a W83627DHG so we just
 > can't claim it is). As for the coretemp driver, the driver currently
 > doesn't support your CPU so we can't point the user to it. If we did,
 > we would receive complaints like "sensors-detect told me to load driver
 > coretemp but it doesn't work." So we have to do changes in the right
 > order, that is, first add support to the coretemp driver, and then
 > change sensors-detect to point to it.
 >
 > In the meantime, please attach the contents of /proc/cpuinfo for the
 > records.

I've filed a bug report on this topic: 
http://bugzilla.kernel.org/show_bug.cgi?id=15348

Anyway, here's the information you requested:

$ cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 37
model name      : Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz
stepping        : 2
cpu MHz         : 1200.000
cache size      : 4096 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 11
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx 
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc 
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 
cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm ida arat tpr_shadow vnmi 
flexpriority ept vpid
bogomips        : 6626.04
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

 >
 >> coretemp driver started working after I applied the attached patch,
 >> however the readings are wrong, so probably this driver is not yet
 >> capable of monitoring Intel Core i5 650 CPU (temperatures are all wrong,
 >> there are only two physical CPU cores):
 >>
 >> coretemp-isa-0000
 >> Adapter: ISA adapter
 >> Core 0:      +23.0°C  (high = +84.0°C, crit = +100.0°C)
 >>
 >> coretemp-isa-0001
 >> Adapter: ISA adapter
 >> Core 1:      +26.0°C  (high = +84.0°C, crit = +100.0°C)
 >>
 >> coretemp-isa-0002
 >> Adapter: ISA adapter
 >> Core 2:      +23.0°C  (high = +84.0°C, crit = +100.0°C)
 >>
 >> coretemp-isa-0003
 >> Adapter: ISA adapter
 >> Core 3:      +26.0°C  (high = +84.0°C, crit = +100.0°C)
 >
 > This is the reason why I am waiting for the Intel folks to give us the
 > details. Apparently your Windows application is reporting temperatures
 > 10 degrees higher, so I would guess that it assumes a critical
 > temperature limit of 110°C for this CPU model (current temperature is
 > reported relative to the critical limit.) But I wouldn't really assume
 > they know it for sure either, given how hard it was to get the
 > information for the other CPU models.

I have found out that TJMax for this CPU is 105C.

 >
 > As for the core count, the coretemp driver will show one device for
 > each separate CPU entry. If you have 4 entries in /proc/cpuinfo, you
 > get 4 coretemp devices. If this is a dual core CPU then I have no idea
 > why you have 4 entries in /proc/cpuinfo.

This CPU has only two physical cores and it has HT (hyperthreading) 
enabled, thus it shows itself as four cores for an operating system. 
However I have a firm belief that HT "cores" should be omitted in 
coretemp sensors output. I tried disabling the third and the fourth 
cores using this configuration

chip "coretemp-*"

ignore temp3
ignore temp4

and even

ignore core3
ignore core4

but it doesn't seem to work.

 >
 >> Thank you very much, Jean, for your invaluable help.
 >
 > You're welcome.
 >

[-- Attachment #2: adt7473.conf --]
[-- Type: text/plain, Size: 692 bytes --]

# lm_sensors configuration for adt7473 chip on NVIDIA GeForce 8800GT GPU by Artem S. Tashkinov
# Requirements:
#   * loaded NVIDIA binary module;
#   * echo adt7473 0x2e > /sys/class/i2c-adapter/i2c-3/new_device (adjust for your environment)

chip "adt7473-*"

# Voltages

    ignore in1  # Always shows 3.0V here, let's omit it

# Temperatures

    label  temp1  "GPU Core"
    label  temp2  "GPU Ambient"
    ignore temp3 # Show the same temperature as temp1 sensor

    compute temp1 @+7.5, @-7.5
    compute temp3 @+7.5, @-7.5

    set temp1_min   20
    set temp3_min   20

# Fans

    label  fan1 "GPU Fan"
    ignore fan2  # My 8800GT GPU has the only fan
    ignore fan3  # Likewise


[-- Attachment #3: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors