08-28-2017 11:58 PM
But your trackpoint has a different ID and it seems unlikely that a Windows driver would cause that.
Here is a link to the blog post: https://op8867555.github.io/posts/2017-06-11-X1C5-notes.html
His trackpoint works out of the box though. I suspect it might be because the Arch Linux kernel enables RMI enabled by default and Fedora perhaps does not.
08-29-2017 12:03 AM
Thank's! I'll have a look.
I am also using Archlinux and it is working out of the box, but not with RMI4 support!
[ 6.651692] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4760]
[ 6.684539] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..]
[ 6.684553] psmouse serio1: synaptics: Your touchpad (PNP: LEN0072 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 firstname.lastname@example.org.
[ 6.748532] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf002a3/0x940300/0x12e800/0x400000, board id: 3289, fw id: 2492434
[ 6.748549] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0
[ 6.789629] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
[ 6.796601] mousedev: PS/2 mouse device common for all mice
08-29-2017 12:07 AM
Even with the patch though something seems weird. The trackpoint is recognized as a PS/2 Generic Mouse which is still not how we want it to be as we obviously want it to be treated as a trackpoint device.
From what I understand the new Synaptics firmware has changed the way they label a trackpoint. I'll look at the Linux trackpoint driver and see if I can make it properly detect the trackpoint in my X1C5.
08-29-2017 12:38 AM
Quick update, there was a commit to the trackpoint driver 11 days ago which references the X1 Carbon specifically. The commit updates the firmware ID constants and fixes the parsing of those IDs in the driver.
This should in theory work perfectly but it remains to be seen if this commit is based on the ALPS or Elantech trackpoint.
08-30-2017 02:11 AM
is your touchpad still working flawlessly? If yes, this is great news, as it seems to prove that it is (and always has been) a hardware failure.
Then I also don't understand why people here are still trying to fix it via parameters and/or compiling their own kernel solutions instead of flooding the lenovo service centers with repair requests.
08-30-2017 03:54 AM
@schröter, Im not quite sure which post you are replying to but allow me to chime in.
The X1 Carbon comes with two different trackpoint hardware. The Synaptics/ALPS trackpoint seem to work just fine with Linux, especially with the latest patches to the trackpoint driver. However, the Elantech trackpoint does not and depending on what Linux distribution you're running you'll either have a trackpoint that doesnt work at all or you'll have one that works poorly. On top of this there are seemingly cases of hardware defects as well.
The various kernel patches and parameters being tried here is primarily for those of us stuck with an Elantech trackpoint which currently does not have Linux support. You can use the TrackPointDetect.exe tool in Windows to determine which trackpoint you have. Alternatively, the pnp id reported in dmesg will also let you know.