[lm-sensors] Gigabyte MA785GMT-UD2H

[lm-sensors] Gigabyte MA785GMT-UD2H

[David Mathog]

Anybody have a sensors.conf for this board that works? 

Attempting to get lm-sensors working on a Gigabyte MA785GMT-UD2H
motherboard on Ubuntu 10.04LTS.   Kernel is 2.6.32-22, lm-sensors is
3.1.2-2, and CPU is AMD Athlon(tm) II X2 240 Processor. sensors-detect
added these to /etc/modules:

 it87
 lm90

and made some comment about k10temp.  There is no k10temp module, but
there is a k8temp.  modprobe k8temp doesn't change anything though.
In any case, the output of sensors clearly isn't correct, for instance,
there are no 5V and 12V readings:

it8718-isa-0228
Adapter: ISA adapter
in0:         +1.14 V  (min =  +0.00 V, max =  +4.08 V)   
in1:         +1.60 V  (min =  +0.00 V, max =  +4.08 V)   
in2:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
in3:         +2.99 V  (min =  +0.00 V, max =  +4.08 V)   
in4:         +3.04 V  (min =  +0.00 V, max =  +4.08 V)   
in5:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
in6:         +4.08 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
in7:         +2.00 V  (min =  +0.00 V, max =  +4.08 V)   
Vbat:        +3.12 V
fan1:       1662 RPM  (min =    0 RPM)
fan2:          0 RPM  (min =    0 RPM)
fan3:          0 RPM  (min =    0 RPM)
fan4:       1184 RPM  (min =    0 RPM)
temp1:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor thermistor
temp2:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor thermal diode
temp3:       +29.0°C  (low  = +127.0°C, high = +127.0°C)  sensor thermistor
cpu0_vid:   +1.050 V


Thanks,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[Jean Delvare]

Hi David,

On Fri, 28 May 2010 11:38:59 -0700, David Mathog wrote:
> Anybody have a sensors.conf for this board that works?

I don't.

> Attempting to get lm-sensors working on a Gigabyte MA785GMT-UD2H
> motherboard on Ubuntu 10.04LTS.   Kernel is 2.6.32-22, lm-sensors is
> 3.1.2-2, and CPU is AMD Athlon(tm) II X2 240 Processor. sensors-detect
> added these to /etc/modules:
> 
>  it87
>  lm90

Did you actually load the lm90 driver? It doesn't show below. Maybe it
was for a graphics adapter?

> and made some comment about k10temp.  There is no k10temp module, but
> there is a k8temp.  modprobe k8temp doesn't change anything though.

The k10temp driver was added in kernel 2.6.33. It is also available as
a standalone driver at:
http://khali.linux-fr.org/devel/misc/k10temp/

> In any case, the output of sensors clearly isn't correct, for instance,
> there are no 5V and 12V readings:
> 
> it8718-isa-0228
> Adapter: ISA adapter
> in0:         +1.14 V  (min =  +0.00 V, max =  +4.08 V)   
> in1:         +1.60 V  (min =  +0.00 V, max =  +4.08 V)   
> in2:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
> in3:         +2.99 V  (min =  +0.00 V, max =  +4.08 V)   
> in4:         +3.04 V  (min =  +0.00 V, max =  +4.08 V)   
> in5:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
> in6:         +4.08 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
> in7:         +2.00 V  (min =  +0.00 V, max =  +4.08 V)   
> Vbat:        +3.12 V
> fan1:       1662 RPM  (min =    0 RPM)
> fan2:          0 RPM  (min =    0 RPM)
> fan3:          0 RPM  (min =    0 RPM)
> fan4:       1184 RPM  (min =    0 RPM)
> temp1:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
> temp2:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermal diode
> temp3:       +29.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
> cpu0_vid:   +1.050 V

You "simply" need a proper configuration file. If you want help from
us, we need the following:

* Messages in the kernel log when loading the it87 driver.
* If you have Windows installed on the machine, all the values reported
  by Gigabyte's EasyTune software.
* All the hardware monitoring values reported in the BIOS. If some
  items oscillate between different values, we need all values.

-- 
Jean Delvare

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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[David Mathog]

> > Attempting to get lm-sensors working on a Gigabyte MA785GMT-UD2H
> > motherboard on Ubuntu 10.04LTS.   Kernel is 2.6.32-22, lm-sensors is
> > 3.1.2-2, and CPU is AMD Athlon(tm) II X2 240 Processor. sensors-detect
> > added these to /etc/modules:
> > 
> >  it87
> >  lm90
> 
> Did you actually load the lm90 driver? It doesn't show below. Maybe it
> was for a graphics adapter?

lsmod | grep lm90
lm90                   12125  0 

Loaded, but apparently not working.

> 
> > and made some comment about k10temp.  There is no k10temp module, but
> > there is a k8temp.  modprobe k8temp doesn't change anything though.
> 
> The k10temp driver was added in kernel 2.6.33. It is also available as
> a standalone driver at:
> http://khali.linux-fr.org/devel/misc/k10temp/

That link is timing out right now, will try later.
> 
> > In any case, the output of sensors clearly isn't correct, for instance,
> > there are no 5V and 12V readings:
> > 
> > it8718-isa-0228
> > Adapter: ISA adapter
> > in0:         +1.14 V  (min =  +0.00 V, max =  +4.08 V)   
> > in1:         +1.60 V  (min =  +0.00 V, max =  +4.08 V)   
> > in2:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
> > in3:         +2.99 V  (min =  +0.00 V, max =  +4.08 V)   
> > in4:         +3.04 V  (min =  +0.00 V, max =  +4.08 V)   
> > in5:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
> > in6:         +4.08 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
> > in7:         +2.00 V  (min =  +0.00 V, max =  +4.08 V)   
> > Vbat:        +3.12 V
> > fan1:       1662 RPM  (min =    0 RPM)
> > fan2:          0 RPM  (min =    0 RPM)
> > fan3:          0 RPM  (min =    0 RPM)
> > fan4:       1184 RPM  (min =    0 RPM)
> > temp1:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor
= thermistor
> > temp2:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor
= thermal diode
> > temp3:       +29.0°C  (low  = +127.0°C, high = +127.0°C)  sensor
= thermistor
> > cpu0_vid:   +1.050 V
> 
> You "simply" need a proper configuration file. If you want help from
> us, we need the following:
> 
> * Messages in the kernel log when loading the it87 driver.
Jun  1 11:12:29 saf04 kernel: [  768.656268] it87: Found IT8718F chip at
0x228, revision 8
Jun  1 11:12:29 saf04 kernel: [  768.656284] it87: in3 is VCC (+5V)

