Touchpad stops working after reboot on Apollo Lake

[Giorgio Andronico]

===SRU Justification===
Hantick touchpad stops working after reboot.

[Fix]
Disable runtime power management for the touchpad.

[Test]
User confirmed it fixed the issue.
Some users reported it doesn't work for them, I'll ask them to file new
bugs for different touchpads.

[Regression Potential]
Low. Disable runtime power management doesn't affect devivce's
funtionality. In general desktop usage the graphical session opens the
touchpad HID device so the touchpad never get runtime suspended, so it
won't hurt power in this case.

===Original Bug Report===
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?

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1728244

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Giorgio Andronico (bytecodex2)]

Also, I cannot run apport-collect 1728244 right now, but I posted the log file above.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7

[Giorgio Andronico (bytecodex2)]

Still not fixed. Updated tag.

[iBART (mogio)]

Ubuntu 17.10, jumper 3 pro v4, kernel 4.13.0-16 still affected. After 10 hours, I give up :D

[Kai-Heng Feng (kaihengfeng)]

Can you attach dmesg under v4.14-rc7?

[iBART (mogio)]

4.14.0-041400rc7 touchpad is working, A lot of tourchpad *i2c_hid i2c-SYNA3602* errors, but it is working.

[iBART (mogio)]

p.s. touchpad movement is working, tap for clic is working too but the 2 buttons are not.

[iBART (mogio)]

xinput attached, same kernel 4.14.0-041400rc7

[iBART (mogio)]

4.14.0-041400rc8

touchpad is not working at all.

[iBART (mogio)]

mich@ezbook:~$ dmesg | grep .hid
[ 3.164258] hidraw: raw HID events driver (C) Jiri Kosina
[ 4.305905] usbcore: registered new interface driver usbhid
[ 4.305907] usbhid: USB HID core driver
[ 4.308860] hid-generic 0003:045E:0023.0001: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-0000:00:15.0-2/input0
[ 6.726802] intel-hid INT33D5:00: platform supports 5 button array
[ 6.869535] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator
[ 6.883919] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 6.888901] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713)
[ 6.891849] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 6.898604] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334)
[ 6.901745] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745)
[ 6.906804] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302)
[ 6.909733] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952)
[ 6.918193] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281)
[ 7.524580] hid-multitouch 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00
[ 102.817373] hid-generic 0003:045E:0023.0003: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft Trackball Optical®] on usb-0000:00:15.0-2/input0
[ 1637.590908] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator
[ 1637.597193] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 1637.599518] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713)
[ 1637.600674] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 1637.604096] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334)
[ 1637.605250] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745)
[ 1637.608647] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302)
[ 1637.609845] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952)
[ 1637.614343] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281)
[ 1637.643866] hid-multitouch 0018:0911:5288.0004: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00
mich@ezbook:~$ uname -r
4.14.0-041400rc8-generic

[mogio (mogio-linux-kernel-bugs)]

Created attachment 260549
dmesg | grep .hid

ezbook 3 pro, apollo lake, ubuntu 16.04/17.10, out of the box touchpad doesn't work. With the v4.14-rc7 movement were tracked but not the phisical click of buttons. With the v4.14-rc8 trackpad is dead.

[mogio (mogio-linux-kernel-bugs)]

latests daily has the trackpad not working at all.

4.14-0.999

[iBART (mogio)]

ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
Package: linux (not installed)
Tags: xenial
Uname: Linux 4.14.0-999-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[iBART (mogio)]

apport information

[iBART (mogio)]

apport information

[iBART (mogio)]

apport information

[iBART (mogio)]

^ attachd apport. latests daily has the trackpad not working at all.

4.14-0.999

[Kai-Heng Feng (kaihengfeng)]

Can you attach dmesg with kernel parameter "i2c-hid.dyndbg=+p"?

Thanks.

[iBART (mogio)]

here sir.

[Brad (bbaker6212)]

This problem is not specific to Ubuntu. I get the same problem on the same notebook with Manjaro and Kernel 4.13

[Brad (bbaker6212)]

Antergos 17.09 Gnome works OK. So I know the touchpad is not defective.
With Manjaro 17.05 Xfce it does not work and I get the same error message
"...i2c_hid_get_input: incomplete report..."

[Brad (bbaker6212)]

If this helps, Attached is my dmesg output with boot param i2c-hid.dyndbg=+p on my notebook with Antergos installed and the touchpad working perfectly.

[bradleybaker (bradleybaker-linux-kernel-bugs)]

I have the ezbook 3 Pro (v4). With Manjaro Xfce 17.05 the touchpad does not work at all, but using Antergos 17.09 the touchpad works perfectly.

[bradleybaker (bradleybaker-linux-kernel-bugs)]

(In reply to Brad Baker from comment #2)
> I have the ezbook 3 Pro (v4). With Manjaro Xfce 17.05 the touchpad does not
> work at all, but using Antergos 17.09 the touchpad works perfectly.

Dmesg logs for both non-working and working config's can be found here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244

[Kai-Heng Feng (kaihengfeng)]

> On 12 Nov 2017, at 8:49 AM, Brad <email address hidden> wrote:
>
> Antergos 17.09 Gnome works OK. So I know the touchpad is not defective.
> With Manjaro 17.05 Xfce it does not work and I get the same error message
> "...i2c_hid_get_input: incomplete report…"

What are the Linux kernel versions in Antergos and Manjaro, respectively?

>
> --
> You received this bug notification because you are 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

[Brad (bbaker6212)]

Trying it more. It started working in Manjaro too. Then booting back into windows then back to Manjaro it stopped working again. So don't know what to make of that. If I can get it to fail again, I'll post the dmesg log. Any other info you need?

[Kai-Heng Feng (kaihengfeng)]

> On 12 Nov 2017, at 2:35 PM, Brad <email address hidden> wrote:
>
> Trying it more. It started working in Manjaro too. Then booting back
> into windows then back to Manjaro it stopped working again. So don't
> know what to make of that. If I can get it to fail again, I'll post the
> dmesg log. Any other info you need?

Does cold boot instead of reboot have the same problem?

>
> --
> You received this bug notification because you are 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

[Brad (bbaker6212)]

Always working touchpad >> Antergos kernel: Linux version 4.13.11-1-ARCH
Sometimes not working >> Manjaro kernel : Linux version 4.12.14-1-MANJARO
Attached are the dmesg logs for both.

[iBART (mogio)]

I tried Ubuntu 16.04 with 4.13.11 and it is not working.

[Brad (bbaker6212)]

FYI, the Manjaro dmesg log attached above was from a boot when the touchpad was NOT working.

[Brad (bbaker6212)]

@iBART, is that Ubuntu 16.04 w/4.13.11 with rEFInd? I'm booting through rEFInd installed on my SSD partion, with my Antergos installed on SSD and Manjaro installed on an external USB drive.

[iBART (mogio)]

Yes, without refind it doesn't boot, because of GRUB.

By the way: strange things are appening! back to the semi working 4.14.0-041400rc7 the touchpad is 100% dead; not clics nor movements.

[iBART (mogio)]

No, sorry, my bad. Too many kernels installed.

This is the dmesg (plus the kernel param kaihengfeng requested) of my ubuntu 16.04 installation with the 4.14.0-041400rc7 kernel. It has the trackpad working but not its left/right buttons.

After this kernel mainline release, the touchpad is not working at all.

[mogio (mogio-linux-kernel-bugs)]

Created attachment 260625
partially working touchpad 4.14.0-041400rc7

This is the dmesg of my ubuntu 16.04 installation with the 4.14.0-041400rc7 kernel. It has the trackpad working but not its left/right buttons.

After this kernel mainline release, the touchpad is not working at all.

[Brad (bbaker6212)]

OK so it turns out I lied. It doesn't always work on Antergos either. It seems to happen randomly and how to get it working again is also a mystery. Resetting BIOS default does not restore it, and neither does booting into Windows - where it's not working there either. I unplugged both the power cable and the USB mouse then just kept restarting it until it mysteriously started working again.
Attached is the full dmesg logs for both working (YES) and not (NO). Here the pertinent parts:

// NOT WORKING //
$ grep -i hid EZBook*
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 0.000000] Command line: \\boot\vmlinuz-linux ro root=UUID=db197dac-84a9-48f2-8de2-803e79eb2a95 initrd=boot\initramfs-linux.img i2c-hid.dyndbg=+p
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 0.000000] Kernel command line: \\boot\vmlinuz-linux ro root=UUID=db197dac-84a9-48f2-8de2-803e79eb2a95 initrd=boot\initramfs-linux.img i2c-hid.dyndbg=+p
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 1.796661] hidraw: raw HID events driver (C) Jiri Kosina
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 1.800642] usbcore: registered new interface driver usbhid
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 1.800644] usbhid: USB HID core driver
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 1.802083] hid-generic 0003:275D:0BA6.0001: input,hidraw0: USB HID v1.11 Mouse [USB OPTICAL MOUSE ] on usb-0000:00:15.0-2/input0
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 8.334410] input: Intel HID events as /devices/platform/INT33D5:00/input/input3
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 8.334430] intel-hid INT33D5:00: platform supports 5 button array
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 8.334475] input: Intel HID 5 button array as /devices/platform/INT33D5:00/input/input4
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 8.471540] i2c_hid i2c-SYNA3602:00: Requesting IRQ: 154
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 13.490316] i2c_hid i2c-SYNA3602:00: failed to reset device.
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 14.507051] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34)
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 14.514231] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34)
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 19.676987] i2c_hid i2c-SYNA3602:00: failed to reset device.
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 25.863656] i2c_hid i2c-SYNA3602:00: failed to reset device.
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 26.880415] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34)
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 26.888099] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34)
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 32.050315] i2c_hid i2c-SYNA3602:00: failed to reset device.
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 33.063375] i2c_hid i2c-SYNA3602:00: can't add hid device: -61
EZBook3Pro-touchpad-NO.Antergos.dmesg.txt:[ 33.069267] i2c_hid: probe of i2c-SYNA3602:00 failed with error -61

