Dear Wolfram,
Thank you for your prompt reply.
Am 27.02.23 um 20:27 schrieb Wolfram Sang:
What can a user do about this? It looks like the I2C addresses need to be
added to `dell_lis3lv02d_devices[]` in `drivers/i2c/busses/i2c-i801.c`.
Complain to Dell about the missing address ;)
I will. (As “Laptop system certified with Ubuntu“ [1], I was hoping that
Canonical would have solved that with Dell already.)
Until then:
[ 20.631866] i801_smbus 0000:00:1f.4: SPD Write Disable is set
# cd /sys/bus/pci/drivers/i801_smbus/0000\:00\:1f.4
# ls -d i2c-?
The last digit of the printout is the bus number. Then:
# modprobe i2c-dev
# i2cdetect <bus_number>
And post the output here.
$ cd /sys/bus/pci/drivers/i801_smbus/0000:00:1f.4
$ ls -d i2c-?
i2c-6
$ sudo i2cdetect 6
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-6.
I will probe address range 0x08-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: -- -- -- -- -- -- -- -- -- 29 -- -- -- -- -- --
30: 30 -- -- -- -- 35 UU UU -- -- -- -- -- -- -- --
40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --
50: UU -- 52 -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
If you are brave and see that the address 0x1d or 0x29 are printed in
your output, you could try adding an entry to the array you already
mentioned above with the address you found. It may be safer to do
some sanity checking before, though.
So, 29 shows up in the dump. Let’s see if I am going to find the time to
build a Linux kernel. (I couldn’t find a module parameter to force
loading at a specific address.)
Kind regards,
Paul
[1]: https://ubuntu.com/certified/201902-26859
