Touchpad detected as SYNA3602, does not work at all.

[Reffman]

On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine.

It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625

If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem.

martin@alanah:~$ cat /proc/bus/input/devices

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2 leds
B: PROP=0
B: EV=120013
B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

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=1b
B: KEY=e420 30000 0 0 0 0
B: ABS=260800000000003
B: MSC=20

I: Bus=0003 Vendor=045e Product=00b9 Version=0111
N: Name="Microsoft Microsoft USB Wireless Mouse"
P: Phys=usb-0000:00:15.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16
U: Uniq=
H: Handlers=mouse1 event15
B: PROP=0
B: EV=17
B: KEY=1f0000 0 0 0 0
B: REL=1c3
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Jun 11 07:57:56 2018
InstallationDate: Installed on 2018-04-25 (46 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: martin 1536 F.... pulseaudio
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-04-25 (48 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: Multicom Multicom U230
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic N/A
 linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/15/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ORO10x.WP313P.NHNAUHL01
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.family: U-series
dmi.product.name: Multicom U230
dmi.product.version: Default string
dmi.sys.vendor: Multicom

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17

[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 1776155

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.

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

apport information

[Reffman (ventruejusticar)]

@Joseph Salisbury, as specified in the OP this is a fresh install. Previous versions of Ubuntu (older than 18.04) will not boot on this latest generation of notebooks/netbooks at all due to Secure Boot.

[Reffman (ventruejusticar)]

Installing kernel 4.17.1 did not help:

martin@alanah:~$ uname -r
4.17.1-041701-generic

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-5/i2c-SYNA3602:00/0018:0911:5288.0002/input/input17
U: Uniq=
H: Handlers=mouse1 event7
B: PROP=5
B: EV=1b
B: KEY=e420 30000 0 0 0 0
B: ABS=260800000000003
B: MSC=20

[Kai-Heng Feng (kaihengfeng)]

Does the touchpad start to work after suspend/resume?

[Reffman (ventruejusticar)]

No. It is, and has always been completely dead. Except on Windows 10, where it worked fine. I did not think to check on what make it was reported as under Win 10 device manager, unfortunately, before I installed Ubuntu 8.04 beta 2.

There has been no previous installation of Ubuntu on this laptop, because Ubuntu versions older than 18.04 fail to boot due to UEFI SecureBoot.

Suspend/resume does not work either, by the way. But this is nornal for Ubuntu on netbooks.

[Jeffrey L Sussman (unspecified)]

Kai-Heng:

No, the touch pad still doesn't work even after I suspend/resume.

I've attached the dmesg output.

also this part of that output seems relevant:

dmesg | grep -i i2c-syna
[ 5.756115] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not
found, using dummy regulator
[ 5.760556] i2c_hid i2c-SYNA3602:00: unexpected HID descriptor
bcdVersion (0x00ff)

Thanks for asking.

Jeff

On Fri, Jul 6, 2018 at 1:19 PM, Kai-Heng Feng <email address hidden>
wrote:

> Does the touchpad start to work after suspend/resume?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1776155
>
> Title:
> Touchpad detected as SYNA3602, does not work at all.
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> On my cheaper-end slimline laptop/netbook the touchpad is (I think
> wrongly) detected by Linux to be the SYNA 3602. Anyway it does not
> work at all, neither touchpad nor buttons. Freshly installed Ubuntu
> 18.04 system. External mouse works fine.
>
> It seems that there is a bug reported on a similar issue, although I
> can not confirm that my touchpad hardware is exactly the same:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625
>
> If so, there may be a whole new generation of slimline Windows 10
> netbooks that have this problem.
>
> martin@alanah:~$ cat /proc/bus/input/devices
>
> I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
> N: Name="AT Translated Set 2 keyboard"
> P: Phys=isa0060/serio0/input0
> S: Sysfs=/devices/platform/i8042/serio0/input/input2
> U: Uniq=
> H: Handlers=sysrq kbd event2 leds
> B: PROP=0
> B: EV=120013
> B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
> B: MSC=10
> B: LED=7
>
> 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=1b
> B: KEY=e420 30000 0 0 0 0
> B: ABS=260800000000003
> B: MSC=20
>
> I: Bus=0003 Vendor=045e Product=00b9 Version=0111
> N: Name="Microsoft Microsoft USB Wireless Mouse"
> P: Phys=usb-0000:00:15.0-1/input0
> S: Sysfs=/devices/pci0000:00/0000:00:15.0/usb1/1-1/1-1:1.0/
> 0003:045E:00B9.0002/input/input16
> U: Uniq=
> H: Handlers=mouse1 event15
> B: PROP=0
> B: EV=17
> B: KEY=1f0000 0 0 0 0
> B: REL=1c3
> B: MSC=10
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: linux-image-4.15.0-20-generic 4.15.0-20.21
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CurrentDesktop: MATE
> Date: Mon Jun 11 07:57:56 2018
> InstallationDate: Installed on 2018-04-25 (46 days ago)
> InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64
> (20180404)
> SourcePackage: linux-signed
> UpgradeStatus: No upgrade log present (probably fresh install)
> ---
> ApportVersion: 2.20.9-0ubuntu7
> ...

[Kai-Heng Feng (kaihengfeng)]

Which protocol does the touchpad use, PS/2 or HID protocol?

[Reffman (ventruejusticar)]

How do you check that?

[Kai-Heng Feng (kaihengfeng)]

Well, in Windows' device manager.

[Reffman (ventruejusticar)]

Ah. Well, that's not going to happen then. Maybe Jeffrey has a dual boot installation?

[Jeffrey L Sussman (unspecified)]

Although I also have a "cheaper-end slimline laptop/netbook" with a non-working touchpad I don't think I'm having the same issue as you. I see that your device appears in your /proc/bus/input/devices list so I gather it was installed but not working. In my case, the touchpad isn't installed at all and does not appear in that list.

For my computer (a Direkt-Tek DTLAPY116-2), Ubuntu 18.04 detects my touchpad as a i2c_hid i2c-SYNA3602:00 but it is not installed because of an "unexpected HID descriptor." I'm still not sure but I think my issue is the one described here: https://bugzilla.redhat.com/show_bug.cgi?id=1526312

In case anyone still thinks it's relevant, Windows 10 reports the device in the Direkt-Tek with hardware ids of "ACPI\VEN_SYN\&DEV_3602" or "ACPI\SYNA3602" as being an I2C HID Device.

[Reffman (ventruejusticar)]

Maybe the problem is the same (Ubuntu kernel not detecting the touchpad correctly), but the touchpads are different models, and so ubuntu responds differently to them.

There are people who have had trouble with the Ubuntu kernel driver not resetting the touchpad on boot because of the touchpad behaving slightly differently than the driver expects. That may be the same issue I'm facing, but it's hard to know exactly.

[Kai-Heng Feng (kaihengfeng)]

Please try v4.18-rc5. It contains this commit:
commit ef6eaf27274c0351f7059163918f3795da13199c
Author: Jason Andryuk <email address hidden>
Date: Fri Jun 22 12:25:49 2018 -0400

    HID: i2c-hid: Fix "incomplete report" noise

[Reffman (ventruejusticar)]

Hey! Thanks for following this up.

reffman@alanah:~$ uname -r
4.18.0-041800rc5-generic
reffman@alanah:~$

Does not seem to make any difference. Touchpad and (integrated) buttons are completely dead.

I have investigated the touchpad a bit more (by disassembling the netbook), and it's marked HLC HK-9964 on the circuit board. Searching the net for more info on this particular touchpad has not yielded any results yet, probably a little-known chinese manufacturer.

[Reffman (ventruejusticar)]

Found something that might be interesting:

martin@alanah:~$ dmesg | grep SYNA
[ 8.244204] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, using dummy regulator
[ 8.253359] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/1)
[ 8.256078] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 8.258749] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/897)
[ 8.261463] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/8713)
[ 8.264126] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/261)
[ 8.266783] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/641)
[ 8.269405] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/38152)
[ 8.271991] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/23334)
[ 8.274594] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/20745)
[ 8.277208] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/641)
[ 8.279741] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/38146)
[ 8.282271] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/31302)
[ 8.284727] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/29952)
[ 8.287169] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/38145)
[ 8.289638] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/38145)
[ 8.292065] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/1472)
[ 8.294439] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/22281)
[ 8.296803] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/945)
[ 8.299145] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/945)
[ 8.301485] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (32/945)
[ 8.375591] input: SYNA3602:00 0911:5288 Mouse as /devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0004/input/input10
[ 8.375776] 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.0004/input/input11
[ 8.375894] hid-generic 0018:0911:5288.0004: input,hidraw3: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00
[ 9.261349] 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.0004/input/input21
[ 9.261532] hid-multitouch 0018:0911:5288.0004: input,hidraw3: I2C HID v1.00 Mouse [SYNA3602:00 0911:5288] on i2c-SYNA3602:00

[Kai-Heng Feng (kaihengfeng)]

Ah, I think this bug the same one as LP: #1728244, right?

[Reffman (ventruejusticar)]

Does not seem to be exactly the same. But do you suggest I try the same fix anyway?

[Kai-Heng Feng (kaihengfeng)]

Yes, please do.

[Reffman (ventruejusticar)]

linux-headers-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-headers-4.17.0-1_4.17.0-1.2~lp1728244_all.deb
linux-image-unsigned-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-modules-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb
linux-modules-4.17.0-1-generic_4.17.0-1.2~lp1728244_amd64.deb

Installed, and now the touchpad actually works. Thanks!

However, still same errors as in comment #32 at boot.

[Olaf (hein-jessen)]

Does anyone know when the patch in the official Ubuntu 18.04 kernel comes?

Thanks

Olaf