// WORKING //
EZBook3Pro-touchpad-YES.Antergos.dmesg.txt:[ 0.000000] Command line: \\boot\vmlinuz-linux ro root=UUID=db197dac-84a9-48f2-8de2-803e79eb2a95 initrd=boot\initramfs-l...

[Brad (bbaker6212)]

One or two more people reported the problem here: https://bbs.archlinux.org/viewtopic.php?id=231540

[Brad (bbaker6212)]

Oh nice! There is a recent patch for this problem as about a week ago.
I've only applied a patch once a long time ago. Gotta go relearn how to do it...

https://patchwork.kernel.org/patch/10046575/

[bradleybaker (bradleybaker-linux-kernel-bugs)]

There is a potential patch (quirk) for this. Please test it, if possible:
https://patchwork.kernel.org/patch/10046575/

[IGOR' (i.guliaew)]

Not Working Patch

igor@igor-EZbook:~/Загрузки$ patch -p1 < v2-HID-i2c-hid-Add-no-irq-after-reset-quirk-for-0911-5288-device.patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
|index be2e005c3c51..c81ea3fbaa6b 100644
|--- a/drivers/hid/hid-ids.h
|+++ b/drivers/hid/hid-ids.h
--------------------------
File to patch:

[Kai-Heng Feng (kaihengfeng)]

This kernel includes the patch:
http://people.canonical.com/~khfeng/lp1728244/

[iBART (mogio)]

I compiled from source (4.14.0-041400) adding the patch and the touchpad is not working.
I tried @kaihengfeng kernel (4.13.0-17) and the touchpad is not working.

Got back to the only one semi working kernel (4.14.0-041400rc7). :|

[mogio (mogio-linux-kernel-bugs)]

Ubuntu 16.04, Jumper ezbook 3 pro V4: patch is not working.

Compiled by myself with this patch 4.14.0-041400 and tried a kernel compiled by a more pro user than me (here. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244).

Touchpad is not working. The only semi working kernel is the 4.14.0-041400rc7 on mainline. Yes MOVING, Yes doubletap for clic, No buttons.

[Brad (bbaker6212)]

@mogio when reporting the problem still exists you should supply the dmesg log. That will help to resolve the problem.

[iBART (mogio)]

dmesg > dmesg 4.14 mainline + released patch + i2c debug kernel param.

It is not working.

@bbaker6212 I know... right now the Jumper 3 pro is my main pc. It takes ages to make :)

[mogio (mogio-linux-kernel-bugs)]

Created attachment 260639
dmesg > dmesg_4.14_patch_i2c_debug

attached dmesg 4.14 mainline + released patch + i2c debug kernel param.

[Brad (bbaker6212)]

@mogio, you forgot the kernel param "i2c-hid.dyndbg=+p"

[iBART (mogio)]

here it is.

[Kai-Heng Feng (kaihengfeng)]

Do you use Hantick touchpad?

#define I2C_VENDOR_ID_HANTICK 0x0911
#define I2C_PRODUCT_ID_HANTICK_5288 0x5288

If yours does not match the ID, then additional IDs needs to be added to the quirk table.

[iBART (mogio)]

[ 7.350290] input: SYNA3602:00 0911:5288 Touchpad as /devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0002/input/input18
[ 7.350982] hid-multitouch 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00

This is my touchpad, as far as I'm concerned.

Honestly, even If I am a noob, I don't think this "Hantick thing" is a solution... rc7 recognizes mytouhpad, but button clicks.

Anyway, tell me what you want me to do and I'll do it! :)

[Brad (bbaker6212)]

@mogio, this probably is not important but I wanted to record the difference between the BIOS version in your EZbook and mine. Yours has a slightly new version NHNAUHN05

[ 0.000000] DMI: Jumper EZbook/P313R, BIOS JUMPER10x.P8.WP313R.NHNAUHN02 08/07/2017
[ 0.000000] DMI: Jumper EZbook/P313R, BIOS JUMPER2x.P8.WP313R.NHNAUHN05 09/30/2017
Note: when the problem happens for me, nothing works. When the problem does not happen everything works including the touchpad buttons. I never have a problem of only the buttons not working.

[iBART (mogio)]

@brad try this Kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7/

Is your BIOS setting Default? (I just changed SSD instead of HDD into SATA port settings).

[Brad (bbaker6212)]

Yes, I reloaded default BIOS settings and always use this. Btw, never use BIOS setting OS "linux", it can freeze the screen and keyboard and you will have to disconnect the battery to reset it.
I will try that kernel.

[Brad (bbaker6212)]

@mogio, It is possible your failure could be caused by something different than mine. In your logs there is one message I do not see in either my working/not-working logs...
"i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator"
I don't know what the significance of this message is.
There is another Arch user with this same log message here...
https://bbs.archlinux.org/viewtopic.php?pid=1747409#p1747409

[Jean-Baptiste Sarrodie (jbsarrodie)]

Hi,

For your information I already own a recent Jumper ezbook pro 3 v4 with 09/30/2017 BIOS version.

I have the same issue with Touchpad that is only solved when using kernel v4.14-rc7.

If I can help with some tests let me know.

BTW I also have an issue with resuming from suspend. In short resuming starts but screen stays black and no mater what I do I can't use my laptop and have to force a power off. I don't think it is related but who knows...

Regards

[Kai-Heng Feng (kaihengfeng)]

Interesting. There are no change between v4.14-rc7 and v4.14-rc8 in hid/i2c-hid, i2c and mfd drivers. Also, both -rc7 and -rc8 use the same config file.

Maybe this is related to cold/warm boot?

[iBART (mogio)]

Another interesting fact: I noticed that if i try to move the touchpad (rc7 kernel) as soon as I entered the password to login, it dies. But if I move it after a couple of seconds after the login, I have no problems at all. Once, it freezed my entire pc. Hard reset. Kaput.

I don't know how to debug this.

[iBART (mogio)]

^ maybe it is not a dead touchpad thing. I have forgotten that I disabled it by mouse panel menu. So, apparently, after the login it is enabled for a couple of seconds; after that, I guess, the setting switches it off.

[Brad (bbaker6212)]

what do you mean? you enabled it in the mouse panel and now the problem is gone? It's working now for you?

[Brad (bbaker6212)]

On my machine it's a very difficult problem to reproduce. I've only gotten it to fail once so far with days of use on Antergos 17.9. First step in debugging this is finding how to reproduce it consistently. Anyone know how?

[Brad (bbaker6212)]

From another user with the same August BIOS as mine said that the patched kernel provided by @kaihengfeng fixed the problem for him:
http://people.canonical.com/~khfeng/lp1728244/

https://techtablets.com/forum/topic/how-to-install-antergos-linux-on-the-ezbook-3-pro-v4/#post-74901

"It is 17.10 Ubuntu from the official download site, isorespined (Linuxium), then kernel changed (yesterday did it) from the link above. Ubuntu installed few weeks ago, but had touchpad problem until kernel change....

4.13.0.17 is working (from your link above)!!!! 4.14-rc7 was not ok (maybe patch was not included at all, god knows who compiled the kernel)!!! Since yesterday all boot was normal, touchpad is working, no freezing issue. Maybe sometimes this 100ms waiting time is not enough. This waiting time includes in the patch.

After some debuging this it seems that this touchpad simply never sends
an interrupt after a reset as expected by the i2c hid driver. This commit
adds a quirk for this device, making i2c_hid_command sleep 100ms after
a reset instead of waiting for an irq, fixing i2c-hid failing to bind to
this touchpad.”

Maybe this 100ms is not enough sometimes, this was the reason, why your touchpad not worked once. (Just a tip)"

[Brad (bbaker6212)]

It looks like this fix will be included in Kernel 4.15

Hans de Goede (1):
      HID: i2c-hid: Add no-irq-after-reset quirk for 0911:5288 device

https://lkml.org/lkml/2017/11/15/168
http://lkml.iu.edu/hypermail/linux/kernel/1711.1/05553.html

[Kai-Heng Feng (kaihengfeng)]

So does the kernel in comment #35 work or not?

If not, does increase the msleep() value work for you guys?

[iBART (mogio)]

For me, touchpad is not working at all: no movements, no clicks.

[iBART (mogio)]

So... we have to wait for this 4.15 kernel in mainline. For now, my touchpad does not work. I bought a wireless mouse. I'll use this, until this problem is solved. But I don't think we are gonna solve this :p

[iBART (mogio)]

For disperation, I tried this kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2017-11-18/

And movements are OK. Tap clic is working. Clic buttons are not.

[Brad (bbaker6212)]

@mogio, I agree with you. That patch I don't think is working on the EZBook 3 Pro. Yesterday I had my touchpad freeze a few times and had to reset BIOS defaults to get it working again. And that was running Ubuntu 17.10 with the above patched @khfeng kernel 4.13.0-17.
I managed to get installed the latest pre-release of Manjaro Xfce 17.1 with kernel 4.14, so I'll run that for a while and see if I ever get touchpad freeze. My guess is this problem is bootup timing releated (timeouts) so perhaps it will not happen with Manjaro.

How to install it: https://forum.manjaro.org/t/solved-refind-live-usb-wont-boot-w-manjaro-xfce-17-1-pre2-nor-17-06/34993/15?u=bako62
dmesg log w/Manjaro: https://pastebin.com/WjFZCnzh

[iBART (mogio)]

May I ask you to check if my settings are correct?

I figured out that right and left buttons are working but they simply do nothing.

I noticed with evtest that my touchpad is capable of right and left clicking but if I try, the debug says only BTN_LEFT, on click, and does nothing. So, please: help :) I think the drm-intel-next kernel is working but I need to tune my touchpad...

[iBART (mogio)]

May I ask you to check if my settings are correct?

I figured out that right and left buttons are working but they simply do nothing.

I noticed with evtest that my touchpad is capable of right and left clicking but if I try, the debug says only BTN_LEFT, on click, and does nothing. So, please: help :) I think the drm-intel-next kernel is working but I need to tune my touchpad...

[Panayotes P (panos345)]

