Ticket #650 (closed task)
Opened 7 years ago
can't find ADM1024 on Intel SKA4 board (Examined/Solved - lm_sensors 2.6.0 Linux 2.2.15-3SGI_32smp)
| Reported by: | contact | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | hardware | Version: | |
| Keywords: | Cc: |
Description
Hi,
I have an SGI 1450 4xPIII Xeon machine (Intel SKA4 motherboard) with ServerWorks?
Champion 2HE chipset (OSB4 Southbridge).
'sensors-detect' finds the bus OK, but can't find the ADM1024 sensor chip
which is meant to be on there, according to the documentation at Intel. The same
documentation says that the ADM1024 is "on a secondary private I2C bus", which I
don't understand, but mentions the addresses 0x30, 0x98, 0x34 and 0x9c for
CPU0-4 temperatures. The eeprom hookup is recognized at 0x50, 0x52, 0x54 and
0x56 and seems to work fine.
Here's some 'sensors-detect' output:
Next adapter: SMBus OSB4 adapter at 0580 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x30
Probing for 'National Semiconductor LM78'... Failed!
Probing for 'National Semiconductor LM78-J'... Failed!
Probing for 'National Semiconductor LM79'... Failed!
Probing for 'Winbond W83781D'... Failed!
Probing for 'Winbond W83782D'... Failed!
Probing for 'Winbond W83783S'... Failed!
Probing for 'Winbond W83627HF'... Failed!
Probing for 'Asus AS99127F'... Failed!
Client found at address 0x32
Probing for 'National Semiconductor LM78'... Failed!
Probing for 'National Semiconductor LM78-J'... Failed!
Probing for 'National Semiconductor LM79'... Failed!
Probing for 'Winbond W83781D'... Failed!
Probing for 'Winbond W83782D'... Failed!
Probing for 'Winbond W83783S'... Failed!
Probing for 'Winbond W83627HF'... Failed!
Probing for 'Asus AS99127F'... Failed!
Client found at address 0x34
Probing for 'National Semiconductor LM78'... Failed!
Probing for 'National Semiconductor LM78-J'... Failed!
Probing for 'National Semiconductor LM79'... Failed!
Probing for 'Winbond W83781D'... Failed!
Probing for 'Winbond W83782D'... Failed!
Probing for 'Winbond W83783S'... Failed!
Probing for 'Winbond W83627HF'... Failed!
Probing for 'Asus AS99127F'... Failed!
Client found at address 0x36
Probing for 'National Semiconductor LM78'... Failed!
Probing for 'National Semiconductor LM78-J'... Failed!
Probing for 'National Semiconductor LM79'... Failed!
Probing for 'Winbond W83781D'... Failed!
Probing for 'Winbond W83782D'... Failed!
Probing for 'Winbond W83783S'... Failed!
Probing for 'Winbond W83627HF'... Failed!
Probing for 'Asus AS99127F'... Failed!
running i2cdump at these addresses fails, e.g.:
# ./i2cdump 0 0x30 b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0, address 0x30, mode byte
You have five seconds to reconsider and press CTRL-C!
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
--- sensors-detect bug in finding adm1024 is fixed in CVS.
Module should work even if sensors-detect can't find the chip,
if it is on the bus, but it must be at 0x2c-0x2e.
'secondary private i2c bus' probably == 'proprietary i2c bus',
i.e. we don't have a driver for it and even sensors-detect CVS
won't find it. Sorry.
0x30-0x36 are eeprom shadows, not sensors.
Unless you find something where i2cdump shows something but XX
you are out of luck.
Sorry.
If you get more info on the secondary i2c bus let us know,
follow up by emailing sensors@… and
reference your ticket number.
MDS 7/28/01
