From Ticket 1972, Gigabyte 7dpxdw+, making it work correctly

From Ticket 1972, Gigabyte 7dpxdw+, making it work correctly

[Douglas Bollinger]

This is from Ticket #1972, Gigabyte 7dpxdw+, making it work correctly

> the lm90 chip, driver, and userspace supports two temperatures.  are you
> saying that only one is reported or only one is correct?  If only one is
> reported check that the other is not set to ignore in /etc/sensors.conf.
> If incorrect you can try adjusting with a compute line in sensors.conf.
> If you need more help follow up by email, ref. your ticket number.
> MDS 5/4/05

Sorry, I should have been more precise.  This is a duallie board, so the
LM90 needs to support TWO external temperatures, instead of the usual one,
along with the usual on-the-chip sensor.  That is what is so special (or
odd) about this board.

Here's a sensor output of what I have so far:

******
doug@ghidorah etc $ sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1:   +1.52 V  (min =  +1.52 V, max =  +1.68 V)       ALARM
VCore 2:   +1.52 V  (min =  +1.52 V, max =  +1.68 V)       ALARM
+3.3V:     +3.10 V  (min =  +3.14 V, max =  +3.47 V)
+5V:       +4.73 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
+12V:     +11.49 V  (min = +10.82 V, max = +13.19 V)
-12V:     -12.03 V  (min = -13.18 V, max = -10.80 V)
-5V:       -5.05 V  (min =  -5.25 V, max =  -4.75 V)
V5SB:      +5.35 V  (min =  +4.76 V, max =  +5.24 V)
VBat:      +3.20 V  (min =  +2.40 V, max =  +3.60 V)
fan1:        0 RPM  (min =    0 RPM, div = 2)
fan2:        0 RPM  (min =    0 RPM, div = 2)
fan3:        0 RPM  (min =    0 RPM, div = 2)
temp1:       +30 C  (high =  +127 C)                     sensor = thermistor 
temp2:     +32.0 C  (high =  +127 C, hyst =  +128 C)   sensor = thermistor 
temp3:     +37.5 C  (high =  +127 C, hyst =  +128 C)   sensor = thermistor 
vid:      +1.600 V  (VRM Version 9.0)
alarms:   Chassis intrusion detection                      ALARM
beep_enable:
          Sound alarm disabled

eeprom-i2c-1-53
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-1-52
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-1-51
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

eeprom-i2c-1-50
Adapter: SMBus AMD768 adapter at 50e0
Memory type:            DDR SDRAM DIMM
Memory size (MB):       512

lm90-i2c-1-4c
Adapter: SMBus AMD768 adapter at 50e0
M/B Temp:    +49 C  (low  =    +0 C, high =   +70 C)
CPU Temp:  +81.2 C  (low  =  +0.0 C, high = +70.0 C)   ALARM
M/B Crit:    +85 C  (hyst =   +75 C)
CPU Crit:    +85 C  (hyst =   +75 C)

Philips NTSC -i2c-0-61
Adapter: bt878 #0 [sw]

tveeprom-i2c-0-50
Adapter: bt878 #0 [sw]
******

From the w83627hf: the voltage readings are OK, the fan RPM readings are OK
as none of my fans have tach lines and the 3 temp. readings are a mystery.
They have nothing to do with the CPU temps.

Skipping down to the lm90, I assume the M/B Temp is the "on-the-chip"
sensor and the CPU temp is the one external temp reading that works.  If I
stall a CPU fan this reading will rise, so this one is good.  Of course,
it's way too high, but that's the way it shows in the BIOS and that's easy
enough to fix anyway.  

The problem is that the lm90 should have one more external temp for the 2nd
CPU.

The website to this Windows program:

http://mbm.livewiredev.com/

The motherboard list of the above website shows the GA7 DPXDW+ with a
LM90-1 remote and a LM90-2 remote.  Alas, the program is closed source so
it's not much help.  The author also quit supporting this program so I
suppose emailing him and asking how he did it wouldn't be much help either.