There are no messages when lm90 loads.

> * If you have Windows installed on the machine, all the values reported
>   by Gigabyte's EasyTune software.
> * All the hardware monitoring values reported in the BIOS. If some
>   items oscillate between different values, we need all values.
EasyTune won't run, W7 complains about a checksum in some driver it
contains and won't let it start.  Here are the BIOS and speedfan 4.40
values, lined up in those few cases where the label is the same.
(Energy saving is turned on when W7 is running, so Vcore may really have
dropped from 1.488 to 1.14).

           BIOS     Speedfan
Vcore      1.488V      -
Vcore1       -      1.14V
Vcore2       -      1.60V
DDR3(1.5v) 1.600V      -
+3.3V      3.344V   3.36V
+5V          -      5.05V
+12V      11.985V  12.16V
-12V         -       .31V
-5V          -      4.15V
+5V          -      3.30V
Vbat         -      3.12V
SysTemp    24C          -
CPUTemp    33C          -
Temp1        -        29C
Temp2        -        29C
Temp3        -        31C
HDO          -        26C
Core         -        20C
CPUFan    1834RPM       -
SysFan       0RPM       -
NBFan     1169RPM       -
Fan1        -        1805RPM
Fan4        -        1188RPM
Fan2,3,5    -     (all) 0RPM

Thanks,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[Jean Delvare]

Hi David,

On Tue, 01 Jun 2010 11:22:58 -0700, David Mathog wrote:
> > > Attempting to get lm-sensors working on a Gigabyte MA785GMT-UD2H
> > > motherboard on Ubuntu 10.04LTS.   Kernel is 2.6.32-22, lm-sensors is
> > > 3.1.2-2, and CPU is AMD Athlon(tm) II X2 240 Processor. sensors-detect
> > > added these to /etc/modules:
> > > 
> > >  it87
> > >  lm90
> > 
> > Did you actually load the lm90 driver? It doesn't show below. Maybe it
> > was for a graphics adapter?
> 
> lsmod | grep lm90
> lm90                   12125  0 
> 
> Loaded, but apparently not working.

OK, most probably the chip is on an Nvidia graphics adapter. To get it
to work, you'll need to run sensors-detect again and write down the i2c
bus number and the address at which the chip is detected.

> > > and made some comment about k10temp.  There is no k10temp module, but
> > > there is a k8temp.  modprobe k8temp doesn't change anything though.
> > 
> > The k10temp driver was added in kernel 2.6.33. It is also available as
> > a standalone driver at:
> > http://khali.linux-fr.org/devel/misc/k10temp/
> 
> That link is timing out right now, will try later.

Works for me...

> > > In any case, the output of sensors clearly isn't correct, for instance,
> > > there are no 5V and 12V readings:
> > > 
> > > it8718-isa-0228
> > > Adapter: ISA adapter
> > > in0:         +1.14 V  (min =  +0.00 V, max =  +4.08 V)   
> > > in1:         +1.60 V  (min =  +0.00 V, max =  +4.08 V)   
> > > in2:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
> > > in3:         +2.99 V  (min =  +0.00 V, max =  +4.08 V)   
> > > in4:         +3.04 V  (min =  +0.00 V, max =  +4.08 V)   
> > > in5:         +3.36 V  (min =  +0.00 V, max =  +4.08 V)   
> > > in6:         +4.08 V  (min =  +0.00 V, max =  +4.08 V)   ALARM
> > > in7:         +2.00 V  (min =  +0.00 V, max =  +4.08 V)   
> > > Vbat:        +3.12 V
> > > fan1:       1662 RPM  (min =    0 RPM)
> > > fan2:          0 RPM  (min =    0 RPM)
> > > fan3:          0 RPM  (min =    0 RPM)
> > > fan4:       1184 RPM  (min =    0 RPM)
> > > temp1:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
> > > temp2:       +27.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermal diode
> > > temp3:       +29.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
> > > cpu0_vid:   +1.050 V
> > 
> > You "simply" need a proper configuration file. If you want help from
> > us, we need the following:
> > 
> > * Messages in the kernel log when loading the it87 driver.
> Jun  1 11:12:29 saf04 kernel: [  768.656268] it87: Found IT8718F chip at 0x228, revision 8
> Jun  1 11:12:29 saf04 kernel: [  768.656284] it87: in3 is VCC (+5V)

OK, this gives us the label and scaling for in3.

> There are no messages when lm90 loads.

This is expected.

> > * If you have Windows installed on the machine, all the values reported
> >   by Gigabyte's EasyTune software.
> > * All the hardware monitoring values reported in the BIOS. If some
> >   items oscillate between different values, we need all values.
> EasyTune won't run, W7 complains about a checksum in some driver it
> contains and won't let it start.

Did you check for an update on their website maybe?

>  Here are the BIOS and speedfan 4.40
> values, lined up in those few cases where the label is the same.

OK, Speedfan is better than nothing, but just as us they don't know the
details of each board so their results must be taken with a grain of
salt.

> (Energy saving is turned on when W7 is running, so Vcore may really have
> dropped from 1.488 to 1.14).

Indeed.

