You are not logged in.
Hey! I upgraded my kernel two days ago from 4.10.13-1 to 4.11.2-1
[2017-05-23 08:13] [ALPM] upgraded linux (4.10.13-1 -> 4.11.2-1)
Since the upgrade, my touchpad has lost it's clickpad functionality (mouse move works fine, but clicking does nothing, doesn't even appear as an event in libinput-debug-events). I've verified that the kernel upgrade was to blame---booting the linux-lts kernel works perfectly.
My laptop is the Dell Inspiron 3148.
Booted into the LTS kernel, the touchpad was listed under some kind of odd codename, but it worked perfectly:
4.9.29-1-LTS $ evemu-describe /dev/input/event13
# Input device name: "DLL068E:00 06CB:2985"
# Properties:
# Property type 0 (INPUT_PROP_POINTER)
# Property type 2 (INPUT_PROP_BUTTONPAD)
With the latest kernel, the device is recognized with its synaptics name, but now the buttonpad functionality isn't even listed:
4.11.2-1-ARCH $ evemu-describe /dev/input/event13
# Input device name: "Synaptics s3203"
# Properties:
# Property type 0 (INPUT_PROP_POINTER)
As I've hunted around on the web, specifically /r/archlinux, I found some bits and pieces about a flag being patched in to address a similar problem with the HP Stream 11:
$ cat /lib/udev/hwdb.d/90-libinput-model-quirks.hwdb | grep -i stream
# HP Stream 11
libinput:name:SYN1EDE:00 06CB:7442:dmi:*svnHewlett-Packard:pnHPStreamNotebookPC11*
LIBINPUT_MODEL_HP_STREAM11_TOUCHPAD=1
I fiddled around with the udev config, adding the same flag for my clickpad model, but no luck. That flag feels like a bit of a hack anyway, so I'm not sure if it's even the right way to go about things.
So, bottom line, my touchpad is now identified with a "Synaptics" model name, but is no longer recognized as having any buttonpad functionality.
Is anyone familiar with what's changed between 4.10.13-1 and 4.11.2-1 that would have affected my touchpad?
Last edited by robbiewxyz (2017-05-26 04:14:00)
Offline
Can confirm that I have a very similar issue. However, it doesn't happen on *every* boot - just some of them, with no rhyme or reason.
My kernel version (according to uname -r) is 4.11.2-1-ARCH. The relevant result of evemu-describe is:
[koz@Emi ~]$ sudo evemu-describe /dev/input/event14
# EVEMU 1.3
# Kernel: 4.11.2-1-ARCH
# DMI: dmi:bvnDellInc.:bvrA06:bd01/12/2015:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0WW73H:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
# Input device name: "Synaptics s3203"
On this boot, the left and right clicks work. I'm on a Dell Inspiron laptop, unsure which model.
Edit: I now have dmesgs for both outcomes. You can download them here.
Last edited by KozRoss (2017-05-29 04:46:56)
Offline
Yup, I've had the very same problem ever since upgrading to 4.11.
In my case on every 5th boot or so the behaviour will switch around completely and suddently the pad will ONLY accept presses of the physical button and stop accepting two-finger-right-clicks. However this happens irregularly (as far as I can determine).
I'm on a dell Dell XPS 13 9333 (Early 2004) (the sputnik-variant) and the problem persists on Kernel 4.11.6-1
Was anyone able to make any progress on the issue?
Offline
https://bugzilla.kernel.org/show_bug.cgi?id=195949 (In case you haven't found this already)
Offline
As a matter of fact, I did not.
Thank you!
Offline
Do you need the modified PKGBUILD (with patch file for the touch pad)?
Offline
Yes, that would be very kind, thank you.
Offline
Blacklisting "i2c-hid" module works for me. DELL Inspiron-3443.
Offline
A bit late now, but:
I keep using 4.11.5 with
PKGBUILD: https://pastebin.com/fRRKhT5h
4.11_s3203_workaround.patch: https://pastebin.com/wUfhLh0q
This should work with the latest 4.11 too tho.
Just checkout the linux package from ABS and adjust the PKGBUILD.
Dont forget to ignore the linux packages in /etc/pacman.conf to avoid a unwanted automatic update:
IgnorePkg = linux linux-headers linux-docs
Last edited by opthomasprime (2017-07-11 14:25:25)
Offline