Ticket #649 (closed task)
Opened 7 years ago
unidentifiable chips on Acer M25C 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 1100 1U 2xPIII machine (Acer M25C motherboard; also used in the
Acer Altos 1200) with ServerWorks? III LE chip set (OSB4 Southbridge).
'sensors-detect' finds the bus OK, but can't identify the sensor chips.
Unfortunately, I don't have adequate documentation for the board or physical
access to the machine right now.
Here's some relevant output:
Next adapter: SMBus OSB4 adapter at 0e80 (Non-I2C SMBus adapter)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x60
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 0x61
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!
and i2cdump:
# ./i2cdump 0 0x60 b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0, address 0x60, 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: 66 11 09 00 47 01 00 22 06 00 00 06 08 20 80 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 00 00 00 00 00 00 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 7e 00 81 14 00 6b 00 00 00 6f
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: 40 2a aa aa 80 07 44 01 01 1e 81 00 04 04 00 00
80: 00 20 00 00 20 40 00 00 00 00 00 00 00 00 00 00
90: ff 02 09 00 2f 30 fe 18 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: ff bf fe 7f 53 ca fa 53 7f fd f7 ff ff df fe df
c0: 00 41 8f 43 90 43 af 43 00 00 59 20 0d 07 00 48
d0: 00 20 fc 3f 4c 17 00 43 c0 02 08 41 01 80 10 93
e0: 04 0b 00 00 00 00 00 00 27 02 00 00 00 00 00 00
f0: 00 37 40 02 00 00 00 00 00 00 00 00 60 18 00 00
# ./i2cdump 0 0x61 b
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c/0, address 0x61, 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: 66 11 09 00 47 01 00 02 06 00 00 06 08 20 80 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 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: 00 00 00 00 01 01 00 00 00 00 00 0b 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 00 00 00 00 00 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: b0 43 bf 43 c0 43 cf 43 54 01 00 00 0d 07 00 00
d0: 00 40 fc 4f 00 00 00 00 00 00 00 00 01 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 10 60 00 00 00 00 00 00 00 00 00 61 18 00 00
Any ideas? --- Sorry.
Best bet is to look at the board.
Haven't seen devices at 0x60-61 before.
If you figure it out let us know.
Follow up by emailing sensors@… and reference
your ticket number.
MDS 7/28/01