I Have the same problems with @mogio.
Touchpad is working with kernel v4.14-rc7 but no buttons.
Tried evtest and it captures BTN_LEFT on *both* button clicks.
Also it freezes after suspend.
My BIOS date is 09/30/2017.

[Panayotes P (panos345)]

when i press down either right or left touchpad button, i get in evtest this repeated:

Event: time 1511778511.423062, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1511778511.423062, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1511778511.423062, -------------- SYN_REPORT ------------
Event: time 1511778511.433104, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1511778511.433104, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1511778511.433104, -------------- SYN_REPORT ------------
Event: time 1511778511.443313, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1511778511.443313, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1511778511.443313, -------------- SYN_REPORT ------------
Event: time 1511778511.453482, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1511778511.453482, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1511778511.453482, -------------- SYN_REPORT ------------

I think it should only be captured once, not repeatedly. Also the code is the same for left and right button which doesnt look good.

[panayotes2 (panayotes2-linux-kernel-bugs)]

(In reply to mogio from comment #6)
> Ubuntu 16.04, Jumper ezbook 3 pro V4: patch is not working.
>
> Compiled by myself with this patch 4.14.0-041400 and tried a kernel compiled
> by a more pro user than me (here.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728244).
>
> Touchpad is not working. The only semi working kernel is the
> 4.14.0-041400rc7 on mainline. Yes MOVING, Yes doubletap for clic, No buttons.

Same here.

[bradleybaker (bradleybaker-linux-kernel-bugs)]

@mogio, I just noticed this in your dmesg log.
"random: fast init done"
If it means you have "fast boot" enabled in your BIOS you should disable that.

[bradleybaker (bradleybaker-linux-kernel-bugs)]

Mogio, see this patch. It looks related to your button click problem perhaps: https://patchwork.kernel.org/patch/10070339/

[iBART (mogio)]

Compiling this http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/

with the last 3 commits by Hans de Goede from this https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/log/?h=for-4.16/hid-quirks-cleanup/multitouch

should save the day.

I am unable to compile right now.

[Brad (bbaker6212)]

Where are there directions on how to compile this?

[Kai-Heng Feng (kaihengfeng)]

Try it here:
http://people.canonical.com/~khfeng/lp1728244-multitouch/

[iBART (mogio)]

Thanks kaihengfeng for the build. Touchpad is not working. No movemens, no clicks.

[Brad (bbaker6212)]

@mogio two of those patches had errors when I applied them to that kernel, probably because the patches are on top of "for-4.16". I don't know, but errors are displayed when I applied the to those sources.

[Kai-Heng Feng (kaihengfeng)]

Do you all have these error messages like @mogio?

[ 7.265701] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 7.276156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713)
[ 7.279098] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 7.284241] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334)

[Brad (bbaker6212)]

Those patches had errors when applying to that kernel version's sources.
This one from yesterday patched without errors:
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/2017-11-30/

[Brad (bbaker6212)]

Yes. "incomplete report" happens often, even when the touchpad is working.

[iBART (mogio)]

drm-intel-nightly is not drm-intel-next

[Brad (bbaker6212)]

@mogio, I'm just reporting that the patches give an error (when I applied them) if you use the two links you provided in your post #64 above. Did you try it? So that makes me wonder what @kaihengfeng used for his latest build and maybe that's why it does not work for you?

[iBART (mogio)]

I am very busy at work, I don't have time to compile with my ezbook, it takes ages. Sorry.

I think the drm-intel-next serie will fix my problem. I'll just sit and wait. An alternative, would be having one physical button working (LFT) and set to it the action of right click while the left click is assured bu tapclic.

[iBART (mogio)]

Latest drm-intel-next 4.15 hasn't the touchpad working.

[mogio (mogio-linux-kernel-bugs)]

4.15 is a big no. Latest drm-intel-next 4.15 hasn't the touch-pad movement working. Rolled back to the 4.14...

[Brad (bbaker6212)]

@mogio did you try kernel 4.14.3-1 ? I have been running Manjaro XFCE with this kernel and have not hit the non-functional touchpad problem for many weeks and dozens of sleep/wake/power cycles.

[bradleybaker (bradleybaker-linux-kernel-bugs)]

@mogio a guy on the TT forum says that 4.15 did not work for him but rolling back to 4.14.3 did. I'm not sure but I think he's using Ubuntu. 4.14.3 has also been working for me without failure (so far). Manjaro just released 4.14.5 so I will be upgrading and testing that out soon.
See: https://techtablets.com/forum/topic/how-to-install-antergos-linux-on-the-ezbook-3-pro-v4/page/3/#post-76087

[iBART (mogio)]

4.13.3 ubuntu's kernel is not working for me. 4.14 drm-intel-next is ok, no touchpad click buttons, but I am using the trackpad movements plus tap clicks.

[Robert Schuettler (rober)]

The only one working for me (JUMPER10x.P8.WP313P.NhNAUHL02) at least a bit is 4.14.0-997-generic #201711172100 for the moment. Touchpad moves the mouse cursor -- but neither tap nor click work.

[Brad (bbaker6212)]

does your touchpad look like mine?...

"cat /proc/bus/input/devices" ...

I: Bus=0018 Vendor=0911 Product=5288 Version=0100
N: Name="SYNA3602:00 0911:5288 Touchpad"
P: Phys=i2c-SYNA3602:00
S: Sysfs=/devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-1/i2c-SYNA3602:00/0018:0911:5288.0001/input/input18
U: Uniq=
H: Handlers=event15 mouse0
B: PROP=5
B: EV=b
B: KEY=e420 10000 0 0 0 0
B: ABS=260800000000003

[Brad (bbaker6212)]

A couple other ones from the TT forum. Slight differences with different things working/not-working (like TP OK but buttons not). I wonder if these property differences make any difference?...

(this one TP works, buttons no, on Ubuntu, 14.4 drm-intel-next)
I: Bus=0018 Vendor=0911 Product=5288 Version=0100
N: Name="SYNA3602:00 0911:5288 Touchpad"
P: Phys=i2c-SYNA3602:00
S: Sysfs=/devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0005/input/input20
U: Uniq=
H: Handlers=mouse1 event17
B: PROP=5
B: EV=b
B: KEY=e420 30000 0 0 0 0
B: ABS=260800000000003

(this one same as mine seems to work OK on 4.14.3)
I: Bus=0018 Vendor=0911 Product=5288 Version=0100
N: Name=”SYNA3602:00 0911:5288 Touchpad”
P: Phys=i2c-SYNA3602:00
S: Sysfs=/devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15
U: Uniq=
H: Handlers=mouse0 event14
B: PROP=5
B: EV=b
B: KEY=e420 10000 0 0 0 0
B: ABS=260800000000003

[Hans de Goede (j-w-r-degoede)]

Hi All,

Clicking the 0911:5288 clickpad not sending button events is a known and fixed issue, this is fixed by the following 3 commits:

"HID: multitouch: Properly deal with Win8 PTP reports with 0 touches"
"HID: multitouch: Only look at non touch fields in first packet of a frame"
"HID: multitouch: Combine all left-button events in a frame"

From this branch:
https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git/log/?h=for-4.16/hid-quirks-cleanup/multitouch

Which will be merged into the 4.16 kernel. In the mean time these should probably be added to the Ubuntu kernels.

Regards,

Hans

[iBART (mogio)]

Thanks Hans, I have tried to patch with your patches my kernel but it didn't work. A better tech guy - a canonical guy - compiled himself for me and it didn't work neither. I'll wait for 4.16 but at this point - because 4.15 has a regression, indeed touchpad movement doesn't work anymore in drm-intel-next mainline branch - I don't think it is going to work :D

[Robert Schuettler (rober)]

@Brad looks like this:

I: Bus=0018 Vendor=0911 Product=5288 Version=0100
N: Name="SYNA3602:00 0911:5288 Touchpad"
P: Phys=i2c-SYNA3602:00
S: Sysfs=/devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15
U: Uniq=
H: Handlers=mouse0 event14
B: PROP=5
B: EV=b
B: KEY=e420 30000 0 0 0 0
B: ABS=260800000000003

Anyone up to producing a(nother) kernel with Hans' patches (.13 .14 .15 - whatever) to try if that solves the problem?

[Brad (bbaker6212)]

Guys, a full list of system and touchpad info that *might* be of assistance in tracking this problem since it seems to manifest differently on different machines:

[brad@EZB3P ~]$ uname -a //of course ;-)

[brad@EZB3P ~]$ dmesg | grep JUMPER
Jumper EZbook/P313R, BIOS JUMPER10x.P8.WP313R.NHNAUHN02 08/07/2017

[brad@EZB3P ~]$ sudo libinput list-devices
Device: SYNA3602:00 0911:5288 Touchpad
Kernel: /dev/input/event15
Group: 6
Seat: seat0, default
Size: 120x71mm
Capabilities: pointer gesture
Tap-to-click: disabled
Tap-and-drag: enabled
Tap drag lock: disabled
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: *two-finger edge
Click methods: *button-areas clickfinger
Disable-w-typing: enabled
Accel profiles: none
Rotation: n/a

[brad@EZB3P ~]$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ SYNA3602:00 0911:5288 Touchpad id=9 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Video Bus id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ USB 2.0 Camera: USB 2.0 Camera id=8 [slave keyboard (3)]
↳ Intel HID events id=10 [slave keyboard (3)]
↳ Intel HID 5 button array id=11 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=12 [slave keyboard (3)]

[brad@EZB3P ~]$ xinput list 9
SYNA3602:00 0911:5288 Touchpad id=9 [slave pointer (2)]
Reporting 7 classes:
Class originated from: 9. Type: XIButtonClass
Buttons supported: 7
Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
Button state:
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 9. Type: XIValuatorClass
Detail for Valuator 3:
Label: Rel Vert Scroll
Range: -1.000000 - -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 9. Type: XIScrollClass
Scroll info for Valuator 2
type: 2 (horizontal)
increment: 15.000000
flags: 0x0
Class originated from: 9. Type: XIScrollClass
Scroll info for Valuator 3
type: 1 (vertical)
increment: 15.000000
flags: 0x0

