On 7 February 2018 at 15:43, Damjan Georgievski <gdamjan@xxxxxxxxx> wrote: > On 5 February 2018 at 12:56, Damjan Georgievski <gdamjan@xxxxxxxxx> wrote: >>>> >>> Second issues is, trackpoint is reported as "ImPS/2 Generic Wheel >>>> >>> Mouse". Middle button scrolling is not enabled by default. >>>> >> >>>> >> I think this will be fixed by: >>>> >> >>>> >> https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/patch/?id=ec667683c532c93fb41e100e5d61a518971060e2 >>>> >> >>>> > >>>> > Interesting, with this patch, the trackpoint appeared sooner, but >>>> > still late (at the 44 second mark): >>>> >>>> but that seems sporadic. on second boot, it didn't show up until I >>>> reloaded the psmouse module >>>> >>>> any ideas how to debug this issue further? possibly before the change >>>> goes upstream. >>> >>> Damjan, >>> >>> Since my other patches seem to have fixed the trackpoint detection >>> issue, mind giving your "tested-by" to this patch so I can get it in? >> >> let me just run some more tests and I'll get back to you soon. >> >> I'm getting some weird clicks on the trackpad, I want to compare with >> vanilla kernel. >> >> Dimitry, what's best for testing, 4.15.1 + your patches or should I use 4.16rc1? > > The only difference I've noticed is these event that seems to be > repeated/stuck (BTN_LEFT 19.60)?: > $ sudo libinput debug-events --device /dev/input/event16 > -event16 DEVICE_ADDED Synaptics TM3289-002 seat0 > default group1 cap:pg size 102x56mm tap(dl off) left scroll-nat > scroll-2fg-edge click-buttonareas-clickfinger dwt-on > … > event16 POINTER_BUTTON +19.56s BTN_LEFT (272) pressed, seat count: 1 > event16 POINTER_BUTTON +19.58s BTN_LEFT (272) released, seat count: 0 > event16 POINTER_BUTTON +19.60s BTN_LEFT (272) pressed, seat count: 1 > event16 POINTER_BUTTON +19.66s BTN_LEFT (272) released, seat count: 0 > event16 POINTER_BUTTON +20.47s BTN_MIDDLE (274) pressed, seat count: 1 > event16 POINTER_BUTTON +19.60s BTN_LEFT (272) pressed, seat count: 1 > event16 POINTER_BUTTON +20.54s BTN_MIDDLE (274) released, seat count: 0 > event16 POINTER_BUTTON +20.57s BTN_MIDDLE (274) pressed, seat count: 1 > event16 POINTER_BUTTON +19.60s BTN_LEFT (272) pressed, seat count: 1 > event16 POINTER_BUTTON +20.57s BTN_MIDDLE (274) released, seat count: 0 > event16 POINTER_BUTTON +21.34s BTN_MIDDLE (274) pressed, seat count: 1 > event16 POINTER_BUTTON +19.60s BTN_LEFT (272) pressed, seat count: 1 > event16 POINTER_BUTTON +21.43s BTN_MIDDLE (274) released, seat count: 0 > event16 POINTER_BUTTON +21.94s BTN_MIDDLE (274) pressed, seat count: 1 > event16 POINTER_BUTTON +19.60s BTN_LEFT (272) pressed, seat count: 1 > event16 POINTER_BUTTON +22.02s BTN_MIDDLE (274) released, seat count: 0 now on kernel 4.16.0-rc5+ with libinput 1.10.3-1 I don't get this weird behaviour. maybe now is the time to merge/enable LEN0072 5th gen X1 Carbon into smbus_pnp_ids -- damjan -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
