On Mon, Sep 2, 2019 at 4:28 AM Jean Delvare <jdelvare@xxxxxxx> wrote: > If you have DDR4 memory then do NOT modprobe eeprom. The legacy eeprom > driver will stupidly bind to ALL devices in I2C address range > 0x50-0x57, preventing the right driver (ee1004) from claiming these > addresses later. OK, I was confused at first because without eeprom I got no data at all. > Most likely your problems are caused by the eeprom driver. Unload it, > then manually bind the I2C addresses to the ee1004 driver (see > Documentation/i2c/instantiating-devices, Method 4), and I think the > warnings will be gone. I still want to improve the script to properly > report the problem. I didn't realize I needed to bind them manually. I couldn't find this Documentation on my Linux Mint install, but read it from here https://www.kernel.org/doc/Documentation/i2c/instantiating-devices So I ended up running: $ sudo su # echo ee1004 0x50 > /sys/bus/i2c/devices/i2c-1/new_device # echo ee1004 0x51 > /sys/bus/i2c/devices/i2c-1/new_device # echo ee1004 0x52 > /sys/bus/i2c/devices/i2c-1/new_device # echo ee1004 0x53 > /sys/bus/i2c/devices/i2c-1/new_device [Ctrl-D] For some reason which I still don't understand, I couldn't just run each command directly with sudo: $ sudo echo eeprom 0x50 > /sys/bus/i2c/devices/i2c-1/new_device bash: /sys/bus/i2c/devices/i2c-1/new_device: Permission denied With those properly setup, I was able to run decode-dimms and it showed that my 2 kits of (2x8GB) are composed of different memory types, (Samsing and Micron) despite being the same kit model #'s. Really frustrating. Anyways, I guess that's the main information I was after, so mystery solved! -Hans