[brad@EZB3P ~]$ xinput list-props "SYNA3602:00 0911:5288 Touchpad"
Device 'SYNA3602:00 0911:5288 Touchpad':
Device Enabled (141): 1
Coordinate Transformation Matrix (143): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Tapping Enabled (276): 1
libinput Tapping Enabled Default (277): 0
libinput Tapping Drag Enabled (278): 1
libinput Tapping Drag Enabled Default (279): 1
libinput Tapping Drag Lock Enabled (280): 0
libinput Tapping Drag Lock Enabled Default (281): 0
libinput Tapping Button Mapping Enabled (282): 1, 0
libinput Tapping Button Mappin...

[iBART (mogio)]

mich@ezbook:~$ uname -a
Linux ezbook 4.14.0-997-generic #201712022100 SMP Sun Dec 3 02:02:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

mich@ezbook:~$ dmesg | grep JUMPER
[ 0.000000] DMI: Jumper EZbook/P313R, BIOS JUMPER2x.P8.WP313R.NHNAUHN05 09/30/2017

mich@ezbook:~$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ MI Dongle MI Wireless Mouse id=9 [slave pointer (2)]
⎜ ↳ MI Dongle MI Wireless Mouse id=10 [slave pointer (2)]
⎜ ↳ SYNA3602:00 0911:5288 Touchpad id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Video Bus id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ MI Dongle MI Wireless Mouse id=8 [slave keyboard (3)]
    ↳ USB 2.0 Camera: USB 2.0 Camera id=11 [slave keyboard (3)]
    ↳ Intel HID 5 button array id=13 [slave keyboard (3)]
    ↳ Intel HID events id=14 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
    ↳ MI Dongle MI Wireless Mouse id=16 [slave keyboard (3)]
    ↳ MI Dongle MI Wireless Mouse id=17 [slave keyboard (3)]

mich@ezbook:~$ xinput list 12
SYNA3602:00 0911:5288 Touchpad id=12 [slave pointer (2)]
 Reporting 7 classes:
  Class originated from: 12. Type: XIButtonClass
  Buttons supported: 12
  Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" None None None None None
  Button state:
  Class originated from: 12. Type: XIValuatorClass
  Detail for Valuator 0:
    Label: Rel X
    Range: 0.000000 - 1310.000000
    Resolution: 14000 units/m
    Mode: relative
  Class originated from: 12. Type: XIValuatorClass
  Detail for Valuator 1:
    Label: Rel Y
    Range: 0.000000 - 859.000000
    Resolution: 14000 units/m
    Mode: relative
  Class originated from: 12. Type: XIValuatorClass
  Detail for Valuator 2:
    Label: Rel Horiz Scroll
    Range: 0.000000 - -1.000000
    Resolution: 0 units/m
    Mode: relative
  Class originated from: 12. Type: XIValuatorClass
  Detail for Valuator 3:
    Label: Rel Vert Scroll
    Range: 0.000000 - -1.000000
    Resolution: 0 units/m
    Mode: relative
  Class originated from: 12. Type: XIScrollClass
  Scroll info for Valuator 2
    type: 2 (horizontal)
    increment: 31.000000
    flags: 0x0
  Class originated from: 12. Type: XIScrollClass
  Scroll info for Valuator 3
    type: 1 (vertical)
    increment: 31.000000
    flags: 0x0

mich@ezbook:~$ xinput list-props "SYNA3602:00 0911:5288 Touchpad"
Device 'SYNA3602:00 0911:5288 Touchpad':
 Device Enabled (141): 1
 Coordinate Transformation Matrix (143): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
 Device Accel Profile (271): 1
 Device Accel Constant Deceleration (272): 2.500000...

[Daniel Ruoso (daniel-ruoso)]

I think I just had a huge breakthrough, after installing a kernel 4.14.0 with all of the patches referenced here, suddenly the touchpad was working. I went ahead and rebooted and sure enough the touchpad was not working again. Then I thought, what if I suspend the computer? And sure enough, the touchpad magically starts working after the computer wakes up. I think there's some device initialization code that gets called on wake-up that is missed on boot.

[iBART (mogio)]

What distro are you using? Are buttons left-right working?

[Ryan Burke (theyield)]

I just thought I would add that I too am affect by this on my system:

SYNA3602 device on a YEPO 737A Laptop - Linux Mint 18.3 Cinnamon respun, as OP describes. The touchpad doesn't work live, and has never worked after install.

I'm currently on 4.15 RC6 which was respun into the install ISO via the -u argument.

Touchpad works flawlessly in windows 10 of course.

[Brad (bbaker6212)]

@theyield/Ryan, does the touchpad function after you perform suspend+wake with either kernel 4.14.x or 4.15 as reported in post #86 above?
What about after you perform these two terminal commands?..
sudo modprobe -rv i2c_hid
sudo modprobe -v i2c_hid

[Brad (bbaker6212)]

Ryan, also provide the info @mogio provided in post #85 so we can see your configuration.

[Ryan Burke (theyield)]

@bbaker6212/Brad, weirdly enough it does work after a suspend/wake but will cease working after any sort of interaction with the touchpad settings including on/off.

modprobe commands have no effect.

Requested Info:

theyield@Keyloggertop ~ $ uname -a
Linux Keyloggertop 4.15.0-041500rc6-generic #201712312330 SMP Sun Dec 31 23:31:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
theyield@Keyloggertop ~ $ dmesg | grep YEPO
[ 0.000000] DMI: LIVEFAN LIVEFAN/P313R, BIOS YEPOM10x.8.WP313R.NHNAUHL01 10/09/2017
theyield@Keyloggertop ~ $ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PixArt Dell MS116 USB Optical Mouse id=8 [slave pointer (2)]
⎜ ↳ SYNA3602:00 0911:5288 Touchpad id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Video Bus id=6 [slave keyboard (3)]
    ↳ Power Button id=7 [slave keyboard (3)]
    ↳ USB2.0 UVC PC Camera: USB2.0 UV id=9 [slave keyboard (3)]
    ↳ Intel HID events id=11 [slave keyboard (3)]
    ↳ Intel HID 5 button array id=12 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=13 [slave keyboard (3)]
theyield@Keyloggertop ~ $ xinput list 10
SYNA3602:00 0911:5288 Touchpad id=10 [slave pointer (2)]
 Reporting 7 classes:
  Class originated from: 10. Type: XIButtonClass
  Buttons supported: 7
  Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"
  Button state:
  Class originated from: 10. Type: XIValuatorClass
  Detail for Valuator 0:
    Label: Rel X
    Range: -1.000000 - -1.000000
    Resolution: 0 units/m
    Mode: relative
  Class originated from: 10. Type: XIValuatorClass
  Detail for Valuator 1:
    Label: Rel Y
    Range: -1.000000 - -1.000000
    Resolution: 0 units/m
    Mode: relative
  Class originated from: 10. Type: XIValuatorClass
  Detail for Valuator 2:
    Label: Rel Horiz Scroll
    Range: -1.000000 - -1.000000
    Resolution: 0 units/m
    Mode: relative
  Class originated from: 10. Type: XIValuatorClass
  Detail for Valuator 3:
    Label: Rel Vert Scroll
    Range: -1.000000 - -1.000000
    Resolution: 0 units/m
    Mode: relative
  Class originated from: 10. Type: XIScrollClass
  Scroll info for Valuator 2
    type: 2 (horizontal)
    increment: 15.000000
    flags: 0x0
  Class originated from: 10. Type: XIScrollClass
  Scroll info for Valuator 3
    type: 1 (vertical)
    increment: 15.000000
    flags: 0x0

theyield@Keyloggertop ~ $ xinput list-props "SYNA3602:00 0911:5288 Touchpad"
Device 'SYNA3602:00 0911:5288 Touchpad':
 Device Enabled (142): 1
 Coordinate Transformation Matrix (144): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
 libinput Tapping Enabled (293): 1
 libinput Tapping Enabled Default (294): 0
 libinput Tapping Drag Enabled (295): 1
 libinput Tappin...

[Wolfram Gürlich (w-guerlich)]

Just a wild guess. Could this issue be related to the one mentioned here?

https://github.com/vlasenko/hid-asus-dkms/issues/24

It deals with a timing issue between the POWER ON and the RESET command to the touchpad which keeps the touchpad from initializing correctly. Apparently the generic Windows driver adds a much larger pause there.

[Daniel Ruoso (daniel-ruoso)]

I'm using Debian Stretch, but I took the source package from the unstable kernel, applied all of the patches referenced by two links in this thread (one to a single github commit, and the other to the branch merged to the Head kernel) and I got it fully working, including multi-touch gestures and button clicks (I'm not on the box right now, but I'm pretty sure both left and right click were working, but let button for sure is). The only remaining issue is the initialization problem.

[Daniel Ruoso (daniel-ruoso)]

@w-guerlich I think that sounds like an interesting bet. I'm not sure I'll be able to test it today, but if someone does, please report back.

[Jean-Baptiste Sarrodie (jbsarrodie)]

I've just received another laptop so I now own 2 of them. The new one is more recent and... everything works out of the box (trackpad, buttons, suspend...).

The BIOS is more recent and is reported as:
DMI: Jumper EZbook/P313P, BIOS JUMPER10x.P8.WP313P.NhNAUHL02 11/06/2017

While my older Jumper is:
DMI: Jumper EZbook/P313R, BIOS JUMPER2x.P8.WP313R.NHNAUHN05 09/30/2017

We can notice that BIOS is more recent and has almost no options available (basically only Security and Boot tabs), but also that model is P313P instead of P313R. I compared output of lspci/lsusb/lshw/dmidecode and there seems to be no real differences on reported hardware except maybe the value of "Interleaved Data Depth" reported as 2 on the old and 4 on the new. You'll find reports attached.

Last I opened both laptops to check hardware and PCB are different.

This now really seems to me like a BIOS issue on the 09/30/2017 version. Did some of you try to contact Jumper by email ? (I did using the only email I found: <email address hidden>, but with no answer yet)

