Ticket #2182 (closed defect: fixed)

Opened 7 years ago

Last modified 4 years ago

Dell Poweredge 830 - sensors all display 0 values

Reported by: dan.walker.uce@… Owned by: khali
Priority: minor Milestone: 3.1.1
Component: hardware Version:
Keywords: Cc: tm31415@…, dukat@…

Description

Hi

I'm trying to use lm-sensors on a Dell Poweredge 830 server, running Ubuntu Edgy. Everything seems to install OK, but this is what I get when I run sensors:

dan@Panoramix:~$ sudo sensors

lm85-i2c-0-2e
Adapter: SMBus I801 adapter at 08c0

V1.5:       +0.00 V  (min =  +1.42 V, max =  +1.58 V)   
VCore:      +0.00 V  (min =  +1.03 V, max =  +1.14 V)   
V3.3:       +0.00 V  (min =  +3.13 V, max =  +3.47 V)   
V5:        +0.00 V  (min =  +4.74 V, max =  +5.26 V)   
V12:       +0.00 V  (min = +11.38 V, max = +12.62 V)   
CPU_Fan:      0 RPM  (min = 4000 RPM)                     ALARM
fan2:         0 RPM  (min =    0 RPM)                     ALARM
fan3:         0 RPM  (min =    0 RPM)                     ALARM
fan4:         0 RPM  (min =    0 RPM)                     ALARM
CPU:          +0°C  (low  =   +10°C, high =   +50°C)       
Board:        +0°C  (low  =   +10°C, high =   +35°C)      
Remote:       +0°C  (low  =   +10°C, high =   +35°C)       
CPU_PWM:   255
Fan2_PWM:  255
Fan3_PWM:  255
vid:      +1.087 V  (VRM Version 10.0)

I have read that Dell machines are sometimes difficult to configure, but I really don't know where to start. Any pointers?

Many thanks

Change History

  Changed 7 years ago by khali

  • reporter changed from ticket to dan.walker.uce@…

follow-up: ↓ 3   Changed 6 years ago by khali

  • owner changed from somebody to khali
  • status changed from new to assigned

It might be a misdetection and you don't really have an LM85 chip. What messages does the lm85 driver log when you load it? It seems that it went into "generic" mode, meaning that it did not actually recognize any of the devices it supports.

Do you have any reason to believe that the Dell Poweredge 830 server includes a hardware monitoring chip? And if so, any reason to believe that this chip would be an LM85 or compatible?

I am curious what a  recent version of sensors-detect would detect (after unloading the lm85 driver).

in reply to: ↑ 2   Changed 6 years ago by ticket

Thanks khali. I'm not the reporter, but I suffered from this for years ;-) I use PowerEdge? 800 with Debian and has the same problem.

It is said that the PowerEdge? sensor chips are "hidden", but the post is quite old, so the situation may be different now.  http://archives.andrew.net.au/lm-sensors/msg22269.html

The following is the result of sensors-detect with your version.

btw, Could you add my e-mail address (tm31415 at csc.jp) to the CC of this ticket?

T. Makino

# sensors
lm85-i2c-0-2e
Adapter: SMBus I801 adapter at 08c0
V1.5:       +0.00 V  (min =  +0.00 V, max =  +3.32 V)
VCore:      +0.00 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:       +0.00 V  (min =  +0.00 V, max =  +4.38 V)
V5:         +0.00 V  (min =  +0.00 V, max =  +6.64 V)
V12:        +0.00 V  (min =  +0.00 V, max = +15.94 V)
CPU_Fan:      0 RPM  (min =    0 RPM)                     ALARM
fan2:         0 RPM  (min =    0 RPM)                     ALARM
fan3:         0 RPM  (min =    0 RPM)                     ALARM
fan4:         0 RPM  (min =    0 RPM)                     ALARM
CPU Temp:     +0 C  (low  =  -127 C, high =  +127 C)
Board Temp:
              +0 C  (low  =  -127 C, high =  +127 C)
Remote Temp:
              +0 C  (low  =  -127 C, high =  +127 C)