-- 
"Rights" is a fictional abstraction.  No one has "Rights", neither machines
nor flesh-and-blood.  Persons... have opportunities, not rights, which they
use or do not use.
		-- Lazarus Long

From Ticket 1972, Gigabyte 7dpxdw+, making it work correctly

[Jean Delvare]

Hi Douglas,

> This is from Ticket #1972, Gigabyte 7dpxdw+, making it work correctly
> 
> > the lm90 chip, driver, and userspace supports two temperatures.  are
> > you saying that only one is reported or only one is correct?  If
> > only one is reported check that the other is not set to ignore in
> > /etc/sensors.conf. If incorrect you can try adjusting with a compute
> > line in sensors.conf. If you need more help follow up by email, ref.
> > your ticket number. MDS 5/4/05
> 
> Sorry, I should have been more precise.  This is a duallie board, so
> the LM90 needs to support TWO external temperatures, instead of the
> usual one, along with the usual on-the-chip sensor.  That is what is
> so special (or odd) about this board.

First, I invite you to read the following thread:
http://archives.andrew.net.au/lm-sensors/msg28081.html

Your board supposedly uses a Philips PCA9540 chip to switch from one
LM90 to the other one (there are two of these on the board). We have no
driver for it in Linux 2.6, only Linux 2.4 - and even there the driver
plain sucks. You may get some results with i2cset. First look for a chip
at 0x70 on the smbus (use i2cdetect), then use "i2cset N 0x70 4 4" or
"i2cset N 0x70 5 5" to select the first or second LM90 (where N is the
bus number, supposedly 1 in your case).

Blame Gigabyte for the poor design. They really could have come up with
a much simpler one.

> From the w83627hf: the voltage readings are OK, the fan RPM readings
> are OK as none of my fans have tach lines and the 3 temp. readings
> are a mystery. They have nothing to do with the CPU temps.

They may be thermal sensors anywhere on the board.

> Skipping down to the lm90, I assume the M/B Temp is the "on-the-chip"
> sensor and the CPU temp is the one external temp reading that works.

Correct.

> If I stall a CPU fan this reading will rise, so this one is good.  Of
> course, it's way too high, but that's the way it shows in the BIOS and
> that's easy enough to fix anyway.  
> 
> The problem is that the lm90 should have one more external temp for
> the 2nd CPU.

In fact this is done by a second LM90 chip, as explained above.

> The website to this Windows program:
> 
> http://mbm.livewiredev.com/
> 
> The motherboard list of the above website shows the GA7 DPXDW+ with a
> LM90-1 remote and a LM90-2 remote.  Alas, the program is closed source
> so it's not much help.  The author also quit supporting this program
> so I suppose emailing him and asking how he did it wouldn't be much
> help either.

Alex van Kaam, who wrote MBM, has been working with us on this actually,
he is the one who found how the board was wired and told us how we could
handle the multiplexing. We did not properly implement support for it
out of time and motivation, but Alex has been really helpful.

-- 
Jean Delvare

From Ticket 1972, Gigabyte 7dpxdw+, making it work correctly

[Douglas Bollinger]

On Sun, 8 May 2005 14:01:54 +0200
Jean Delvare <khali@linux-fr.org> wrote:

> First, I invite you to read the following thread:
> http://archives.andrew.net.au/lm-sensors/msg28081.html

Thanks, that thread explains alot.  So the trick was to use 2 LM90s.
Gigabyte making easy things hard.

<snip>
> Alex van Kaam, who wrote MBM, has been working with us on this actually,
> he is the one who found how the board was wired and told us how we could
> handle the multiplexing. We did not properly implement support for it
> out of time and motivation, but Alex has been really helpful.

At least now I understand it just won't work and the ticket database is
updated to that fact as well.  From some of the previous entries, it almost
seemed like CPU temps were working for this board, but I think those users
were fooled by the bogus W83627HF temp readings.  Actually, those temp
readings probably are from the CPU sockets, but obviously those readings
aren't nearly as desirable as getting a temp directly from the CPU itself
via the LM90s.

Thanks for taking the time to look into this.

-- 
Don't you wish that all the people who sincerely want to help you
could agree with each other?