[Jean-Baptiste Sarrodie (jbsarrodie)]

With missing attachements

[Brad (bbaker6212)]

@jean-baptiste-f, that's good to know. I thought it was highly likely a BIOS issue. Jumper really needs to have better support, and they need to supply a BIOS flashing tool so people can address problems like this. They seem to have zero support. Not even a users' discussion forum.

[iBART (mogio)]

Brad, they cannot support BIOS flashing because they are changing pc components every batch.

Jumper sells for very few something that we know is "as it".

The touchpad is working, I can use it at 100% on Windows 10, the issue should be fixed by software BUT we need a fix 'ad personam'... is it worth it?

[Ryan Burke (theyield)]

Adding some information obtained last night:

On my YEPO 737A I flashed both Lubuntu and Elementary images to test if the suspend/wake "trick" would initialize the trackpad, and it did not. Both flashes making use of 4.15rc6.

Attacking this problem via BIOS seems problematic, as so many brand names produce cheap apollo lake machines with similar SYNA trackpad hardware: Jumper, chuwei, yepo, etc.

It really does feel like this is a delay issue as mentioned above, and jumper must have tightened this up of their own accord. I sincerely doubt the dozen or more other makers will do the same.

[Brad (bbaker6212)]

@theyield, It could be that 4.14.3 (and later 4.14.X versions) work better than 4.15.X
I found this true in my case. See this post on the TT forum: https://techtablets.com/forum/topic/how-to-install-antergos-linux-on-the-ezbook-3-pro-v4/page/3/#post-76098

[Ryan Burke (theyield)]

@Brad - As much as I dislike using "old" kernels, this is definitely worth testing. I'll try as you've suggested tonight and report back ASAP.

[Brad (bbaker6212)]

Kernel 4.14 is LTS (Long Term Support) for SIX years!... so maybe it gets more dev attention than 4.15? dunno. I did read there are some related Touchpad fixes to be rolled into 4.16 and no doubt back ported to 4.14.X

[Ryan Burke (theyield)]

That's fair enough. I'll be sure to try 4.14.3 as well as the newer .11 variant.

[Ryan Burke (theyield)]

Alright so 4.14.4 and .11 actually resulted in worse behaviour from the touch pad, and even some system wide instability. I'm back to 4.15-rc6 (Mint Cinnamon) and, although it will not initiate at boot, suspending gets me full functionality including multi touch gestures - and it doesn't randomly turn off while under use.

This is acceptable for daily driver use right now on this YEPO 737A. I'll be testing new kernels as they are released hoping for that coveted boot initialization.

[Cong Anh Huan Trinh (huantrinh1802)]

I am using EZbook 3L Pro with Ubuntu 16.04. Try to keep pressing left and right trackpad's buttons until the login shows up. The trackpad is working but not 2 buttons.

[Vi+ (vitaliyy)]

Touchpad still does not work (with "i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report" err in dmesg) as with latest v4.15-rc9 as with previous 4.15.0-rc7, 4.15.0-rc6, 4.14.0, 4.13.0-17 builds on YEPO 737A.

[iBART (mogio)]

Final hours. Waiting for the first 4.16 salvation kernel... ;)

[Kai-Heng Feng (kaihengfeng)]

Please try this kernel,

people.canonical.com/~khfeng/lp1728244-2/

[iBART (mogio)]

ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
Package: linux (not installed)
Tags: xenial
Uname: Linux 4.15.0+ x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[iBART (mogio)]

apport information

[iBART (mogio)]

apport information

[iBART (mogio)]

apport information

[iBART (mogio)]

Thanks Kai-Heng Feng but touch-pad is still not working.

[pstez84 (pstez84-linux-kernel-bugs)]

Same problem here on Chuwi LapBook Air
touchpad showing as ALPS0001:00 0911:5288 Touchpad
tried kernels 4.14.14 through 4.15.1 including discussed patches and all no goor on Arch Linux.

I have magaed to bodge the touchpad to work by constantly removing and re-adding the driver using modprobe but on first suspend, if the touchpad is enabled, my system crashes.

Any news would be helpful.

[mogio (mogio-linux-kernel-bugs)]

just wait 4.16 and see if all hid patches fixed the issue.

[iBART (mogio)]

Kernel 4.16, the saviour, didn't save us. From mainline (http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D)

TOUCH IS NOT WORKING AT ALL (rc1) linux-headers-4.16.0-041600rc1_4.16.0-041600rc1.201802120030_all.deb
TOUCH IS WORKING, BUTTONS ARE NOT (drm-intel) linux-image-4.14.0-997-generic_4.14.0-997.201712022100_amd64.deb

[iBART (mogio)]

this is the LAST working touchpad dmesg for drm-intel, after 201712022100 touch is not working.

[iBART (mogio)]

sorry, i meant drm-intel-next branch.

[iBART (mogio)]

This is the TRUE not working drm-intel (not the drm-intel-next I posted) dmesg.

[mogio (mogio-linux-kernel-bugs)]

Created attachment 274123
4.14, 4.15, 4.16... still not working.

From ubuntu mainline...

the last semi working touchpad (movements are ok, physical buttons are not working) is the drm-intel-next 4.14.0-997.201712022100. After this: kaput. :)

[Hans de Goede (j-w-r-degoede)]

Hi All,

So several people here are reporting that touch is not working for them at all, starting with 4.15 kernels, where as 4.14 works but does not have working buttons. The buttons thing is known and fixed (I believe), but that is of little help if touch no longer works at all.

I've a feeling that this might be related to my commit to fix touch on some devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=402946a8ef71ebfd1cbb19829db2da62906f0519

I'm attaching a revert of that patch, if someone (Bart?) can build a 4.15 generic kernel with that patch to revert the commit added and test that, then that would be great.

If reverting that commit does not work then someone will need to do a bisect between 4.14 and 4.15 to figure out what in 4.15 breaks the touchpad.

Regards,

Hans

[iBART (mogio)]

Hi Hans, again. Right now I don't have a very good PC to build kernels... my crappy ezbook takes ages. :D I hope Kai-Heng Feng (kaihengfeng) could do what you are asking! :)

I am not a pro, I don't know what the "bisect thing" means but I know exactly what kernel is working and what is not... a pro user could easily spots the bad commit!

From Ubuntu Mainline:

Last semi working (touch movements,no butons) 4.14 kernel is the the rc7 (4.14.0-041400rc7).
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7/

Last semi working (touch movements,no butons) drm-intel-next is the 4.14.0-997.201712022100_amd64.
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2017-12-03/

After those, KAPUT...

Thanks.

[Hans de Goede (j-w-r-degoede)]

Hi Bart,

In your previous comment you set that linux-image-4.14.0-997-generic_4.14.0-997.201712022100_amd64.deb is working, now you say that 4.14.0-041400rc7 is the latest working, and that 4.14 final does not work? linux-image-4.14.0-997-generic_4.14.0-997.201712022100_amd64.deb sounds like it is a final (non rc) build?

Note I'm not an Ubuntu developer, so I don't know how Ubuntu's kernel versioning scheme works.

If the generic kernel builds broke between 4.14-rc7 and 4.14.0 final then it should be easy (I hope) to pinpoint the problem. Also note that some people say rebooting is an issue so you should probably do a poweroff and then a cold boot for each test.

Also it is interesting to see if things don't work if doing a manual rmmod i2c-hid; modprobe i2c-hid helps.

Regards,

Hans