> 
>            BIOS     Speedfan
> Vcore      1.488V      -
> Vcore1       -      1.14V
> Vcore2       -      1.60V
> DDR3(1.5v) 1.600V      -
> +3.3V      3.344V   3.36V
> +5V          -      5.05V
> +12V      11.985V  12.16V
> -12V         -       .31V
> -5V          -      4.15V
> +5V          -      3.30V
> Vbat         -      3.12V
> SysTemp    24C          -
> CPUTemp    33C          -
> Temp1        -        29C
> Temp2        -        29C
> Temp3        -        31C
> HDO          -        26C
> Core         -        20C
> CPUFan    1834RPM       -
> SysFan       0RPM       -
> NBFan     1169RPM       -
> Fan1        -        1805RPM
> Fan4        -        1188RPM
> Fan2,3,5    -     (all) 0RPM

OK, this is a good start. I've come up with the following configuration
file for you:

# lm_sensors 3 configuration file for the Gigabyte MA785GMT-UD2H motherboard
# 2010-06-03, Jean Delvare <khali@linux-fr.org>
# Comments welcome!

chip "it8718-*"

### Voltages

   label  in0  "Vcore"
   label  in1  "Vram"    # "DDR3" in BIOS
   label  in2  "+3.3V"
   label  in3  "+5V"     # Not in BIOS
   ignore in6
   label  in8  "Vbat"    # Not in BIOS

   # Vcore, Vram, +3.3V and Vbat are connected directly, so no compute
   # line is needed for these. For +5V the chip is configured to use
   # internal scaling.
   compute  in3  @ * (6.8/10+1), @ / (6.8/10+1)

   # The BIOS won't set any limit for voltages.

   set in0_min  0.825 * 0.95
   set in0_max  1.425 * 1.05
   set in1_min  1.5   * 0.95
   set in1_max  1.6   * 1.05
   set in2_min  3.3   * 0.95
   set in2_max  3.3   * 1.05
   set in3_min  5     * 0.95
   set in3_max  5     * 1.05

### Fans

   label  fan1  "CPU Fan"
   label  fan2  "Case Fan"  # Must be confirmed
   ignore fan3
   label  fan4  "NBr Fan"

   # Adjust for your own fans
   set fan1_min 1500
   set fan4_min 1000

#####

Remaining points:

* Voltages: I don't know which of in4, in5 or in7 corresponds to +12V.
  I suspect in4, but I'm not certain. Please write down all the values
  displayed for +12V in the BIOS, and then all the values displayed for
  in4, in5 and in7 by "sensors". Voltage sensors almost always
  oscillate between two values, sometimes more. If in4 is +12V, then
  maybe in5 may be +3.3 Stand-By (3VSB). No idea about in7.

* Temperatures: I really don't know who is who, nor whether the sensor
  types are set properly. Try comparing the temperatures between idle
  and full load. If one value raises much faster than the others, that
  would be the CPU temperature. Also check the motherboard manual, if
  they say where the thermal sensors are, that would be useful.

* Fans: please check how many fan headers your board has. If you have a
  spare fan, I would appreciate if you could plug it in the free
  header(s). This will help us figure out the labels of fan2 and fan3.
  My guess is that one of them is what the BIOS labels SysFan, and the
  other one is not connected.

With this information I should be able to complete the configuration
file and publish it for other users to benefit.

-- 
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] Gigabyte MA785GMT-UD2H

[David Mathog]

> > > 
> > > Did you actually load the lm90 driver? It doesn't show below. Maybe it
> > > was for a graphics adapter?
> > 
> > lsmod | grep lm90
> > lm90                   12125  0 
> > 
> > Loaded, but apparently not working.
> 
> OK, most probably the chip is on an Nvidia graphics adapter. To get it
> to work, you'll need to run sensors-detect again and write down the i2c
> bus number and the address at which the chip is detected.

i2c-2, found lm90
also
I2c 0x4c

> > > http://khali.linux-fr.org/devel/misc/k10temp/
> > 
> > That link is timing out right now, will try later.
> 
> Works for me...

Got it through an anonymizer.  Apparently khali's web server or firewall
is blocking Caltech.  I have seen this before on a couple of other
sites, sometimes our central mail server gets blacklisted and that ends
up in other sites' firewall rules.

> > > * If you have Windows installed on the machine, all the values
reported
> > >   by Gigabyte's EasyTune software.
> > > * All the hardware monitoring values reported in the BIOS. If some
> > >   items oscillate between different values, we need all values.
> > EasyTune won't run, W7 complains about a checksum in some driver it
> > contains and won't let it start.
> 
> Did you check for an update on their website maybe?

Yes.  The current version has an AODDriver.sys with an invalid checksum
once installed, and W7 blocks it from running.


> Remaining points:
> 
> * Voltages: I don't know which of in4, in5 or in7 corresponds to +12V.
>   I suspect in4, but I'm not certain. Please write down all the values
>   displayed for +12V in the BIOS, and then all the values displayed for
>   in4, in5 and in7 by "sensors". Voltage sensors almost always
>   oscillate between two values, sometimes more. If in4 is +12V, then
>   maybe in5 may be +3.3 Stand-By (3VSB). No idea about in7.

In4 oscillates between 3.02 and 3.04, in5 is stable at 3.36, in7 reads
2.00 or 2.02.  In the BIOS reading there is no oscillation. +12V is
11.985V and +3.3V=3.344V.

> * Temperatures: I really don't know who is who, nor whether the sensor
>   types are set properly. Try comparing the temperatures between idle
>   and full load. If one value raises much faster than the others, that
>   would be the CPU temperature. Also check the motherboard manual, if
>   they say where the thermal sensors are, that would be useful.
 
                  2xburnK7               idle
Temp1              29.0                   30.0
Temp2              49.0                   28.0
Temp3              43.0                   30.0
K10Temp1           41.0                   19.5

The K10 temperature rises/falls more slowly than temp2 or temp3.


> * Fans: please check how many fan headers your board has. If you have a
>   spare fan, I would appreciate if you could plug it in the free
>   header(s). This will help us figure out the labels of fan2 and fan3.
>   My guess is that one of them is what the BIOS labels SysFan, and the
>   other one is not connected.

