Touchpad on Gemibook Pro stops working on 21.10 (Live USB or via upgrading from 20.04/21.04)

Any ideas on what I could do to resolve this? It appears like I can’t even see it via xinput or any other means. Downgraded back to 20.04 as a result. The audio also does not work by the ES8336 has a patch out there that has not yet been upstreamed.

This is the reading I get under 20.04, but again none of this appears under 21.10, also on 21.04 the touchpad had worked.

xinput --list

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SYNA3602:00 093A:0255 Mouse             	id=11	[slave  pointer  (2)]
⎜   ↳ SYNA3602:00 093A:0255 Touchpad          	id=12	[slave  pointer  (2)]
cat /proc/bus/input/devices

I: Bus=0018 Vendor=093a Product=0255 Version=0100
N: Name="SYNA3602:00 093A:0255 Mouse"
P: Phys=i2c-SYNA3602:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA3602:00/0018:093A:0255.0001/input/input10
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=2
B: EV=17
B: KEY=1 30000 0 0 0 0
B: REL=3
B: MSC=10

I: Bus=0018 Vendor=093a Product=0255 Version=0100
N: Name="SYNA3602:00 093A:0255 Touchpad"
P: Phys=i2c-SYNA3602:00
S: Sysfs=/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA3602:00/0018:093A:0255.0001/input/input11
U: Uniq=
H: Handlers=mouse1 event6 
B: PROP=5
B: EV=1b
B: KEY=e520 30000 0 0 0 0
B: ABS=2e0800000000003
B: MSC=20

Smells like a kernel issue since it isn’t even visible.

If you are up for it I would retry again but this time test install the latest 5.16 mainline kernel

Either way, for kernel bugs at a minimum you will need to file a bug against the linux package.

This looks like your issue https://bugzilla.kernel.org/show_bug.cgi?id=209413

So it’s the kernel module in that link that needs further prodding at.

Yea, I just read up last night on ukuu or now the mainline GUI app to help me update the kernel to the latest 5.16 rc4 kernel and sadly it appears the touchpad remains broken and my ES8336 sound chip still remains broken (despite speculation that they’d be including an update to enable my sound for this laptop too).

Thank you for finding that bug report too, I will take a look at it. It does look like if I want this laptop working that I might be having to track down whats going on with the touchpad and manually adding in a patch for ES8336 till its inclusion happens.

I am not entirely sure that my issue really aligns with theirs, mine is synaptic, but I have not seen any references to elan (which I guess is also synaptic). I am going to update my grub so I can more easily select which kernel to boot into and incrementally go up until I find the exact kernel that started to break it. I figure that will give me a much clearer picture, because even the latest kernel does not fix it, so I assume it is a regression of some kind.

There is a sleep bug as well that kills the touchpad, even with working kernels… but one thing at a time lol.

Faulty loads on the touchpad happen at 5.13.x kernels. Going to reboot in 5.12.x and compare.

journalctl | grep i2c

Dec 10 13:33:18 rreaves-gbp14 kernel: i2c /dev entries driver
Dec 10 13:33:18 rreaves-gbp14 kernel: i2c i2c-0: 2/2 memory slots populated (from DMI)
Dec 10 13:33:18 rreaves-gbp14 kernel: i2c_designware i2c_designware.0: controller timed out
Dec 10 13:33:18 rreaves-gbp14 kernel: ov13858: probe of i2c-OVTID858:01 failed with error -22

Working touchpad on Kernel 5.12.19

Dec 10 13:57:44 rreaves-gbp14 kernel: i2c /dev entries driver
Dec 10 13:57:44 rreaves-gbp14 kernel: i2c i2c-0: 2/2 memory slots populated (from DMI)
Dec 10 13:57:44 rreaves-gbp14 kernel: input: SYNA3602:00 093A:0255 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA3602:00/0018:093A:0255.0001/input/input5
Dec 10 13:57:44 rreaves-gbp14 kernel: input: SYNA3602:00 093A:0255 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA3602:00/0018:093A:0255.0001/input/input6
Dec 10 13:57:44 rreaves-gbp14 kernel: hid-generic 0018:093A:0255.0001: input,hidraw0: I2C HID v1.00 Mouse [SYNA3602:00 093A:0255] on i2c-SYNA3602:00
Dec 10 13:57:45 rreaves-gbp14 kernel: ov13858: probe of i2c-OVTID858:01 failed with error -22
Dec 10 13:57:45 rreaves-gbp14 kernel: input: SYNA3602:00 093A:0255 Mouse as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA3602:00/0018:093A:0255.0001/input/input11
Dec 10 13:57:45 rreaves-gbp14 kernel: input: SYNA3602:00 093A:0255 Touchpad as /devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-1/i2c-SYNA3602:00/0018:093A:0255.0001/input/input12
Dec 10 13:57:45 rreaves-gbp14 kernel: hid-multitouch 0018:093A:0255.0001: input,hidraw1: I2C HID v1.00 Mouse [SYNA3602:00 093A:0255] on i2c-SYNA3602:00

These people seemed like they were tracking the issue until recently, but I suspect this is a regression.
https://bbs.archlinux.org/viewtopic.php?id=252711&p=2

These look related as well, but it is saddening to see that an interrupt storm and cpu spike may be happening after suspend with this trackpad… I do not see anything open currently for 5.13.x+ but this is definitely a kernel level issue.
https://bugzilla.kernel.org/show_bug.cgi?id=200787
https://bugzilla.redhat.com/show_bug.cgi?id=1526312