[iBART (mogio)]

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... :(

[Kai-Heng Feng (kaihengfeng)]

There you go,
http://people.canonical.com/~khfeng/lp1728244-revert/

[iBART (mogio)]

Thanks kaihengfeng.

Touch-pad is not working. :(

[Vi+ (vitaliyy)]

Touchpad is working and both 2 buttons are clickable after applying v4.16-rc1 (4.16.0-041600rc1-generic and 4.16.0-041600rc1-lowlatency), and only after returning back from "suspend" mode (before v4.16-rc1 both 2 buttons were not clickable even touchpad was working after "suspend") on my YEPO 737A laptop.

[Kai-Heng Feng (kaihengfeng)]

Hans,
Based on the test result, the commit is not the culprit.

[iBART (mogio)]

Vitaliyy, post your dmesg please.

[David Franko (lavjamanxd)]

I can't test the touchpad on 4.16, since it wont get up from suspend state. Tried it on 4.16-rc1 and 4.16-rc2 and it was the same. Resume from suspend worked on 4.15 but not on 4.16 and also on 4.15-rc9 i was able to get a half-working (cursor movement/tap, but no left/right buttons) touchpad after resuming the notebook from suspend.
My device is a Chuwi Lapbook Air.

[Vi+ (vitaliyy)]

iBART, dmesg @ YEPO 737A (obtained after closing the cover and opening it back after preliminary login - touchpad works with fully workable mouse and both buttons after that) is attached.

I used next cmds in order to automatically enter into 4.16.0-041600rc1-lowlatency after reboot:

yep ~ # wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/linux-headers-4.16.0-041600rc1-lowlatency_4.16.0-041600rc1.201802120030_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/linux-image-4.16.0-041600rc1-lowlatency_4.16.0-041600rc1.201802120030_amd64.deb
yep ~ # dpkg -i *.deb
yep ~ # reboot

[Mike O (mikognn)]

Does not work on 4.16.0-041600rc1-lowlatency on my YEPO 737S. I never had it working a bit, whichever kernel i booted. `dmesg` output is attached.

[iBART (mogio)]

Still not working for me. I just tried a new 4.16 kernel and I noticied that audio is not working. I tried a lot of 4.16 ubuntu kenerls and audio is not working in them.

[iBART (mogio)]

Reported.

https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1753298

[Mike O (mikognn)]

Still not working on 4.16.0-rc6. Is there actually development going on concering this issue?

[David Franko (lavjamanxd)]

Someone mentioned, if you blacklist the i2c_hid driver, then the resume/suspend starts working without deep freeze. (atleast on Chuwi Lapbook Air)

[Andrey (demontager)]

Teclast F7 affected this bug too, actually it uses same touchpad as Chuwi and Yepo.
I have compared dmesg messages from teclast f7 working on ubuntu 18.04 with above posted almost same messages there.

[jose (joselus)]

Also affected.

In my case I got a 4.15 kernel working in my jumper ezbook3 pro, ubuntu 17.10, the touchpad was detected as ImPS/2 protocol (so as an extended mouse) (enough for me), but after reinstall a ubuntu mate 18 (recent kernel) the touchpad is detected with CyPS/2 protocol and does not work at all.

[Robert Schuettler (rober)]

Jose, can you tell us which exact kernel 4.15 build you got to work? Can you also specify which revision of the Jumper EZbook 3 you are using?

If you don't know, you can find out your BIOS version and release date using:

 sudo dmidecode -s bios-version
 sudo dmidecode -s bios-release-date

[Bogdan Arabadzhi (hiseni)]

Another Teclast F7 user here.
Touchpad is not working for me at all on 18.04 daily.

Works fine on Windows 10 though. =\

[iBART (mogio)]

it is a lost cause. :)

[Vi+ (vitaliyy)]

My YEPO 737A with recent 4.16.1-041601-lowlatency kernel under Mint 18.3 still needs suspend in order to run touchpad smoothly after it (I expected 4.16 release will fix it finally, but it's not).

[Boris Urman (urmanbm)]

Hi, is there any progress on this bug?

[Boris Urman (urmanbm)]

Hi, I tried Ubuntu 160404 and Ubuntu 1804 beta 2 on Chuwi Lapboo air with live usb. On both of them touchpad didn't work. I am not very experienced with linux environment yet. Is there way for me to contribute in solving this problem&

[Andrey (demontager)]

Hi guys,
glad to inform that touchpad now is working on Teclast F7 running Xubuntu 18.04
It is just temporary workaround, hope it will added to default kernel.

All you need to do is patch kernel with that file https://github.com/brotfessor/sipodev/tree/master/b

1. Add needed packages before compiling kernel
sudo apt-get update
sudo apt-get build-dep linux
sudo apt-get install kernel-package
sudo apt-get install libncurses5-dev
sudo apt-get install libgtk2.0-dev libglib2.0-dev libglade2-dev
sudo apt-get install patch dpkg-dev

2. Download kernel sources
apt-get source linux-image-`uname -r`

3. Enter kernel folder and do config
cd linux-4.15.0/
make oldconfig

4. Replace original i2c-hid.c with one downloaded from github

mine located here
/home/teclast/linux-4.15.0/drivers/hid/i2c-hid/i2c-hid.c

5. Build kernel.This proccess might take over 1 hour
fakeroot make-kpkg -j 5 --initrd --append-to-version=-custom kernel_image kernel_headers

6. Compiled kernel will be located in home folder. Jump to it and install
dpkg -i *.deb

7. Update grup and reboot. You should have working touchpad now.
sudo update-grub

[Kai-Heng Feng (kaihengfeng)]

Please try this one:
https://people.canonical.com/~khfeng/lp1728244-bionic/

[David Franko (lavjamanxd)]

Tried it on my machine, it does not solve the touchpad problems on Chuwi Lapbook air, i think it has a different touchpad than what that fix solves.

lavjamanxd@sargeras:~/Downloads$ uname --all
Linux sargeras 4.15.0-20-generic #21~lp1728244 SMP Fri Apr 27 13:19:49 CST 2018 x86_64 x86_64 x86_64 GNU/Linux

:c

[Hans de Goede (j-w-r-degoede)]

Can people with this problem please boot with:

i2c_designware_core.dyndbg=+p i2c-hid.debug=1

Added to their kernel commandline and then directly after boot run:

dmesg > dmesg.log

And attach the generated dmesg.log file here?

[Vi+ (vitaliyy)]

@Hans de Goede (j-w-r-degoede)

[Olivier Fock (fpolive)]

Hi,

I had a Thomson X6 notebook, it's seems to be a Jumper Ebook 3 Pro rebranded.

I compiled original kernel from kernel.org.

- With 4.14 RC7 version, movements, simple ou double tab click, 2 finger gesture worked. But click buttons not.
- With 4.14 RC8 version, nothing works anymore ! I did some investigations.
  I copied the "drivers/base" files from 4.14 RC7 to 4.14 RC8. I compiled the custom kernel... and it works again (except click buttons).
- I did the same thing with the latest version currently available (4.14.41), I had the same behavior.
- With 4.16 version, after startup/reboot, the touchpad is recognized in log (dmesg) but it's not work. So, if I suspend and resume, gestures and even buttons are working !
- From my 4.14.41 version already patched ("drivers/base" files from 4.14 RC7), I copied "drivers/hid" and "drivers/input" files from 4.16.
  Now, everything works : gesture and buttons after a first startup and after suspend/resume.
  I don't know if "drivers/input" files modifications are really necessary, I will do a rollback and test later.

Obviously, I can't compile kernel if I replace files without minor modifications.

I analyzed the code changes (drivers/base) between the 4.14 RC7 and 4.14 RC8 versions. There are only a few lines that have been modified.
So I made the reverse modifications in version 4.16, but without success. Touchpad is still not work after startup/reboot but works only after suspend/resume.

In all versions (4.14 RC7 original, 4.14 RC8 and 4.14.41 modified, 4.16 original), I still have error messages :

[ 6.326589] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 6.328725] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713)
[ 6.329796] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 6.333024] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334)
[ 6.334090] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745)
[ 6.337295] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302)
[ 6.338385] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952)
[ 6.342743] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281)

[Olivier Fock (fpolive)]

Patch for 4.14.41 kernel

[Hans de Goede (j-w-r-degoede)]

Olivier Fock,

Thanks for your work on this, that is some excellent detective work. Also good to know that the "incomplete report" errors are also happening in a working setup.

The buttons starting to work after you updating the drivers/hid directory is expected, I have done several fixes to the hid-mt button handling, so I was already hoping that was fixed, but the other problem was blocking testing this.

So now I think we need to figure out which change exactly between the 4.14-rc7 and 4.14-rc8 drivers/base directory is causing the problem. To be clear are you talking vanilla 4.14-rc7 and 4.14-rc8 here, or Ubuntu kernel builds.

Looking at your diff, one thing which you could try is reverting this in your kernel / reapplying this fix from 4.14-rc8:

--- a/drivers/base/regmap/regmap.c 2018-05-16 10:10:32.000000000 +0200
+++ b/drivers/base/regmap/regmap.c 2017-10-29 21:58:38.000000000 +0100
@@ -1739,7 +1739,7 @@
   return -EINVAL;
  if (val_len % map->format.val_bytes)
   return -EINVAL;
- if (map->max_raw_write && map->max_raw_write < val_len)
+ if (map->max_raw_write && map->max_raw_write > val_len)
   return -E2BIG;

  map->lock(map->lock_arg);

