Elantech Touchpad detected intermittently, not detected when these system logs were taken

[Andrew F in Australia]

Hi,

The Elantech Touchpad appears to be buggy in linux/Ubuntu through messages.

Today, the touchpad was not detected on startup and I am using an external mouse to drive the cursor.
ubuntu-bug linux output attached.

For comparison, when the touchpad was working, the same system logs are recorded in bug #1644919.

Have tried both the mainline and stable kernel.

These logs are on the stable kernel, same as those in bug 1644919

Expected behaviour. Start computer up, cursor responds to touchpad command
Current behaviour. Start computer up, cursor not visible until external mouse plugged in and moved. Cursor responds normally to external mouse, issue with touchpad driver.

xinput shows no touchpad detected

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-51-generic 4.4.0-51.72
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: horace 1893 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Dec 4 07:58:01 2016
HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e
InstallationDate: Installed on 2016-11-13 (20 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: GIGABYTE P57
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic.efi.signed root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-51-generic N/A
 linux-backports-modules-4.4.0-51-generic N/A
 linux-firmware 1.157.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FB0B
dmi.board.asset.tag: Default string
dmi.board.name: P57
dmi.board.vendor: GIGABYTE
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.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.name: P57
dmi.product.version: Default string
dmi.sys.vendor: GIGABYTE

[Brad Figg (brad-figg)]

This change was made by a bot.

[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.9 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.9-rc8

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]