Re: dmi_scan on x86_64

[Daniel Egger]

On 04.11.2004, at 14:02, Jean Delvare wrote:

> The (admittedly limited) documentation [1] I have for the S2875 states
> that only 3 of the 6 fan headers have their tachometer pin wired. This
> matches the W83627HF hardware monitoring chip capabilities, which is 
> why
> I see no evidence of any kind of multiplexing on that board.

Ah, I start to make sense of what exactly you're doing.

> Not all SMBus clients are hardware monitoring chips. The fact that
> sensors-detect didn't recognize it would even suggest that your unknown
> chip isn't. What you see may be about anything, including
> pseudo-clients used for the SMBus protocol itself.

> Feel free to submit a dump (using i2cdump) of that unknown chip if you
> want me to comment on it.

egger@ulli:~$ sudo i2cdetect -l
i2c-2   unknown         SMBus2 AMD8111 adapter at c400          
Algorithm unavailable
i2c-1   dummy           ISA main adapter                        ISA bus 
algorithm
i2c-0   unknown         SMBus AMD756 adapter at 50e0            
Algorithm unavailable

egger@ulli:~$ sudo i2cdetect 2
WARNING! This program can confuse your I2C bus, cause data loss and 
worse!
I will probe file /dev/i2c-2.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          XX XX XX XX XX 08 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

egger@ulli:~$ sudo i2cdump 2 8
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and 
worse!
I will probe file /dev/i2c-2, address 0x8, mode byte
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX

Anything else I can try?

Servus,
      Daniel

Attachment: PGP.sig
Description: This is a digitally signed message part