The fix which went into your 4.14-rc8 (I don't see this in the vanilla 4.14-rc8) is obviously correct, but it could be that this is allowing some other driver to do something somewhere which is making the touchpad not work.

Something else to try is to revert this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7&id=0cc2b4e5a020fc7f4d1795741c116c983e9467d7

Which is in 4.17-rc7 but not in any later kernels, so your copying over of the drivers/base dir from 4.17-rc7 adds that commit and it would be interesting to see if dropping that commit from your special working kernel makes it non working again.

Eventually a different version of that commit did go upstream:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=0759e80b84e34a84e7e46e2b1adb528c83d84a47

But that is slightly different, so perhaps the original fix happens to somehow make the touchpad work.

Note there is no need to try reverting this commit if changing the max_raw_write check breaks/unbreaks the touchpad, then that is likely the cause and we need to debug further from there.

[Hans de Goede (j-w-r-degoede)]

What would also be helpful is an acpidump of your Thomson X6 as well the output of:

ls -l /sys/bus/i2c/devices

[Hans de Goede (j-w-r-degoede)]

And a dmesg directly after boot with the non-working 4.14-rc7 + another one with the working 4.14-rc8 based one would also be good.

[Olivier Fock (fpolive)]

Hans,

- I compiled a fresh 4.14-rc8 vanilla kernel and touchpad didn't work.

After applied this patch (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7&id=0cc2b4e5a020fc7f4d1795741c116c983e9467d7), the touchpad worked again !

To compile, I need to add "#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX" in somes files. I didn't modify .h file dependency.

$ grep -ri S32_MAX *
base/power/qos.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX
base/power/sysfs.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX
base/power/domain_governor.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX
base/cpu.c:#define PM_QOS_RESUME_LATENCY_NO_CONSTRAINT S32_MAX

Note, the unmodified file regmap.c contains this line :
if (map->max_raw_write && map->max_raw_write > val_len)

[Olivier Fock (fpolive)]

Some details about /sys/bus/i2c/devices/, note I used a 4.14-rc8 previously patched (#153)

olivier@debian:~$ uname -a
Linux debian 4.14.0-rc8 #2 SMP Sun May 20 20:25:16 CEST 2018 x86_64 GNU/Linux
olivier@debian:~$ ls -l /sys/bus/i2c/devices/
total 0
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-0 -> ../../../devices/pci0000:00/0000:00:02.0/i2c-0
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-1 -> ../../../devices/pci0000:00/0000:00:02.0/i2c-1
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-10 -> ../../../devices/pci0000:00/0000:00:17.1/i2c_designware.5/i2c-10
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-11 -> ../../../devices/pci0000:00/0000:00:17.2/i2c_designware.6/i2c-11
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-12 -> ../../../devices/pci0000:00/0000:00:17.3/i2c_designware.7/i2c-12
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-2 -> ../../../devices/pci0000:00/0000:00:02.0/i2c-2
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-3 -> ../../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-eDP-1/i2c-3
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-4 -> ../../../devices/pci0000:00/0000:00:1f.1/i2c-4
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-5 -> ../../../devices/pci0000:00/0000:00:16.0/i2c_designware.0/i2c-5
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-6 -> ../../../devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-6
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-7 -> ../../../devices/pci0000:00/0000:00:16.2/i2c_designware.2/i2c-7
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-8 -> ../../../devices/pci0000:00/0000:00:16.3/i2c_designware.3/i2c-8
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-9 -> ../../../devices/pci0000:00/0000:00:17.0/i2c_designware.4/i2c-9
lrwxrwxrwx 1 root root 0 mai 20 21:23 i2c-SYNA3602:00 -> ../../../devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-6/i2c-SYNA3602:00
pi@debian:~$

[Olivier Fock (fpolive)]

dmesg log

[Hans de Goede (j-w-r-degoede)]

Olivier Fock,

Thanks, so it seems that: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/base?h=v4.14-rc7&id=0cc2b4e5a020fc7f4d1795741c116c983e9467d7
on top of 4.17-rc8 fixes things again, that is very interesting.

You may want to try a recent kernel and then do:

git revert 0759e80b84e34a84e7e46e2b1adb528c83d84a47
git cherry-pick 0cc2b4e5a020fc7f4d1795741c116c983e9467d7

And see what that does (assuming this applies cleanly).

At this point I think that we need to get some upstream kernel developers involved. Can you send me an email at: <email address hidden> please? (I need your email address) then I will start an email discussion about this with you in the Cc.

Regards,

Hans

[Olivier Fock (fpolive)]

I finally managed to have a working 4.16.10 kernel (touchpad, gesture, buttons, sdcard, sound, etc...).

I reverted this patch 0759e80b84e34a84e7e46e2b1adb528c83d84a47 (applied cleanly) and applied manually 0cc2b4e5a020fc7f4d1795741c116c983e9467d7. I'll attach a full diff later.

So that's the proof that's the "PM / QoS: Fix device resume latency PM QoS" patch doesn't work on Thomson X6 (https://www.mythomson.com/fr_fr/ordinateurs-155-fr-fr/ultrabook-158-fr-fr/ultrabook-13-3-32-go-2452).

@Hans, I'll contact you by email.

Regards,
Olivier

[Olivier Fock (fpolive)]

Patch for kernel 4.16.10 to fix touchpad problems of Thomson X6 (revert PM / QoS: Fix device resume latency PM QoS patch)

[Hans de Goede (j-w-r-degoede)]

Olivier, thank you excellent work. I've mailed the upstream developers and the author of the patch of which the older version fixes things.

Kai-Heng, can you perhaps do a test Ubuntu kernel build with the patch from comment 158, then other users with different (but similar) model laptops can test and hopefully confirm that this fixes things for them too. Note I don't believe that this is the proper fix, but it will be good to have confirmation that this fixes things for others too.

[David Franko (lavjamanxd)]

Oliver & Hans, thank you!

After reverting that patch and applying the other one + resolving the conflicts, i can confirm it works on 4.17.0-rc6 (chuwi lapbook air).
Movement, tap, scroll, left and right button.

[iBART (mogio)]

If someone compile I can test it on my jumper v4 ezbook

Il mer 23 mag 2018, 09:40 David Franko <email address hidden> ha
scritto:

> Oliver & Hans, thank you!
>
> After reverting that patch and applying the other one + resolving the
> conflicts, i can confirm it works on 4.17.0-rc6 (chuwi lapbook air).
> Movement, tap, scroll, left and right button.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728244
>
> Title:
> Touchpad stops working after reboot on Apollo Lake
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions
>

[Kai-Heng Feng (kaihengfeng)]

Of course. Here's the Kernel:
https://people.canonical.com/~khfeng/lp1728244-testing/

[iBART (mogio)]

Ezbook Jumper 3 PRO V4: touchpad is fully working.

Good job guys :D

2018-05-24 7:02 GMT+02:00 Kai-Heng Feng <email address hidden>:

> Of course. Here's the Kernel:
> https://people.canonical.com/~khfeng/lp1728244-testing/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728244
>
> Title:
> Touchpad stops working after reboot on Apollo Lake
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions
>

--
*Cordialmente, Mich.*
- *[phone]*
- *<email address hidden> <email address hidden>*

[David Franko (lavjamanxd)]

After using that patched kernel for 2 days, it's also solves the suspend freezing problem, i am able to close the lid and open it without removing the i2c_hid.
Also theres no random freezes/slowdowns like on the 4.14-rc7 kernel.

[Olivier Fock (fpolive)]

I found the line which causes troubles. Rafael J. Wysocki's comments put me on the path (https://bugzilla.kernel.org/show_bug.cgi?id=199821).

In the file "include/linux/pm_qos.h", if you set the PM_QOS_RESUME_LATENCY_NO_CONSTRAINT constant to value 0, then it works.

I used a vanilla 4.16.10 kernel and without reverting patch like before.

Olivier

[Mike O (mikognn)]

The patched kernel results in trackpad fully working on my Yepo 737A. Buttons, tracking, tapping for doubleclick and two-finger-gesture. Very good research work, guys!

Did someone already talk to upstream/mainline for investigation and further steps?

[Kai-Heng Feng (kaihengfeng)]

Hans is the upstream guy here ;)

[David Perez Millan (david-perez-millan)]

188/5000
I have a Jumper Ezbook v3 and it seems to work correctly, running on Ubuntu 18.04.
Mouse movement and double pulsation.
I would have to check, buttons, suspension and two fingers.

[David Perez Millan (david-perez-millan)]

In Ezbook v3 works the scroll, left button and gestures with two fingers, but the right button does not work.
Testing suspension ... works correctly

[Hans de Goede (j-w-r-degoede)]

David Perez Millan,

Please run gnome-tweaks and go to: "Keyboard & Mouse" then under "Mouse Click Emulation" select "Area" that should give you a right click at the bottom right area of the touchpad.

Regards,

Hans

[iBART (mogio)]

V4 Jumper 3 pro, touchpad works perfectly BUT now something is wrong with
the mouse. It has lag. :D

2018-05-25 17:02 GMT+02:00 David Perez Millan <email address hidden>
:

> In Ezbook v3 works the scroll, left button and gestures with two fingers,
> but the right button does not work.
> Testing suspension ... works correctly
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1728244
>
> Title:
> Touchpad stops working after reboot on Apollo Lake
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions
>

--
*Cordialmente, Mich.*
- *[phone]*
- *<email address hidden> <email address hidden>*

[David Perez Millan (david-perez-millan)]

Hi, Hans de Goede.
Following your instructions the right button works correctly.
Thank you very much.

For me this solution is correct, I hope it is implemented.

[iBART (mogio)]

Is it going mainline?

[jfdesign (jfdesignnet)]

Hi. Can confirm it's working good too on Mybook-14 apollolake N3350 laptop with [SYNA3602:00 0911:5288] touchpad. Using 18.04 fresh install and kernel 4.17.0-1 from khfeng, thank you very much.

i2c_hid_get_input still throw garbage incomplete report, but movement, tap, button all works okay.
once again thanks and hope this will go upstream.

[Sven Meyer (sven.meyer)]

I have a Yepo 737A and just installed the modified kernel

Kai-Heng Feng (kaihengfeng) wrote on 2018-05-24: #162
Of course. Here's the Kernel:
https://people.canonical.com/~khfeng/lp1728244-testing/

Touchpad is working great! Mouse movement works, corners for left and right click worked.

I attached (after boot) an external USB-mouse: that one is working great as well, no problems, no problems with mouse pad while external mouse is attached, no lag or what so ever.

Great work, thanks a lot. That makes the finally a great cheap Linux computer.

btw: If you remove the bottom cover and remove the thread for the M.2 SATA SSD, then it even fits the larger (chewing gum sized) SSDs 2280. I insulated the metal and fixed the SSD with some tape.
If you really want to do it properly then you add some thermal 1 mm laver on top so that it touches SSD and metal cover.

[Sven Meyer (sven.meyer)]

I am running Lubuntu 18.04 with the kernel from @kaihengfeng

[Christophe Caralp (chrisbi)]

I have a Yepo 737A, when i use linux-modules-extra-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb, i can use WIFI, i have a error when i want to connetc to my SSID

An idea?

[Brad (bbaker6212)]

@chrisbi, this bug is about a touchpad-kernel. It's not the right place for your post/question about wifi-kernel.

[Boris Urman (urmanbm)]

Hi, does anyone know when this bug will be fixed?

I really would love to use Ubuntu on my Chuwi Lapbook Air but I can't because touchpad doesn't work.

[Brad (bbaker6212)]

@Boris, it depends what is the touchpad device you have in your Lapbook Air.
There is a couple of patches rolled into kernel 4.17 and 4.18 ...

https://forum.manjaro.org/t/lenovo-ideapad-330-touchpad-not-working/50764/12
https://forum.manjaro.org/t/touchpad-syna3602-0911-5288-not-working-at-all/36269/49

plus the above mentioned SYNA3602 patch for the Ubuntu distro.

[Boris Urman (urmanbm)]

@bbaker6212 Hi, Brad

Thank you for quick answer.

Touchpad model is HID\ALPS0001. Laptop is Chuwi Lapbook Air 14.1.

I tried linux kernel 4.18rc8 with Ubuntu 18.04 today and touchpad didn't work at all there. Could you please guide me on how to make it work?

[Brad (bbaker6212)]

@Boris, there is a mention in this Arch Linux discussion thread of Kernel 4.14.04 and 4.14-rc7 working for your touchpad:
https://bbs.archlinux.org/viewtopic.php?pid=1768446#p1768446
 I don't know why kernel 4.18 would not also have this fix. If it works, then just don't update the kernel.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc7/

[PS!] See this. There there is at least one other bug already open on this specific to the ALPS0001 touchpad: https://bugzilla.redhat.com/show_bug.cgi?id=1569422

[Brad (bbaker6212)]

@Boris, it's probably better you followup on these bug threads more specific to your Notebook and touchpad device:
https://bugzilla.redhat.com/show_bug.cgi?id=1591307#c6

Hans de Goede 2018-06-17 05:56:11 EDT
(In reply to Viktar from comment #0)
> I am trying to use Fedora 28 on Chuwi Lapbook Air, but touchpad does not
> work.
> Similar problem was in bug "1526312", but it seems like I have ALPS touchpad
> and modified "i2c-hid.c" file does not work for me after recompiling the
> kernel.

I don't think you have the same issue, the problem in bug 1526312 is a touchpad with missing descriptors.

I think what you are seeing is the same i2c-hid touchpad power-management issue as other people or seeing on various ezbook models. This is currently being discussed here:

https://bugzilla.kernel.org/show_bug.cgi?id=199821

The touchpad should work after a suspend/resume. You may need to do:

sudo rmmod i2c-hid
sudo modprobe i2c-hid

After suspend-resume.

[Daniele Della Rocca (daniele95100)]

Hi, can anyone explain me how to use the patched kernel of the comment #162 in linux mint 19? or how can apply the patch and compile the kernel?
I have used the kernel with ubuntu on my yepo 373a and the touchpad worked, but now i'm trying to do the same thing with linux mint and i'm having no success, perhaps the system boots with the wrong kernel.
Thanks.
Daniele.

[Brad (bbaker6212)]

@Daniele, go to the Ubuntu or Linuxmint forums or documentation and look up the command:
sudo dpkg -i *.deb
And you might have to update Grub as well.

[Hans de Goede (j-w-r-degoede)]

Good news (hopefully) it looks like we finally have found a fix which is not an ugly hack / does not disable runtime pm for other devices which will hopefully fix this.

Kai-Heng Feng, can you build a kernel with this patch:

https://patchwork.kernel.org/patch/10597519/

Added for reporters of this bug to test ?

That patch hopefully resolves this in a supportable/maintainable way.

[Kai-Heng Feng (kaihengfeng)]

Sure.

Kernel with the patch included:
https://people.canonical.com/~khfeng/lp1728244-norpm/

[carloslp (carloslp)]

I have not tested the kernel from Kai-Heng, but I have tested to rebuild my i2c-hid module after applying the patch from https://patchwork.kernel.org/patch/10597519/ (running kernel 4.17.0-0.bpo.3-amd64 on Debian Stretch) and I can confirm that the touchpad now works fine on a Yepo 737A

[Robert Schuettler (rober)]

Kernel from #187 (4.15.0-35 generic; 2018-09-12) works fine on Jumper EZbook. Thanks a lot Hans and Kai-Heng!

[Robert Schuettler (rober)]

OK, the touchpad works (same as it did with 4.14.0-997; 2017-12-02), but there are still some error messages:

 kernel: i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/1)
 kernel: i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)

