Hans, from the mainline the last semi working is the rc7 (4.14.0-041400rc7 ... http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7/)
We have other kernel branches and I tried the drm-intel-next thinking that something labelled intel has more compatibility. I was right, indeed the touchpad was partially working (no buttons). Here it is the last working one: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm- intel-next/2017-12-03/ After this, touchpad is not working anymore. I am a noob but a think that we have 2 ways to debug the problem: 1) see what changed after the drm-intel-next 2017-12-03 kernel... 2) build this 2017-12-03 kernel (or the rc7) with your buttons patches... Even if my PC was more powerful than it is, I don't think that I am skilled enough to do these things... :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
