Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Touchpad and touchscreen are not working on my Chromebook Pixel 2015 edition. Version-Release number of selected component (if applicable): 4.0.0-0.rc5.git4.1.fc22.x86_64 How reproducible: Always Actual results: touchpad/touchscreen don't work Expected results: touchpad/touchscreen work Additional info: Same problem on fully updated Fedora 21
Created attachment 1011246 [details] lsmod
Created attachment 1011250 [details] lspci -nvv
[root@bart ~]# lsmod | grep chrome [root@bart ~]# modprobe chromeos_laptop modprobe: ERROR: could not insert 'chromeos_laptop': No such device [root@bart ~]#
Please provide the full output of dmesg from a fresh boot, as well as the output of lsusb.
Also, as far as I know there is no upstream support for either the touchpad or touchscreen on these machines: https://plus.google.com/+OlofJohansson/posts/1yopVMjEhjK so I'm moving this to rawhide. You might be waiting a while.
Josh, fresh from yesterday: https://patchwork.kernel.org/patch/6177151/ Input: atmel_mxt_ts - add support for Google Pixel 2 and maybe the 2/2 (https://patchwork.kernel.org/patch/6177171/)
Created attachment 1014112 [details] dmesg
Created attachment 1014113 [details] lsusb -v [dave@bart ~]$ sudo lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 2232:6001 Silicon Motion Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [dave@bart ~]$ sudo lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 7: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M [dave@bart ~]$
Created attachment 1014114 [details] lsmod
The patches in comment 6 apply clean to 4.0.0-0.rc5.git4.1 however the touchpad/touchscreen are still not working. Are there additional modules that need to be loaded?
Update. After some help from upstream, I was missing 2 commits to actually support the touchpad. So here is the complete list: https://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/commit/?h=next&id=b23157dc74272ac8ebffd1a566e3e822dbc3e65f (already in Linus' tree) https://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/commit/?h=next&id=b6d2d3289f84e9c7449dff04fb959e29207acd80 (already in Linus' tree) https://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/commit/?h=next&id=4f8d808889d05807f494f82f8cfaa6c113c2f761 (only in the input maintainer's tree) Note that the touchpad suffers from a hovering problem where libinput thinks that hovering fingers are touching the touchpad while they are 1 cm above the sensor. The kernel seems correct (it sends the hovering information), but libinput ignores it. I'll try to figure out what needs to be done today hopefully.
BTW, I tested yesterday night this series on top of the 4.0 f22 kernel. The scratch-build is here if you want to dive a try by yourself :) https://koji.fedoraproject.org/koji/taskinfo?taskID=9491712
I've added the third patch to 4.1.0-0.rc0.git7.1.fc23 in rawhide. I'll backport all three to Fedora 22 shortly.
OK, all three added in the F22 git branch. Will be in the next 4.0 build we do there.
I can confirm the build referenced in comment 12 leads to a working touchscreen/touchpad. The hovering issue mentioned in comment 11 is pretty bad. I'm seeing it from even further than 1cm.
(In reply to Dave Maley from comment #15) > The hovering issue mentioned in comment 11 is pretty > bad. I'm seeing it from even further than 1cm. Yeah, I know. The good thing is that the kernel is fine. All we need to do is fixing libinput. Here is an WIP of the libinput work: http://koji.fedoraproject.org/koji/taskinfo?taskID=9499333 It will only work for the pixel, but it makes it so much better that I need to share it. Having this upstream and in Fedora will take a little bit more time (hopefully by the end of next week if everything works out).
The libinput build from comment 16 makes it completely usable. Many thanks!
kernel-4.0.1-300.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/kernel-4.0.1-300.fc22
(In reply to Benjamin Tissoires from comment #16) > Having this upstream and in Fedora will take a little bit more time (hopefully > by the end of next week if everything works out). @btissoir - Was curious if there were any updated builds I could play with. Thanks again!
Package kernel-4.0.1-300.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-4.0.1-300.fc22' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7371/kernel-4.0.1-300.fc22 then log in and leave karma (feedback).
(In reply to Dave Maley from comment #19) > @btissoir - Was curious if there were any updated builds I could play with. > Thanks again! I just sent yesterday a new version of the patch to the libinput (wayland) mailing list: http://lists.freedesktop.org/archives/wayland-devel/2015-April/021707.html There is not much differences with the build I posted: mostly tests and a few corner cases raised by the tests (nothing to worry about I guess). So let just wait and see if and when it gets accepted.
kernel-4.0.1-300.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.