There are 3:
fan1  CPU_FAN
fan2  SYS_FAN
fan4  NB_FAN

verified by plugging/unplugging that this was how they mapped.  I
plugged a 60mm ~5000rpm fan into SYS_FAN and it read only 2710 RPM, but
in the BIOS it had "System Smart Fan Control is enabled", so the
motherboard may have been running it at less than full speed.  The test
fan only has 3 pins, plugged into a 4 pin header.  Since the speed
control should be on pin 4, which isn't connected, I think maybe SYS_FAN
is off by a factor of 2. Did not test SYS_FAN speed in the BIOS.  

Thanks,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[Jean Delvare]

Hi David,

On Thu, 03 Jun 2010 10:56:12 -0700, David Mathog wrote:
> > OK, most probably the chip is on an Nvidia graphics adapter. To get it
> > to work, you'll need to run sensors-detect again and write down the i2c
> > bus number and the address at which the chip is detected.
> 
> i2c-2, found lm90
> also
> I2c 0x4c

OK, then you can run the following command to instantiate the device:

echo lm90 0x4c > /sys/bus/i2c/devices/i2c-2/new_device

> > (...)
> > Works for me...
> 
> Got it through an anonymizer.  Apparently khali's web server or firewall
> is blocking Caltech.  I have seen this before on a couple of other
> sites, sometimes our central mail server gets blacklisted and that ends
> up in other sites' firewall rules.

Odd. I've asked my ISP for details, but I'm not holding my breath.

> > (...)
> > Did you check for an update on their website maybe?
> 
> Yes.  The current version has an AODDriver.sys with an invalid checksum
> once installed, and W7 blocks it from running.

Oh well. I'm glad I'm away from the Windows world ;)

> > Remaining points:
> > 
> > * Voltages: I don't know which of in4, in5 or in7 corresponds to +12V.
> >   I suspect in4, but I'm not certain. Please write down all the values
> >   displayed for +12V in the BIOS, and then all the values displayed for
> >   in4, in5 and in7 by "sensors". Voltage sensors almost always
> >   oscillate between two values, sometimes more. If in4 is +12V, then
> >   maybe in5 may be +3.3 Stand-By (3VSB). No idea about in7.
> 
> In4 oscillates between 3.02 and 3.04, in5 is stable at 3.36, in7 reads
> 2.00 or 2.02.  In the BIOS reading there is no oscillation. +12V is
> 11.985V and +3.3V=3.344V.

Did you try leaving the monitoring panel and entering it again? Maybe
the BIOS doesn't update the values dynamically.

It would be very useful to have another BIOS value for +12V. You might
change the value by temporarily adding a fan and/or a disk drive to the
system.

Anyway, I still believe that in4 is +12V, and Speedfan seems to agree.
I disagree with their scaling though, they apparently used a scaling
factor of 4.00, but this makes their reading diverge a lot from the
BIOS': 12.16 V instead of 11.985 V. The scaling factor is more likely
in the 3.94-3.97 range. I have an old nForce2 board here where they
used 3.963 (according to my guesses back then), maybe that's the same
on yours.

> > * Temperatures: I really don't know who is who, nor whether the sensor
> >   types are set properly. Try comparing the temperatures between idle
> >   and full load. If one value raises much faster than the others, that
> >   would be the CPU temperature. Also check the motherboard manual, if
> >   they say where the thermal sensors are, that would be useful.
>  
>                   2xburnK7               idle
> Temp1              29.0                   30.0
> Temp2              49.0                   28.0
> Temp3              43.0                   30.0
> K10Temp1           41.0                   19.5

This suggests that temp1 is either unused or used for a part which
doesn't work too hard ;) Maybe a sensor on the board itself. Would be
interesting to see if it's affected by the case being opened or closed.
It might really be unused though - after all the BIOS only displays 2
temperature values.

temp2 would be the CPU temperature. temp3 could be the north bridge,
after all it has a dedicated fan so it's probably worth monitoring.

> The K10 temperature rises/falls more slowly than temp2 or temp3.

This is strange, as the digital sensor is supposed to be very close to
the core.

> > * Fans: please check how many fan headers your board has. If you have a
> >   spare fan, I would appreciate if you could plug it in the free
> >   header(s). This will help us figure out the labels of fan2 and fan3.
> >   My guess is that one of them is what the BIOS labels SysFan, and the
> >   other one is not connected.
> 
> There are 3:
> fan1  CPU_FAN
> fan2  SYS_FAN
> fan4  NB_FAN

Thanks, at least this part is done now.

> verified by plugging/unplugging that this was how they mapped.  I
> plugged a 60mm ~5000rpm fan into SYS_FAN and it read only 2710 RPM, but
> in the BIOS it had "System Smart Fan Control is enabled", so the
> motherboard may have been running it at less than full speed.  The test
> fan only has 3 pins, plugged into a 4 pin header.  Since the speed
> control should be on pin 4, which isn't connected, I think maybe SYS_FAN
> is off by a factor of 2. Did not test SYS_FAN speed in the BIOS.  

I wouldn't conclude too fast, as the IT8718F datasheet doesn't say
anything about 4-pin fan support. But the board manual claims that pin
4 of SYS FAN is "reserved", so maybe they do traditional 3-pin-style
control on that header.

(OTOH they claim that pin 3 of the NB FAN is not connected, which is
certainly wrong, otherwise you wouldn't get a speed reading for that
fan. So the manual may not be trustworthy.)

Testing in the BIOS and with "Smart Fan" disabled would certainly be a
good idea. Fan speeds normally need no scaling, unless they have a pole
count different from 4 (but then this is a per-fan setting.)

There seems to be many hardware revisions of your board. For the
records, can you tell us which one you have?

