Hi, Norbert. Thanks for your report. I'm sorry to say that, but from my experience, you're lucky if your synaptics–rmi4 problem gets fixed; i.e. usually it won't be fixed. But anyway if you feel like, why don't you try it again when new kernels are released? About a half year ago, another user reported that for "LEN2014 PNP0f13", RMI4 messed sleep / resume, but otherwise it worked: https://marc.info/?l=linux-input&m=150302854417266&w=2 https://marc.info/?l=linux-input&m=150306118525076&w=2 I'm not a kernel developer, but has been watching this issue. Best regards, Teika From: Norbert Preining <norbert@xxxxxxxxxxxxx> Subject: Synaptics touchpad and RMI hangs Date: Mon, 13 Aug 2018 23:45:29 +0900 > Debian/sid > kernel 4.18.0 > Lenovo X260 > > I found in the journal log the following statement: > > kernel: psmouse serio1: synaptics: queried max coordinates: x [..5712], y [..4780] > kernel: psmouse serio1: synaptics: queried min coordinates: x [1232..], y [1074..] > kernel: psmouse serio1: synaptics: Your touchpad (PNP: LEN2014 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-input@xxxxxxxxxxxxxxx. > kernel: random: fast init done > kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf002a3/0x943300/0x12e800/0x10000, board id: 3075, fw id: 2560 > kernel: psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 > > I have i2c-hid and hid-rmi compiled as modules. > > I tried to set the > psmouse.synaptics_intertouch=1 > on the kernel cmd line, but that resulted in the touchpad being > completely unresponsive, and lots of error messages about > not being able to read or so - somehow the error messages weren't > captured during reboot. > > Other error message I see in kern.log are > rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: TM3075-002, fw id: 1741313 > rmi4_f11: probe of rmi4-00.fn11 failed with error -16 > rmi4_physical rmi4-00: Read PDT entry at 0x00d1 failed, code: -16. > rmi4_physical rmi4-00: Function creation failed with code -16. > rmi4_physical: probe of rmi4-00 failed with error -16 > > I am happy to help debug this any further, but I don't know what I > should do. > > Here are some relevant entries in .config: > CONFIG_RMI4_I2C=y > CONFIG_RMI4_SMB=y > CONFIG_RMI4_F03=y > CONFIG_RMI4_F03_SERIO=y > CONFIG_RMI4_2D_SENSOR=y > CONFIG_RMI4_F11=y > CONFIG_RMI4_F12=y > CONFIG_RMI4_F30=y > CONFIG_RMI4_F34=y > CONFIG_RMI4_F55=y > CONFIG_MOUSE_PS2=m > # CONFIG_MOUSE_PS2_ALPS is not set > # CONFIG_MOUSE_PS2_BYD is not set > # CONFIG_MOUSE_PS2_LOGIPS2PP is not set > CONFIG_MOUSE_PS2_SYNAPTICS=y > CONFIG_MOUSE_PS2_SYNAPTICS_SMBUS=y > # CONFIG_MOUSE_PS2_CYPRESS is not set > # CONFIG_MOUSE_PS2_LIFEBOOK is not set > # CONFIG_MOUSE_PS2_TRACKPOINT is not set > # CONFIG_MOUSE_PS2_ELANTECH is not set > # CONFIG_MOUSE_PS2_SENTELIC is not set > # CONFIG_MOUSE_PS2_TOUCHKIT is not set > # CONFIG_MOUSE_PS2_FOCALTECH is not set > CONFIG_MOUSE_PS2_SMBUS=y > > Please let me know what further information I can provide.
