Touchpad stops working after reboot on Apollo Lake

Bug #1728244 reported by Giorgio Andronico on 2017-10-28
74
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Medium
Unassigned

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?

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

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

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.

1 comments hidden view all 141 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 141 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.

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/

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

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

Brad (bbaker6212) wrote :

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

iBART (mogio) wrote :

here it is.

61 comments hidden view all 141 comments
Brad (bbaker6212) wrote :

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

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

Ryan Burke (theyield) wrote :

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.

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

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

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

Kai-Heng Feng (kaihengfeng) wrote :

Please try this kernel,

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

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

apport information

apport information

apport information

iBART (mogio) wrote :
iBART (mogio) wrote :

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

iBART (mogio) wrote :

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

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

iBART (mogio) wrote :

sorry, i meant drm-intel-next branch.

iBART (mogio) wrote :

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

Hans de Goede (j-w-r-degoede) wrote :

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

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

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

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

iBART (mogio) wrote :

Thanks kaihengfeng.

Touch-pad is not working. :(

Vi+ (vitaliyy) wrote :

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

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

iBART (mogio) wrote :

Vitaliyy, post your dmesg please.

David Franko (lavjamanxd) wrote :

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

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

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

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.

Mike O (mikognn) wrote :

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

David Franko (lavjamanxd) wrote :

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

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

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

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

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

it is a lost cause. :)

Vi+ (vitaliyy) wrote :

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

Hi, is there any progress on this bug?

Displaying first 40 and last 40 comments. View all 141 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.