Here's my current config, which I will also upload. Basically I'm happy
with everything except +12V (which we should be able to figure out at
least approximately), temp1 and in7 (but it doesn't matter that much.)

# lm_sensors 3 configuration file for the Gigabyte MA785GMT-UD2H motherboard
# 2010-06-04, Jean Delvare <khali@linux-fr.org>
# Thanks to David Mathog for testing and reporting.
# Comments welcome!

chip "it8718-*"

### Voltages

   label  in0  "Vcore"
   label  in1  "Vram"    # "DDR3" in BIOS
   label  in2  "+3.3V"
   label  in3  "+5V"     # Not in BIOS
   label  in4  "+12V"
   label  in5  "3VSB"    # Not in BIOS, guessed
   ignore in6
#  label  in7  "???"     # No idea about that one, maybe -12V?
   label  in8  "Vbat"    # Not in BIOS

   # Vcore, Vram, +3.3V and Vbat are connected directly, so no compute
   # line is needed for these. For +5V the chip is configured to use
   # internal scaling. Scaling for +12V isn't known yet.
   compute  in3  @ * (6.8/10+1), @ / (6.8/10+1)
#  compute  in4  @ * ( 30/10+1), @ / ( 30/10+1)

   # The BIOS won't set any limit for voltages.

   set in0_min  0.825 * 0.95
   set in0_max  1.425 * 1.05
   set in1_min  1.5   * 0.95
   set in1_max  1.6   * 1.05
   set in2_min  3.3   * 0.95
   set in2_max  3.3   * 1.05
   set in3_min  5     * 0.95
   set in3_max  5     * 1.05
#  set in4_min 12     * 0.95
#  set in4_max 12     * 1.05
   set in5_min  3.3   * 0.95
   set in5_max  3.3   * 1.05

### Temperatures

   label  temp1  "Sys Temp"    # Needs confirmation
   label  temp2  "CPU Temp"
   label  temp3  "NBr Temp"    # Guessed

   set temp1_min  10
   set temp1_max  50
   set temp2_min  10
   set temp2_max  60
   set temp3_min  10
   set temp3_max  50

### Fans

   label  fan1  "CPU Fan"
   label  fan2  "Case Fan"
   ignore fan3
   label  fan4  "NBr Fan"

   # Adjust for your own fans
   set fan1_min 1500
   set fan4_min 1000


-- 
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] Gigabyte MA785GMT-UD2H

[David Mathog]

> OK, then you can run the following command to instantiate the device:
> 
> echo lm90 0x4c > /sys/bus/i2c/devices/i2c-2/new_device

That works.

lm90-i2c-2-4c
Adapter: NVIDIA i2c adapter 
temp1:       +29.0°C  (low  =  +0.0°C, high = +105.0°C)  
                      (crit = +127.0°C, hyst = +117.0°C)  
temp2:       +19.6°C  (low  = -11.0°C, high = +94.0°C)  
                      (crit = +127.0°C, hyst = +117.0°C)  


Verified that these go up when the graphics card is busy.

Where would one normally put this on an Ubuntu system?
Somewhere in /etc/init.d, or as a line in /etc/modules, or ???

> 
> > > Remaining points:
> > > 
> > > * Voltages: I don't know which of in4, in5 or in7 corresponds to +12V.
> > >   I suspect in4, but I'm not certain. Please write down all the values
> > >   displayed for +12V in the BIOS, and then all the values
displayed for
> > >   in4, in5 and in7 by "sensors". Voltage sensors almost always
> > >   oscillate between two values, sometimes more. If in4 is +12V, then
> > >   maybe in5 may be +3.3 Stand-By (3VSB). No idea about in7.
> > 
> > In4 oscillates between 3.02 and 3.04, in5 is stable at 3.36, in7 reads
> > 2.00 or 2.02.  In the BIOS reading there is no oscillation. +12V is
> > 11.985V and +3.3V=3.344V.
> 
> Did you try leaving the monitoring panel and entering it again? Maybe
> the BIOS doesn't update the values dynamically.

Tried adding two more fans, both reasonably high current, and the 12V
reading stayed at 11.985.  Entering and exiting the BIOS system monitor
didn't change that.  While running linux I could make in4, in5, and in7
shift very slightly by running a couple of copies of burnK7.  Not sure
the result is real. In the third column no load but set governor to
performance.  Results:
     noload     loaded  performance
in4  3.02,3.04  3.01    3.02,3.04
in5  3.36       3.34    3.34 
in7  2.00       2.90    2.66   <-- so it scales with the governor.


> Anyway, I still believe that in4 is +12V, and Speedfan seems to agree.
> I disagree with their scaling though, they apparently used a scaling
> factor of 4.00, but this makes their reading diverge a lot from the
> BIOS': 12.16 V instead of 11.985 V. The scaling factor is more likely
> in the 3.94-3.97 range. I have an old nForce2 board here where they
> used 3.963 (according to my guesses back then), maybe that's the same
> on yours.

Hmm, could be due to the CPU speed scaling.  In the BIOS I'm pretty sure
the CPUs are both running at their maximum speed of 2800MHz, but in
Windows and linux they scale down to 800MHz.  Plugged a DMM into a molex
connector and measured this for the performance and ondemand governors:
     2800MHz  800Mz
5V    5.07    5.06
12V  12.03    12.04

