On Thu, Apr 11, 2019 at 8:12 PM Jean Delvare <jdelvare@xxxxxxx> wrote: > > On Thu, 11 Apr 2019 19:40:55 +0100, Dreamcat4 wrote: > > Hmm. Well! I have no reasonable explanation for this: But it seems > > these commands worked now: > > > > [root:/sys/devices/pci0000:00/0000:00:1f.4/i2c-2] # echo ee1004 0x50 > > > /sys/bus/i2c/devices/i2c-2/new_device > > [root:/sys/devices/pci0000:00/0000:00:1f.4/i2c-2] # echo ee1004 0x52 > > > /sys/bus/i2c/devices/i2c-2/new_device > > [root:/sys/devices/pci0000:00/0000:00:1f.4/i2c-2] # > > > > # dmesg -w > > [ 6856.828823] ee1004 2-0050: Currently selected page: 1 > > [ 6856.828825] ee1004 2-0050: 512 byte EE1004-compliant SPD EEPROM, read-only > > [ 6856.828835] i2c i2c-2: new_device: Instantiated device ee1004 at 0x50 > > [ 6870.013347] ee1004 2-0052: Currently selected page: 1 > > [ 6870.013349] ee1004 2-0052: 512 byte EE1004-compliant SPD EEPROM, read-only > > [ 6870.013364] i2c i2c-2: new_device: Instantiated device ee1004 at 0x52 > > BTW, whenever you run these commands, please double check (with > i2cdetect -l) that i2c-2 corresponds to the i2c-i801 SMBus. Numbering of > i2c buses can change depending on which drivers are loaded and in which > order. Yeah there are no other devices, except for the 2 nvidia ones of my GPU. Checked it... was not that. > > > However still getting the same next error message: > > > > [id:/sys/bus/i2c/devices/i2c-2] $ sudo decode-dimms > > No EEPROM found, try loading the eeprom or at24 module > > > > Perhaps my perl script 'decode-dimms' is not the newest / fully up to > > date? My official ubuntu version is: > > > > [id:/sys/bus/i2c/devices/i2c-2] $ apt search i2c-tools > > Sorting... Done > > Full Text Search... Done > > i2c-tools/cosmic,now 4.0-2build1 amd64 [installed] > > heterogeneous set of I2C tools for Linux > > > > Tried finding and downloading a newer version of the script, git it from here: > > > > https://kernel.googlesource.com/pub/scm/utils/i2c-tools/i2c-tools/+/refs/heads/master/eeprom/decode-dimms > > Official location is: > > https://git.kernel.org/pub/scm/utils/i2c-tools/i2c-tools.git/tree/eeprom/decode-dimms > [root:~] # ./decode-dimms.new Cannot read /sys/bus/i2c/drivers/ee1004/2-0050/eeprom at ./decode-dimms.new line 2358. different line number > I don't know why google folks think it's a good idea to duplicate all of > kernel.org. Anyway it should be the same file. Hopefully. > > > Unfortunately there is a different error message now: > > > > [root:~] # ./decode-dimms.new > > Cannot read /sys/bus/i2c/drivers/ee1004/2-0050/eeprom at > > ./decode-dimms.new line 2028. > > > > Not sure what I am supposed to do next > > Not sure either. I've not seen that specific error before. Once again > you should check the last few lines of the kernel log buffer for extra > information. Also check the file permissions of > /sys/bus/i2c/drivers/ee1004/2-0050/eeprom > and see what happens if you read from it yourself: > > # cat /sys/bus/i2c/drivers/ee1004/2-0050/eeprom > /dev/null > Ah-ha! brief error message with that last commands [root:/sys/bus/i2c/devices] # ls -lsa /sys/bus/i2c/drivers/ee1004/2-0050/eeprom 0 -r--r--r-- 1 root root 512 Apr 11 19:37 /sys/bus/i2c/drivers/ee1004/2-0050/eeprom file exists ^^ but: [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) [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? > -- > Jean Delvare > SUSE L3 Support
