Quote Originally Posted by justapost View Post
I'd need a list of smbus devices. The smbus chip is a part of the SB600/700 i guess. sensors-detect finds the SB600 here and uses the i2c-piix4 module for the smbus component.

"i2cdetect -l" shows that chip at i2c-0 here. The chip is accessible thru /dev/i2c-0 after you loaded the i2c-dev module.

"i2cdetect 0" probes what adresses have chips behind but does not run read probes on those adresses.

I assume you will get at least 0x38, 0x69, 0x50-0x53 (depends on the numer of dimms you use). On a crossfire board also 0x6e should show up.
The chips at 0x2e and 0x4e are there on the DFI 790FX and the DFI NF4. 0x2e is the troublemaker.
0x2e is SPD EEPROM on mine.
# sensors-detect revision 5016 (2007-11-11 22:20:16 +0100)
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Client found at address 0x2e
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Probing for Super-I/O at 0x2e/0x2f
Trying family `VIA/Winbond/Fintek'... Yes
Found `Winbond W83627DHG Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
AMD K10 thermal sensors... Success!
(driver `to-be-written')
Driver `w83627ehf' (should be inserted):
Detects correctly:
* ISA bus, address 0x290
Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)
Driver `to-be-written' (should be inserted):
Detects correctly:
* Chip `AMD K10 thermal sensors' (confidence: 9)

$ i2cdetect -l
Code:
i2c-0	unknown   	SMBus PIIX4 adapter at 0b00     	N/A
$ sudo i2cdetect 0
Code:
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- 2e -- 
30: -- -- -- -- -- -- -- -- 38 -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --
$ sudo i2cdump 0 0x2e
Code:
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: c5 0f 00 00 00 00 00 c0 14 62 ff ff ff ff ff ff    ??.....??b......
10: 02 00 00 ff ff ff ff ff ff ff ff ff ff ff ff ff    ?...............
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff    ................
Today i found that even the "i2cdetect -l" makes the smbus chip unusable till i restart (it does not freeze or reboot the system but i can not read out the chips with "i2cdump 0 0x69" i only get XX's as results.
This issue only occures with an phenom mounten and not with an X2 chip.
With a phenom mounten there are also smbus interfaces at 0x57 and 0x4c.
Mine seem to be similar with a few differences but I'm on SB600 not SB700 and 770 chipset. HIH