Asus K556UB-XX115D Elan Touchpad works only AFTER suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
After login, the touchpad is detected and shown in xinput --list and in /proc/bus/
The really weird part is that the touchpad STARTS working after waking from suspend.
The touchpad works flawlessly in Windows 10 (didn't work in Windows 7), and external mice also work in both Ubuntu and Windows. The problem happens in Ubuntu 16.04, Ubuntu 14.04 didn't detect the touchpad at all in xinput and /proc/bus/
I have tried several GRUB command line parameters that I've seen recommended on the internet, such as i8042.reset=1 i8042.nomux=1 i8042.noloop=1 psmouse.proto=bare, but none of them changed anything the touchpad didn't work when the system boots up, but it starts working after suspend.
I've attached the outputs from xinput --list, /proc/bus/
The outputs don't change when I suspend and wake up the computer, the list of modules in lsmod also doesn't change.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-
ProcVersionSign
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Aug 12 19:44:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
InstallationDate: Installed on 2016-08-10 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 005: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X556UB
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xserver-
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/28/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X556UB.405
dmi.board.
dmi.board.name: X556UB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: X556UB
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Fri Aug 12 19:41:06 2016
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 20049
vendor SDC
xserver.version: 2:1.18.3-1ubuntu2.2
Никола Павловић, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http:// kernel. ubuntu. com/~kernel- ppa/mainline/ ?C=N;O= D ? Please keep in mind the following: /wiki.ubuntu. com/Kernel/ MainlineBuilds .
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https:/
If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.
If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: fixed-upstream fixed-upstream- X.Y-rcZ
kernel-
kernel-
Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.
If the mainline kernel does not fix the issue, please add the following tags: bug-exists- upstream bug-exists- upstream- X.Y-rcZ
kernel-
kernel-
Please note, an error to install the kernel does not fit the criteria of kernel- bug-exists- upstream.
Also, you don't need to apport-collect further unless specifically requested to do so.
It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.
Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.
Thank you for your help.