Also the "hardware-buttons" don't generate left and right mouse-clicks, but point-and-click (left) as well as 2-finger-click (right mouse button) work -- at least once Gnome desktop has started.

[Hans de Goede (j-w-r-degoede)]

Robert,

There are some patches pending upstream to fix the "incomplete report" errors in the mean time these can be safely ignored.

As for you needing to do a 2-finger-click to get a right click, that means that libinput is configured for clickfinger behavior rather then click areas.

To change this run gnome-tweaks and go to: "Keyboard & Mouse" then under "Mouse Click Emulation" select "Area" that should give you a right click at the bottom right area of the touchpad.

Regards,

Hans

[Boris Urman (urmanbm)]

Hi, Hans/Kai-Heng Feng

I tried kernel from comment #187 on Chuwi Lapbook Air 14.1 with touchpad HID\ALPS0001. It doesn't work for me completely - neither trackpad nor buttons. Is there anyhow I can help troubleshoot this issue?

BTW. Hans, thank you for your support and answers in my previous question.

[Kai-Heng Feng (kaihengfeng)]

Boris,

Can you attach dmesg? Or even better, file a new bug since it may be a different issue.

[iBART (mogio)]

Would be nice having it on mainline. 😅

[Olaf (hein-jessen)]

Hello,

have a Telcast F7 should be also the Touchpad SYNA3602, but not working with Kernel 4.15035.
Does anyone know when the patch comes in the current Ubuntu kernel?

[elPraga (elpraga)]

Hello,

I've tried briefly this kernel: https://people.canonical.com/~khfeng/lp1728244-testing/ on the Chuwi Lapbook Air using the current Ubuntu 18.10 (not officially released yet). Touchpad was working, no right button, but I didn't know about the GnomeTweak hack mentioned above. @urmanbm use this kernel.

@kaihengfeng Is there a chance for your patches to be included in the official 18.10 kernel?

It would help a lot..

[elPraga (elpraga)]

I can now confirm that two finger scrolling is working, and tapping with two fingers works like a charm as the rightclick on Chuwi Lapbook Air.

[Boris Urman (urmanbm)]

Hi, Kai-Heng @kaihengfeng

Please find attached dmesg file. This is with kernel from comment #187. Should I file a new bug from it?

@elpraga, thank you. I wil try kernel from comment #162 and write back my testing results here.

[Boris Urman (urmanbm)]

@elpraga, @kaihengfeng

I can confirm that touchpad works perfectly with kernel from #162 on Chuwi Lapbook Air, Ubuntu 18.04. Please find attached dmesg for it.

Is there anyhow I can help further to resolve this issue?

[Kai-Heng Feng (kaihengfeng)]

Boris,

Does it work after S3?

[Boris Urman (urmanbm)]

Kai-Heng @kaihengfeng,

Kernel from #187 doesn't work after Suspend on Ubuntu 18.04.

[elPraga (elpraga)]

Hi Kai-Heng @kaihengfeng,

I can confirm that suspend works as expected under Ubuntu 18.10 using the kernel from comment #162.

[Mikhail (sul)]

Hello,

I've got Chuwi Lapbook Air and the touchpad doesn't work with Ubuntu 18.10 latest kernel v4.19, so the only one proper kernel for me it's the one from #162. Are those changes going to be included in the official Ubuntu's kernel someday?

[Kai-Heng Feng (kaihengfeng)]

The issue should be fixed by next Bionic kernel. Should be release at January.

[Kai-Heng Feng (kaihengfeng)]

Another Bionic back port here:
https://people.canonical.com/~khfeng/lp1728244/bionic/

Make sure the system gets coldboot (shutdown) before testing.

If this doesn't work, please file a new bug. Quite possibly the touchpad is different.

[Dawid Olesinski (dawidro)]

EZBook 3 Pro v4 Touchpad stil not working. I've tried kernels from comment #187 (v4.15.0-35) and comment #221 (v4.15.0-43.46) and both haven't worked. I have tried to reload modules for both kernels as well as suspending laptop. Nothing helps.
Kernel v4.14-rc7 from comment #3 works correct apart from hard buttons.

dmidecode -s bios-version
JUMPER2x.P8.WP313R.NHNAUHN05
dmidecode -s bios-release-date
09/30/2017
[ 6.410333] hid-multitouch 0018:0911:5288.0003: input,hidraw2: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00

[Brad (bbaker6212)]

Try Manjaro with kernel 4.19.xx or LinuxMint latest. There have been various fixes for touchpad in newer kernels.

[Brad (bbaker6212)]

I don't know about LinuxMint but you can install Manjaro onto a USB destination drive and boot from that to test it out first/without touching your HDD/SD installation.

[Dawid Olesinski (dawidro)]

Linux Mint uses Ubuntu kernels so it won't work as I have tried newer kernels as well (I'm on Ubuntu 18.04) I haven't tried Manjaro but I have installed Arch free days ago and it didn't work. I guess I will have to stick to that kernel 4.14-rc7 for some time. I might give it a go with Manjaro tho.

[Brad Figg (brad-figg)]

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 4.15.0-44.47

---------------
linux (4.15.0-44.47) bionic; urgency=medium

  * linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts

  * CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
    - blk-wbt: pass in enum wbt_flags to get_rq_wait()
    - blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
    - blk-wbt: move disable check into get_limit()
    - blk-wbt: use wq_has_sleeper() for wq active check
    - blk-wbt: fix has-sleeper queueing check
    - blk-wbt: abstract out end IO completion handler
    - blk-wbt: improve waking of tasks

  * To reduce the Realtek USB cardreader power consumption (LP: #1811337)
    - mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't support
      1.8v
    - mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
    - mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
    - mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
    - mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
    - mmc: rtsx_usb_sdmmc: Re-work runtime PM support
    - mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
    - memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
    - misc: rtsx_usb: Use USB remote wakeup signaling for card insertion detection
    - memstick: Prevent memstick host from getting runtime suspended during card
      detection
    - memstick: rtsx_usb_ms: Use ms_dev() helper
    - memstick: rtsx_usb_ms: Support runtime power management

  * Support non-strict iommu mode on arm64 (LP: #1806488)
    - iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
    - iommu/arm-smmu-v3: Implement flush_iotlb_all hook
    - iommu/dma: Add support for non-strict mode
    - iommu: Add "iommu.strict" command line option
    - iommu/io-pgtable-arm: Add support for non-strict mode
    - iommu/arm-smmu-v3: Add support for non-strict mode
    - iommu/io-pgtable-arm-v7s: Add support for non-strict mode
    - iommu/arm-smmu: Support non-strict mode

  * ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
    - pinctrl: cannonlake: Fix community ordering for H variant
    - pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant

  * Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
    - perf: Export perf_event_update_userpage
    - Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
    - drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
    - [Config] New config CONFIG_THUNDERX2_PMU=m

  * Update hisilicon SoC-specific drivers (LP: #1810457)
    - SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi BD"
    - Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
      resetting"
    - Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling roce
      callback function"
    - Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
      function when link status change"
    - Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of notifying
      roce client"
    - Revert "UBUNTU: S...

[Andy Whitcroft (apw)]

This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed.

[elPraga (elpraga)]

Has the fix been applied in Cosmic already?

I've just tried to install the proposed kernel (linux-4.18.0-16-generic), and the touchpad _is not_ working. I have to keep using the 4.17 kernel from this thread.

[Kai-Heng Feng (kaihengfeng)]

elPraga, please file a new bug report, thanks!

[You-Sheng Yang (vicamo)]

Landed to upstream as commit 807588ac92018, sru-ed to Bionic as 459448830a9b0 and Cosmic as commit 35e4595ea550f in bug 1801931. Disco or newer has it automatically.