CPU_PWM:   255
Fan2_PWM:  255
Fan3_PWM:  255
vid:      +1.087 V  (VRM Version 10.0)
# rmmod lm85
# perl ./sensors-detect.perl
# sensors-detect revision $Revision$

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no): yes
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801FB ICH6

We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
If you have undetectable or unsupported I2C/SMBus adapters, you can have
them scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.

Next adapter: SMBus I801 adapter at 08c0 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2e
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM78-J'...              No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85 or LM96000'...     Success!
    (confidence 7, driver `lm85')
Probing for `Analog Devices ADM1027, ADT7460 or ADT7463'... No
Probing for `SMSC EMC6D100, EMC6D101 or EMC6D102'...        No
Probing for `Analog Devices ADT7462'...                     No
Probing for `Analog Devices ADT7467 or ADT7468'...          No
Probing for `Analog Devices ADT7470'...                     No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7475'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `National Semiconductor LM93'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Winbond W83791SD'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG'...                          No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L786NR/NG/R/G'...                   No
Probing for `Winbond W83L785TS-S'...                        No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `Analog Devices ADM1028'...                     No
Probing for `ITE IT8712F'...                                No
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           No
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Analog Devices ADM1024'...                     No
Probing for `Winbond W83791D'...                            No
Client found at address 0x44
Probing for `Maxim MAX6633/MAX6634/MAX6635'...              No
Client found at address 0x50
Handled by driver `eeprom' (already loaded), chip type `eeprom'
    (note: this is probably NOT a sensor chip!)
Client found at address 0x52
Handled by driver `eeprom' (already loaded), chip type `eeprom'
    (note: this is probably NOT a sensor chip!)

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'...                   Yes
Found `Nat. Semi. PC8374L Super IO Sensors'
    (but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Trying family `ITE'...                                      No

Some south bridges, CPUs or memory controllers may also contain
embedded sensors. Do you want to scan for them? (YES/no):
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD K10 thermal sensors...                                  No
Intel Core family thermal sensor...                         No
Intel AMB FB-DIMM thermal sensor...                         No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `lm85' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 08c0'
    Busdriver `i2c-i801', I2C address 0x2e
    Chip `National Semiconductor LM85 or LM96000' (confidence: 7)

Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):

#----cut here----
# I2C adapter drivers
modprobe i2c-i801
# Chip drivers
modprobe lm85
/usr/bin/sensors -s
#----cut here----

If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.

  Changed 6 years ago by khali

  • cc tm31415@… added

Can you please provide a dump of the I2C device at address 0,0x2e (the one which is supposed to be LM85-compatible)? The following commands (as root) should get the dump:

modprobe i2c-dev
i2cdump 0 0x2e b > poweredge-0x2e.dump

Ideally I'd like you to get the dump after a cold reboot and before the lm85 driver is loaded. If that's not possible then just unload the lm85 driver before running the commands.

  Changed 6 years ago by ticket

I'm not on the site of the machine, and I'm too chicken to challenge rebooting the machine remotely. So this is the data just after unloading lm85 driver (and also unloaded some drivers that have been installed during my trial to install Dell OpenManage? server assistant, that seems to report some sensor values). I'll try cold booting within the next two weeks.

# i2cdump 0 0x2e b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x2e, mode byte
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 01 68    ..............?h
40: 05 80 3c 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ??<...........??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
60: c4 c4 00 00 80 80 80 00 00 00 64 64 64 44 44 a4    ??..???...dddDD?
70: ff ff ff 00 00 00 08 00 00 22 6e 6e 6e 00 00 00    ......?.."nnn...
80: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00    ........?.......

And this is the kernel log at the load of lm85.

Apr 28 10:06:49 debian kernel: i2c_adapter i2c-0: Unrecognized version/stepping 0x68 Defaulting to LM85.

Hope this helps. T. Makino

  Changed 6 years ago by khali

  • status changed from assigned to closed
  • resolution set to wontfix

The device at 0x2e is really a National Semiconductor LM96000, for which we have no dedicated support, but which is supported by the lm85 driver in generic mode.

The odd thing is that all inputs appear to be grounded. The device's status is correct (the "ready" and "start" bits of the configuration register are both set.) I have no idea why a system manufacturer would include a hardware monitoring chip to not use its feature at all. Maybe it's monitoring an optional part of the server, which you don't have?

As far as I can see the driver does its job properly (except for the lack of dedicated support) so there's not much we can do. Please ask Dell for additional information about how the hardware monitoring is supposed to be done on this server (if it is supported at all.) Without this information there's simply nothing we can do. I am thus closing this ticket as wontfix - but I'll be glad to reopen it if additional information is available and something needs to be done with it on our end.

  Changed 6 years ago by khali

  • status changed from closed to reopened
  • resolution wontfix deleted

Herbert Pötzl made me notice that the dump has a strange value for register 0x6f. So I would like to ask you to try the following sequence:

# rmmod lm85
# i2cset -y 0 0x2e 0x40 0x04
# i2cset -y 0 0x2e 0x6f 0x00
# i2cset -y 0 0x2e 0x40 0x05
# modprobe lm85

I wonder if this will unstuck the chip. Chances are thin, I'd say, but it's worth trying.

  Changed 6 years ago by ticket

Unfortunately, it didn't work. I tried i2cdump again and the register 0x6f seems no longer interesting... anyway, here is the result.

# sensors
lm85-i2c-0-2e
Adapter: SMBus I801 adapter at 08c0
V1.5:       +0.00 V  (min =  +0.00 V, max =  +3.32 V)
VCore:      +0.00 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:       +0.00 V  (min =  +0.00 V, max =  +4.38 V)
V5:         +0.00 V  (min =  +0.00 V, max =  +6.64 V)
V12:        +0.00 V  (min =  +0.00 V, max = +15.94 V)
CPU_Fan:      0 RPM  (min =    0 RPM)                     ALARM
fan2:         0 RPM  (min =    0 RPM)                     ALARM
fan3:         0 RPM  (min =    0 RPM)                     ALARM
fan4:         0 RPM  (min =    0 RPM)                     ALARM
CPU Temp:     +0°C  (low  =  -127°C, high =  +127°C)
Board Temp:
              +0°C  (low  =  -127°C, high =  +127°C)
Remote Temp:
              +0°C  (low  =  -127°C, high =  +127°C)
CPU_PWM:   255
Fan2_PWM:  255
Fan3_PWM:  255
vid:      +1.087 V  (VRM Version 10.0)

# rmmod lm85
# i2cset -y 0 0x2e 0x40 0x04
No size specified (using byte-data access)
Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory
# modprobe i2c-dev
# i2cset -y 0 0x2e 0x40 0x04
No size specified (using byte-data access)
Value 0x04 written, readback matched
# i2cset -y 0 0x2e 0x6f 0x00
No size specified (using byte-data access)
Value 0x00 written, readback matched
# i2cset -y 0 0x2e 0x40 0x05
No size specified (using byte-data access)
Value 0x05 written, readback matched
# modprobe lm85
# sensors
lm85-i2c-0-2e
Adapter: SMBus I801 adapter at 08c0
V1.5:       +0.00 V  (min =  +0.00 V, max =  +3.32 V)
VCore:      +0.00 V  (min =  +0.00 V, max =  +2.99 V)
V3.3:       +0.00 V  (min =  +0.00 V, max =  +4.38 V)
V5:         +0.00 V  (min =  +0.00 V, max =  +6.64 V)
V12:        +0.00 V  (min =  +0.00 V, max = +15.94 V)
CPU_Fan:      0 RPM  (min =    0 RPM)                     ALARM
fan2:         0 RPM  (min =    0 RPM)                     ALARM
fan3:         0 RPM  (min =    0 RPM)                     ALARM
fan4:         0 RPM  (min =    0 RPM)                     ALARM
CPU Temp:     +0°C  (low  =  -127°C, high =  +127°C)
Board Temp:
              +0°C  (low  =  -127°C, high =  +127°C)
Remote Temp:
              +0°C  (low  =  -127°C, high =  +127°C)
CPU_PWM:   255
Fan2_PWM:  255
Fan3_PWM:  255
vid:      +1.087 V  (VRM Version 10.0)

# i2cdump 0 0x2e b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x2e, mode byte
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 01 68    ..............?h
40: 05 80 3c 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ??<...........??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
60: c4 c4 00 00 80 80 80 00 00 00 64 64 64 44 44 00    ??..???...dddDD.
70: ff ff ff 00 00 00 08 00 00 22 6e 6e 6e 00 00 00    ......?.."nnn...
80: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00    ........?.......

  Changed 6 years ago by khali

OK, so it didn't make a difference. Sorry for the false hope.

follow-up: ↓ 11   Changed 5 years ago by ticket

i have the same problem altough with a total different board: intel dg45id (g45+ich10r)

neighter of those documents provide any detailed information about hw monitoring:

product guide/manual:  http://download.intel.com/support/motherboards/desktop/dg45id/sb/e3002101_en.pdf

"tech" spec  http://download.intel.com/support/motherboards/desktop/dg45id/sb/e35960001us.pdf

i tried to "unstuck" the chip as khali suggested and it did the same thing (resetting 0x6f to 00):

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 01 68    ..............?h
40: 05 80 3c 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ??<...........??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
60: c4 c4 00 00 80 80 80 00 00 00 64 64 64 44 44 00    ??..???...dddDD.
70: ff ff ff 00 00 00 08 00 00 22 6e 6e 6e 00 00 00    ......?.."nnn...
80: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00    ........?.......

but that did not change anything regarding sensors' output.

i dont have time now, but i could search on the board itself for any chips.

sensors -v
sensors version 3.0.2 with libsensors version 3.0.2
uname -a
Linux tuxi 2.6.27-7-generic #1 SMP Fri Oct 24 06:40:41 UTC 2008 x86_64 GNU/Linux

in reply to: ↑ 10   Changed 5 years ago by ticket

ive noticed, that the data sheet of the southbridge mentions a fan sensor/controller and temp sensors...  http://developer.intel.com/Assets/PDF/datasheet/319973.pdf

so maybe im wrong to reply to this ticket altogether? :)

follow-up: ↓ 13   Changed 5 years ago by khali

Yes, the ICH10 has integrated sensors, and it is entirely possible that this is what is used on your motherboard. However the original report was for an ICH6 which doesn't have such integrated sensors. And anyway, even if your ICH10's integrated sensors are used, this still doesn't explain the presence of a seemingly disabled LM96000 on your system.

So the mystery remains at this point.

in reply to: ↑ 12   Changed 5 years ago by ticket

there is no other monitoring chip on the board (dg45id). the only suspicious ic is a winbond WPCD377I, which is used to interface with special infrared receivers/senders (consumer ir, cir). i dont know if it has monitoring features as well.

can i do anything else (to get them working)?

  Changed 5 years ago by khali

Aha! Thanks for opening my eyes. The explanation has been there in front of me since the beginning and I just couldn't see it.

What the sensors-detect script detected on the SMBus isn't a physical LM96000 chip, but a compatible interface exposed by the PC8374L Super I/O (or WPCD377I, they are compatible.) I just looked at the PC8374L datasheet and the vendor ID and device ID exposed on the SMBus are the same at those of the LM96000, which is why sensors-detect reported an LM96000.

This partly explains why the supposedly LM96000 chip reports all 0 values: sensors-detect also says that the PC8374L's hardware monitoring logical device is disabled. So I guess that something needs to be enabled through the LPC interface before the emulated LM96000 chip will start reporting values. Not too sure about the WPCD377I though, as this is supposed to be a "legacy reduced" chip and its description doesn't mention hardware monitoring at all.

Please provide a dump of the logical device 8 of your Super-I/O:

isadump 0x2e 0x2f 8

  Changed 5 years ago by ticket

I will probe address register 0x2e and data register 0x2f.
Probing bank 8 using bank register 0x07.
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41 
20: f1 01 00 00 01 01 00 91 00 11 2e 00 00 10 00 00 
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

  Changed 5 years ago by khali

OK, the logical device is disabled (as sensors-detect reported). I would like you to try and enable it and see if it makes the LM96000 more responsive:

isaset -y 0x2e 0x2f 0x07 8
isaset -y 0x2e 0x2f 0x30 1

You can disable it again with the following sequence:

isaset 0x2e 0x2f 0x07 8
isaset 0x2e 0x2f 0x30 0

If this doesn't help, maybe we need to give the logical device an address before enabling it.

  Changed 5 years ago by ticket

mh im not sure how "more responsive" would look like. after reloading the lm85 module sensors still shows just zeros. here are the dumps after enabling the logical device:

isadump 0x2e 0x2f 8
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x2e and data register 0x2f.
Probing bank 8 using bank register 0x07.
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 41 
20: f1 01 00 00 01 01 00 91 00 11 2e 00 00 10 00 00 
30: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
70: 00 03 00 00 04 04 00 00 00 00 00 00 00 00 00 00 
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
f0: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

i2cdump 0 0x2e b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x2e, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
20: 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff    ................
30: ff ff ff 00 00 00 00 00 00 00 00 00 00 00 01 68    ..............?h
40: 05 80 3c 00 00 ff 00 ff 00 ff 00 ff 00 ff 81 7f    ??<...........??
50: 81 7f 81 7f ff ff ff ff ff ff ff ff 62 62 62 c4    ????........bbb?
60: c4 c4 00 00 80 80 80 00 00 00 64 64 64 44 44 a4    ??..???...dddDD?
70: ff ff ff 00 00 00 08 00 00 22 6e 6e 6e 00 00 00    ......?.."nnn...
80: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ?...............
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00    ........?.......

  Changed 5 years ago by khali

So that didn't work... Let's try once more with a proper I/O address. First you need to find a free I/O port range. Check in /proc/ioports, you need 16 consecutive free ports, first port being a multiple of 16. I will use address 0x290 in the example below, please make sure you adjust to something that is suitable for your system if 0x290-0x29f isn't free.

isaset 0x2e 0x2f 0x07 8
isaset 0x2e 0x2f 0x30 0
isaset 0x2e 0x2f 0x60 0x02
isaset 0x2e 0x2f 0x61 0x90
isaset 0x2e 0x2f 0x30 1

Then try reloading the lm85 driver and see if you finally get non-zero readings.

  Changed 5 years ago by ticket

for the log:
tried without success. khali mailed nuvoton to ask whether the WPCD377I has sensors or not.

  Changed 5 years ago by khali

I got a reply from Nuvoton: they confirm that the WPCD377i is a "feature reduced" super-I/O and there is no HM feature.

So there is probably no way to get the "emulated" LM96000 chip to work on your system. This would mean that the monitored value must come from a different chip. The ICH10 would be a good candidate for the temperatures and fans, but it doesn't not include voltage sensors as far as I know. That being said, the ICH10 has a SST pin, to which voltage sensors could be connected. So maybe it's the ICH10 after all. Either that, or another monitoring chip not yet known to sensors-detect.

At this point, I don't know if this conclusion can be generalized to all users who reported this all-zero LM96000 issue or not.

  Changed 5 years ago by ticket

Hi, I've also got an Intel DG45ID with the exact same problem (and no solution). Could you add my email 'dukat@…', so I'll be notified if there is progress?

  Changed 5 years ago by khali

  • cc dukat@… added

  Changed 5 years ago by khali

r5660 adds detection of the Winbond WPCD377I on the SMBus. This will avoid misdetections and false hopes ;) The LPC detection is still confusing though.

  Changed 5 years ago by khali

r5680 fixed the LPC detection as well. This solves the user-space part of the issue. Remaining is the lm85 driver, which should be improved to detect the WPCD377I and ignore it.

  Changed 4 years ago by khali

  • status changed from reopened to closed
  • resolution set to fixed
  • milestone set to 3.1.1
Note: See TracTickets for help on using tickets.