(It's a really cheap DMM, certainly not accurate to the last decimal place.)

> > The K10 temperature rises/falls more slowly than temp2 or temp3.
> 
> This is strange, as the digital sensor is supposed to be very close to
> the core.

Also strange, k10temp only shows a single temperature, but it is a dual
core system. 

cat /proc/cpuinfo | grep processor
processor       : 0
processor       : 1

k10temp-pci-00c3
Adapter: PCI adapter
temp1:       +21.4°C  (high = +70.0°C, crit = +72.0°C)  

k8temp running on a different system with Opteron 280 proessors shows
the temperature of each core, like this:

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:  +23.0C                                    
Core1 Temp:  +31.0C                                    

 
> (OTOH they claim that pin 3 of the NB FAN is not connected, which is
> certainly wrong, otherwise you wouldn't get a speed reading for that
> fan. So the manual may not be trustworthy.)

It wouldn't be the first time.

> There seems to be many hardware revisions of your board. For the
> records, can you tell us which one you have?

Both the box and the board itself say "Rev 1.1".

Thanks,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech



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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[David Mathog]

> Hmm, could be due to the CPU speed scaling.  In the BIOS I'm pretty sure
> the CPUs are both running at their maximum speed of 2800MHz, but in
> Windows and linux they scale down to 800MHz.  Plugged a DMM into a molex
> connector and measured this for the performance and ondemand governors:
>      2800MHz  800Mz
> 5V    5.07    5.06
> 12V  12.03    12.04

A slightly different table:
                              DMM
BIOS measurement  11.985    = 12.00
W7 speedfan       12.10     = 12.02
in4/lm_sensors    3.02/3.04 = 12.03 (2800MHz)
in4/lm_sensors    3.02/3.04 = 12.04 (800MHz)

So it does look like 12V in the BIOS mode really is a hair lower than it
is in either linux or W7.  Using 3.03 for the avg in4 measurement and
12.035 for the avg DMM measurement gives a scale factor of 3.97,
assuming the DMM is actually correct.  

Regards,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[Jean Delvare]

Hi David,

On Fri, 04 Jun 2010 10:23:26 -0700, David Mathog wrote:
> > OK, then you can run the following command to instantiate the device:
> > 
> > echo lm90 0x4c > /sys/bus/i2c/devices/i2c-2/new_device
> 
> That works.
> 
> lm90-i2c-2-4c
> Adapter: NVIDIA i2c adapter 
> temp1:       +29.0°C  (low  =  +0.0°C, high = +105.0°C)  
>                       (crit = +127.0°C, hyst = +117.0°C)  
> temp2:       +19.6°C  (low  = -11.0°C, high = +94.0°C)  
>                       (crit = +127.0°C, hyst = +117.0°C)  
> 
> 
> Verified that these go up when the graphics card is busy.

The values are surprising. temp1 is on the sensor chip itself, so it's
the graphics adapter's temperature. Sounds reasonable. temp2 OTOH is a
remote sensors, which typically monitors the GPU. It should be much
hotter, and can anyway not be cooler than the board.

Are you sure sensors-detect found an LM90 chip and not an LM99? The
LM99 has a 16 degrees offset on temp2, 35°C would see more reasonable.

> Where would one normally put this on an Ubuntu system?
> Somewhere in /etc/init.d, or as a line in /etc/modules, or ???

I am not familiar with Ubuntu nor Debian, so I can't help with this,
sorry.

> > > > (...)
> > > > Remaining points:
> > > > 
> > > > * Voltages: I don't know which of in4, in5 or in7 corresponds to +12V.
> > > >   I suspect in4, but I'm not certain. Please write down all the values
> > > >   displayed for +12V in the BIOS, and then all the values displayed
> > > >   for in4, in5 and in7 by "sensors". Voltage sensors almost always
> > > >   oscillate between two values, sometimes more. If in4 is +12V, then
> > > >   maybe in5 may be +3.3 Stand-By (3VSB). No idea about in7.
> > > 
> > > In4 oscillates between 3.02 and 3.04, in5 is stable at 3.36, in7 reads
> > > 2.00 or 2.02.  In the BIOS reading there is no oscillation. +12V is
> > > 11.985V and +3.3V=3.344V.
> > 
> > Did you try leaving the monitoring panel and entering it again? Maybe
> > the BIOS doesn't update the values dynamically.
> 
> Tried adding two more fans, both reasonably high current, and the 12V
> reading stayed at 11.985.  Entering and exiting the BIOS system monitor
> didn't change that.  While running linux I could make in4, in5, and in7
> shift very slightly by running a couple of copies of burnK7.  Not sure
> the result is real. In the third column no load but set governor to
> performance.  Results:
>      noload     loaded  performance
> in4  3.02,3.04  3.01    3.02,3.04
> in5  3.36       3.34    3.34 
> in7  2.00       2.90    2.66   <-- so it scales with the governor.

The the results with in7 are repeatable, then in7 is indeed used, it
isn't a negative voltage as I thought, and is also not a
"standard" (constant) voltage. I wasn't aware of any voltage changing
that way other than Vcore, so I'm stuck.

> > Anyway, I still believe that in4 is +12V, and Speedfan seems to agree.
> > I disagree with their scaling though, they apparently used a scaling
> > factor of 4.00, but this makes their reading diverge a lot from the
> > BIOS': 12.16 V instead of 11.985 V. The scaling factor is more likely
> > in the 3.94-3.97 range. I have an old nForce2 board here where they
> > used 3.963 (according to my guesses back then), maybe that's the same
> > on yours.
> 
> Hmm, could be due to the CPU speed scaling.  In the BIOS I'm pretty sure
> the CPUs are both running at their maximum speed of 2800MHz, but in
> Windows and linux they scale down to 800MHz.  Plugged a DMM into a molex

Good point.

> connector and measured this for the performance and ondemand governors:
>      2800MHz  800Mz
> 5V    5.07    5.06
> 12V  12.03    12.04
> 
> (It's a really cheap DMM, certainly not accurate to the last decimal place.)
> 
> > > The K10 temperature rises/falls more slowly than temp2 or temp3.
> > 
> > This is strange, as the digital sensor is supposed to be very close to
> > the core.
> 
> Also strange, k10temp only shows a single temperature, but it is a dual
> core system. 
> 
> cat /proc/cpuinfo | grep processor
> processor       : 0
> processor       : 1
> 
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1:       +21.4°C  (high = +70.0°C, crit = +72.0°C)  
> 
> k8temp running on a different system with Opteron 280 proessors shows
> the temperature of each core, like this:
> 
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp:  +23.0C                                    
> Core1 Temp:  +31.0C                                    

This is expected. As I understand it, the K8 sensor was per-core (or
even 2 sensors per core) while the K10 sensor is per CPU package.

> > (OTOH they claim that pin 3 of the NB FAN is not connected, which is
> > certainly wrong, otherwise you wouldn't get a speed reading for that
> > fan. So the manual may not be trustworthy.)
> 
> It wouldn't be the first time.
> 
> > There seems to be many hardware revisions of your board. For the
> > records, can you tell us which one you have?
> 
> Both the box and the board itself say "Rev 1.1".

OK, thanks for the info.

-- 
Jean Delvare

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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[Jean Delvare]

On Fri, 04 Jun 2010 10:44:00 -0700, David Mathog wrote:
> > Hmm, could be due to the CPU speed scaling.  In the BIOS I'm pretty sure
> > the CPUs are both running at their maximum speed of 2800MHz, but in
> > Windows and linux they scale down to 800MHz.  Plugged a DMM into a molex
> > connector and measured this for the performance and ondemand governors:
> >      2800MHz  800Mz
> > 5V    5.07    5.06
> > 12V  12.03    12.04
> 
> A slightly different table:
>                               DMM
> BIOS measurement  11.985    = 12.00
> W7 speedfan       12.10     = 12.02
> in4/lm_sensors    3.02/3.04 = 12.03 (2800MHz)
> in4/lm_sensors    3.02/3.04 = 12.04 (800MHz)
> 
> So it does look like 12V in the BIOS mode really is a hair lower than it
> is in either linux or W7.  Using 3.03 for the avg in4 measurement and
> 12.035 for the avg DMM measurement gives a scale factor of 3.97,
> assuming the DMM is actually correct.

This is very interesting. Even if your DMM isn't accurate for absolute
readings, using it as a comparison point for relative differences if a
very good idea. I'll try to remember it for next time.

Note that, even if the DMM was infinitely accurate, comparing the
absolute values wouldn't make much sense: Voltage scaling is achieved
by the means of resistors, the value of which is known only with
limited accuracy. Even with 1% resistors, this means the reading in the
BIOS is +/-2% of the actual voltage (not even counting the limited
resolution of the sensor, which makes things worse in practice.)

So 3.97 might be the best scaling factor for your own (physical) board,
but this doesn't mean this is the right value for the model. We'd need
many more samples to make sure, if we really cared to that degree of
detail.

My own computations, which aim at getting the same result as the BIOS
for a given voltage value, led me to a scaling factor of 3.9843. And
guess what, 255 / 64 = 3.9843. This is certainly no coincidence, and I'm
reasonably certain that this is the computation done by the BIOS:
(reg * 0xff) >> 6.

OTOH, I can't find a combination of E96 (1%) resistors that would lead
to this exact scaling factor. So it is also possible that the BIOS is
wrong (wouldn't be the first time...) in which case we don't really
have a comparison point.

The bottom line is that we should probably stop wasting our time
polishing this configuration file, we've already made a good work IMHO
and your +12V line seems to be just fine so we should leave it alone
now ;)

So this is my final version:

# lm_sensors 3 configuration file for the Gigabyte MA785GMT-UD2H motherboard
# 2010-06-05, Jean Delvare <khali@linux-fr.org>
# Written for board revision 1.1, may or may not be suitable for other
# revisions. Thanks to David Mathog for testing and reporting.
# Comments welcome!

chip "it8718-*"

### Voltages

   # in7 is mysterious, it lives in the range 2.00 to 2.90 V, and seems to
   # change with CPU frequency and possibly CPU load. No idea what it can
   # be.

   label  in0  "Vcore"
   label  in1  "Vram"    # "DDR3" in BIOS
   label  in2  "+3.3V"
   label  in3  "+5V"     # Not in BIOS
   label  in4  "+12V"
   label  in5  "3VSB"    # Not in BIOS, guessed
   ignore in6
   label  in8  "Vbat"    # Not in BIOS

   # Vcore, Vram, +3.3V and Vbat are connected directly, so no compute
   # line is needed for these. For +5V the chip is configured to use
   # internal scaling. Scaling for +12V is apparently not standard, my
   # guess is that the BIOS uses 255/64 as the scaling factor. Not sure
   # if it matches the physical reality.
   compute  in3  @ * (6.8/10+1), @ / (6.8/10+1)
   compute  in4  @ * (255/64),   @ / (255/64)

   # The BIOS won't set any limit for voltages.

   set in0_min  0.825 * 0.95
   set in0_max  1.425 * 1.05
   set in1_min  1.5   * 0.95
   set in1_max  1.6   * 1.05
   set in2_min  3.3   * 0.95
   set in2_max  3.3   * 1.05
   set in3_min  5     * 0.95
   set in3_max  5     * 1.05
   set in4_min 12     * 0.95
   set in4_max 12     * 1.05
   set in5_min  3.3   * 0.95
   set in5_max  3.3   * 1.05

### Temperatures

   # The BIOS only shows 2 temperature values, so temp1 might not be
   # actually used.

   label  temp1  "Sys Temp"    # Needs confirmation
   label  temp2  "CPU Temp"
   label  temp3  "NBr Temp"    # Guessed

   set temp1_min  10
   set temp1_max  50
   set temp2_min  10
   set temp2_max  60
   set temp3_min  10
   set temp3_max  50

### Fans

   label  fan1  "CPU Fan"
   label  fan2  "Case Fan"
   ignore fan3
   label  fan4  "NBr Fan"

   # Adjust for your own fans
   set fan1_min 1500
   set fan4_min 1000


-- 
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] Gigabyte MA785GMT-UD2H

[David Mathog]

> > lm90-i2c-2-4c
> > Adapter: NVIDIA i2c adapter 
> > temp1:       +29.0째C  (low  =  +0.0째C, high = +105.0째C)  
> >                       (crit = +127.0째C, hyst = +117.0째C)  
> > temp2:       +19.6째C  (low  = -11.0째C, high = +94.0째C)  
> >                       (crit = +127.0째C, hyst = +117.0째C)  
> > 
> > 
> > Verified that these go up when the graphics card is busy.
> 
> The values are surprising. temp1 is on the sensor chip itself, so it's
> the graphics adapter's temperature. Sounds reasonable. temp2 OTOH is a
> remote sensors, which typically monitors the GPU. It should be much
> hotter, and can anyway not be cooler than the board.
> 
> Are you sure sensors-detect found an LM90 chip and not an LM99? The
> LM99 has a 16 degrees offset on temp2, 35째C would see more reasonable.

Ran sensors-detect again and it was LM99.  So tried this instead:

echo lm99 0x4c > /sys/bus/i2c/devices/i2c-2/new_device
sensors
lm99-i2c-2-4c
Adapter: NVIDIA i2c adapter 
temp1:       +27.0캜  (low  =  +0.0캜, high = +105.0캜)  
                      (crit = +127.0캜, hyst = +117.0캜)  
temp2:       +34.9캜  (low  =  +5.0캜, high = +110.0캜)  
                      (crit = +143.0캜, hyst = +133.0캜)  

but that doesn't agree with the nvidia tools either:

nvidia-smi --query-gpu-info -a

GPU 0:
        Product Name            : Quadro FX 1400
        PCI ID                  : ce10de
        Temperature             : 38 C

Ran a graphics intensive program and did this again and both went up 5C,
so it looks like lm99 reads 3C below the actual temp fairly
consistently.  For whatever it is worth speedfan showed 40C when "idle",
but idle on W7 is probably not the same as idle on linux.  Is there a
way to add 3C to the lm99 reading in the sensors.conf file?

<SNIP>

> This is expected. As I understand it, the K8 sensor was per-core (or
> even 2 sensors per core) while the K10 sensor is per CPU package.

I thought these CPUs had both per core sensors and a package sensor. 
Why report only the last one?  Maybe because some of Brisbane chips had
broken core sensors?  This is Regor though, hopefully with working core
sensors.

Thanks,

David Mathog
mathog@caltech.edu
Manager, Sequence Analysis Facility, Biology Division, Caltech

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

Re: [lm-sensors] Gigabyte MA785GMT-UD2H

[Jean Delvare]

Hi David,

On Mon, 07 Jun 2010 09:45:58 -0700, David Mathog wrote:
> > > lm90-i2c-2-4c
> > > Adapter: NVIDIA i2c adapter 
> > > temp1:       +29.0°C  (low  =  +0.0°C, high = +105.0°C)  
> > >                       (crit = +127.0°C, hyst = +117.0°C)  
> > > temp2:       +19.6°C  (low  = -11.0°C, high = +94.0°C)  
> > >                       (crit = +127.0°C, hyst = +117.0°C)  
> > > 
> > > 
> > > Verified that these go up when the graphics card is busy.
> > 
> > The values are surprising. temp1 is on the sensor chip itself, so it's
> > the graphics adapter's temperature. Sounds reasonable. temp2 OTOH is a
> > remote sensors, which typically monitors the GPU. It should be much
> > hotter, and can anyway not be cooler than the board.
> > 
> > Are you sure sensors-detect found an LM90 chip and not an LM99? The
> > LM99 has a 16 degrees offset on temp2, 35°C would see more reasonable.
> 
> Ran sensors-detect again and it was LM99.  So tried this instead:
> 
> echo lm99 0x4c > /sys/bus/i2c/devices/i2c-2/new_device
> sensors
> lm99-i2c-2-4c
> Adapter: NVIDIA i2c adapter 
> temp1:       +27.0°C  (low  =  +0.0°C, high = +105.0°C)  
>                       (crit = +127.0°C, hyst = +117.0°C)  
> temp2:       +34.9°C  (low  =  +5.0°C, high = +110.0°C)  
>                       (crit = +143.0°C, hyst = +133.0°C)  
> 
> but that doesn't agree with the nvidia tools either:
> 
> nvidia-smi --query-gpu-info -a
> 
> GPU 0:
>         Product Name            : Quadro FX 1400
>         PCI ID                  : ce10de

6-digit PCI IDs? Wow.

>         Temperature             : 38 C

The problem is that we don't know where nvidia gets the value. Maybe
from the same sensor and they add an offset, or from another (internal)
sensor, which could explain the difference.

> Ran a graphics intensive program and did this again and both went up 5C,
> so it looks like lm99 reads 3C below the actual temp fairly
> consistently.  For whatever it is worth speedfan showed 40C when "idle",
> but idle on W7 is probably not the same as idle on linux.  Is there a
> way to add 3C to the lm99 reading in the sensors.conf file?

Yes there is:

chip "lm99-i2c-2-4c"

   compute temp2  @+3, @-3

> <SNIP>
> 
> > This is expected. As I understand it, the K8 sensor was per-core (or
> > even 2 sensors per core) while the K10 sensor is per CPU package.
> 
> I thought these CPUs had both per core sensors and a package sensor. 
> Why report only the last one?  Maybe because some of Brisbane chips had
> broken core sensors?  This is Regor though, hopefully with working core
> sensors.

I just don't know, sorry. Adding Andreas and Clemens to Cc, they may
know.

-- 
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] Gigabyte MA785GMT-UD2H

[Clemens Ladisch]

Jean Delvare wrote:
> On Mon, 07 Jun 2010 09:45:58 -0700, David Mathog wrote:
> >         Product Name            : Quadro FX 1400
> >         PCI ID                  : ce10de
> 
> 6-digit PCI IDs? Wow.

10de:00ce

> > I thought these CPUs had both per core sensors and a package sensor.
> > Why report only the last one?  Maybe because some of Brisbane chips had
> > broken core sensors?  This is Regor though, hopefully with working core
> > sensors.

The K10 CPUs have one internal temperature sensor which is shown
by k10temp, and one thermal diode that can be connected to the
motherboard's temperature sensor chip.

I see in the datasheet that revision D processors (six cores) can be
multi-node processors with two internal sensors, one for the entire CPU
and one for the second node.  As far as I can tell, these would have two
northbridge PCI devices, and the k10temp driver would be attached to
both, resulting in two separate devices with temp1_value.


Regards,
Clemens

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