Touchpad stops working after reboot on Apollo Lake

Bug #1728244 reported by Giorgio Andronico on 2017-10-28
114
This bug affects 17 people
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
Medium
Unassigned
Bionic
Undecided
Unassigned

Bug Description

===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?

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.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: zesty
Giorgio Andronico (bytecodex2) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Giorgio Andronico (bytecodex2) wrote :

Still not fixed. Updated tag.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
iBART (mogio) wrote :

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) wrote :

Can you attach dmesg under v4.14-rc7?

iBART (mogio) wrote :

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

iBART (mogio) wrote :

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

iBART (mogio) wrote :

xinput attached, same kernel 4.14.0-041400rc7

iBART (mogio) wrote :

4.14.0-041400rc8

touchpad is not working at all.

iBART (mogio) wrote :

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

191 comments hidden view all 231 comments

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.

Changed in linux (Ubuntu):
status: Confirmed → Triaged

latests daily has the trackpad not working at all.

4.14-0.999

191 comments hidden view all 231 comments

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

tags: added: apport-collected xenial

apport information

apport information

apport information

iBART (mogio) wrote :

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

4.14-0.999

Kai-Heng Feng (kaihengfeng) wrote :

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

Thanks.

iBART (mogio) wrote :

here sir.

Brad (bbaker6212) wrote :

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

Brad (bbaker6212) 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..."

Brad (bbaker6212) wrote :

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.

183 comments hidden view all 231 comments

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.

(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

182 comments hidden view all 231 comments

> 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) 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?

1 comments hidden view all 231 comments
Kai-Heng Feng (kaihengfeng) wrote :

> 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) wrote :

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) wrote :

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

Brad (bbaker6212) wrote :

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

Brad (bbaker6212) wrote :

@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) wrote :

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) wrote :

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.

176 comments hidden view all 231 comments

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.

175 comments hidden view all 231 comments
Brad (bbaker6212) wrote :
Download full text (4.4 KiB)

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

Read more...

Brad (bbaker6212) wrote :

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

Brad (bbaker6212) wrote :

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/

174 comments hidden view all 231 comments

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

173 comments hidden view all 231 comments
IGOR' (i.guliaew) wrote :

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:

tags: added: patch
Kai-Heng Feng (kaihengfeng) wrote :

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

iBART (mogio) wrote :

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

172 comments hidden view all 231 comments

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.

171 comments hidden view all 231 comments
Brad (bbaker6212) wrote :

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

iBART (mogio) wrote :

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 :)

171 comments hidden view all 231 comments

Created attachment 260639
dmesg > dmesg_4.14_patch_i2c_debug

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

170 comments hidden view all 231 comments
Brad (bbaker6212) wrote :

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

iBART (mogio) wrote :

here it is.

170 comments hidden view all 231 comments

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

@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.

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

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

@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

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.

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

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

25 comments hidden view all 231 comments
Boris Urman (urmanbm) wrote :

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) wrote :

Boris,

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

iBART (mogio) wrote :

Would be nice having it on mainline. 😅

Olaf (hein-jessen) wrote :

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) wrote :

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) wrote :

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) wrote :

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) wrote :

@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) wrote :

Boris,

Does it work after S3?

Boris Urman (urmanbm) wrote :

Kai-Heng @kaihengfeng,

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

elPraga (elpraga) wrote :

Hi Kai-Heng @kaihengfeng,

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

Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
16 comments hidden view all 231 comments
Mikhail (sul) wrote :

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) wrote :

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

Kai-Heng Feng (kaihengfeng) wrote :

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.

description: updated
Changed in linux (Ubuntu Bionic):
status: New → In Progress
Changed in linux (Ubuntu Bionic):
status: In Progress → Fix Committed
Dawid Olesinski (dawidro) wrote :

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) wrote :

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

Brad (bbaker6212) wrote :

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) wrote :

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) wrote :

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!

tags: added: verification-needed-bionic
Launchpad Janitor (janitor) wrote :
Download full text (47.0 KiB)

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

Changed in linux (Ubuntu Bionic):
status: Fix Committed → Fix Released
Andy Whitcroft (apw) wrote :

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

tags: added: kernel-fixup-verification-needed-bionic verification-done-bionic
removed: verification-needed-bionic
elPraga (elpraga) wrote :

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) wrote :

elPraga, please file a new bug report, thanks!

You-Sheng Yang (vicamo) wrote :

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.

Displaying first 40 and last 40 comments. View all 231 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.