On Mon, 15 Apr 2019 15:45:24 +0100, Dreamcat4 wrote: > Jean, I have just tried different ram kit in same motherboard. And it > does not seem to be doing much differently, its same behaviour, same > error messages. > > [root:~] # ./decode-dimms.new > Cannot read /sys/bus/i2c/drivers/ee1004/2-0050/eeprom at > ./decode-dimms.new line 2358. > > dmesg -w > [ 763.518594] ee1004 2-0050: Failed to select page 0 (-6) > > > decode-dimms (older version with ubuntu distribution): > > [root:/] # decode-dimms > No EEPROM found, try loading the eeprom or at24 module > [root:/] # decode-dimms > No EEPROM found, try loading the eeprom or at24 module > [root:/] # decode-dimms > No EEPROM found, try loading the eeprom or at24 module > [root:/] # decode-dimms > No EEPROM found, try loading the eeprom or at24 module > [root:/] # I don't think your old script knows about the ee1004 driver anyway, so it has no chance to work. > other command: > [root:/] # modprobe i2c-dev > [root:/] # i2cdetect 2 > Error: Could not open file `/dev/i2c-2' or `/dev/i2c/2': No such file > or directory > [root:/] 1 # cd /sys/bus/i2c/devices/ > [root:/sys/bus/i2c/devices] # ls > i2c-0 i2c-1 > [root:/sys/bus/i2c/devices] # sudo modprobe i2c-i801 > [root:/sys/bus/i2c/devices] # ls > i2c-0 i2c-1 i2c-2 > [root:/sys/bus/i2c/devices] # modprobe ee1004 > [root:/sys/bus/i2c/devices] # > [root:/sys/bus/i2c/devices] # > [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: -- -- -- -- -- -- -- -- 18 -- 1a -- -- -- -- -- > 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 30: 30 31 -- -- 34 35 -- -- -- -- -- -- -- -- -- -- > 40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- -- > 50: 50 -- 52 -- -- -- -- -- -- -- -- -- -- -- -- -- > 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > 70: -- -- -- -- -- -- -- -- > [root:/sys/bus/i2c/devices] # > [root:/sys/bus/i2c/devices] # modprobe ee1004 > [root:/sys/bus/i2c/devices] # Remember that the ee1004 driver does not autodetect devices and you need to instantiate them explicitly: # echo ee1004 0x50 > /sys/bus/i2c/devices/i2c-2/new_device # echo ee1004 0x52 > /sys/bus/i2c/devices/i2c-2/new_device But anyway, it seems you have done that at some point (otherwise decode-dimms.new would not possibly mention /sys/bus/i2c/drivers/ee1004/2-0050/eeprom). This is really hinting at a problem with the Z370 chipset, or this mainboard specifically. But I did not find anything relevant in the errata list published by Intel for this chipset. Now I just remembered that my wife's system is based on an Intel Z370 chipset. So I tested the ee1004 driver again on it, and it works just fine. It's an Asrock motherboard with Corsair CMK16GX4M2A2400C16 memory in it. One key difference, maybe, is that the SPD protection bit is NOT set. I'm out of idea at this point. Either there is something messing with I2C address 0x36 on the SMBus on your Asus motherboard, or there is a bug in the implementation of the SPD protection on the Z370. Jarkko, can you check with your engineering team if this has been tested or if this is a known issue? All I can suggest is waiting for more reports from other users and see if there is a pattern. -- Jean Delvare SUSE L3 Support
