On Thu, 11 Apr 2019 21:08:54 +0100, Dreamcat4 wrote: > [root:/sys/bus/i2c/devices] # cat /sys/bus/i2c/drivers/ee1004/2-0050/eeprom > cat: /sys/bus/i2c/drivers/ee1004/2-0050/eeprom: No such device or address > > and that command ^ causes this error msg in dmesg log: > > dmesg -w > [12555.445082] ee1004 2-0050: Failed to select page 0 (-6) OK, so the problem is that the EEPROMs on your memory modules do not behave the way the ee1004 driver expects. I thought EE1004 was a standard for all DDR4 modules... I have no satisfactory explanation for what you observe. Either Crucial used non-standard SPD EEPROMs, or the SMBus controller is messing up with the commands before they reach the EEPROMs. But both are pretty unlikely. Out of curiosity, what's your SMBus controller? # lspci -nn | grep SMBus > [root:/sys/bus/i2c/devices] # 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: -- -- -- -- -- 08 -- -- -- -- -- -- -- > 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: 30 -- -- -- 34 35 UU UU -- -- -- -- -- -- -- -- > 40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- -- > 50: UU -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > [root:/sys/bus/i2c/devices] # > > The 'UU' at locations 0x50 and 0x52 is bad thing, right? No, it's OK once the right driver is bound to the devices. -- Jean Delvare SUSE L3 Support
