Asus K556UB-XX115D Elan Touchpad works only AFTER suspend

Bug #1612762 reported by Никола Павловић
8
This bug affects 1 person
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/input/devices. But any movements or clicks are not detected.

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/input/devices.

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/input/devices and synclient.
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-xorg-input-synaptics 1.8.2-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
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=/vmlinuz-4.4.0-34-generic.efi.signed root=UUID=a818d628-6917-48f8-8d23-89d267d0925a ro quiet splash pci=nomsi vt.handoff=7
SourcePackage: xserver-xorg-input-synaptics
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.asset.tag: ATN12345678901234567
dmi.board.name: X556UB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X556UB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
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

Revision history for this message
Никола Павловић (nikola825) wrote :
Revision history for this message
Никола Павловић (nikola825) wrote :
Revision history for this message
Никола Павловић (nikola825) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Никола Павловић, 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:
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://wiki.ubuntu.com/Kernel/MainlineBuilds .

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:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

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:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

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.

tags: added: latest-bios-405
Changed in xserver-xorg-input-synaptics (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Никола Павловић (nikola825) wrote :

I've tested the 4.8-rc5 mainline kernel, it boots successfully, but the problem is still there - touchpad is not working after boot but starts working after suspend. The outputs from xinput and synclient are the same.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.8-rc5
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Никола Павловић, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Dmitry Torokhov CC linux-input)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.

tags: added: trusty
affects: xserver-xorg-input-synaptics (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
Revision history for this message
jakub (sencak) wrote :

Hello, I had Ubuntu 16.06 installed on the same laptop ASUS X556UB and everything worked very well. It was a clean installation. Unfortunatelly I reinstalled it and now I have dualboot Debian 8 Jesie with Windows 10 on the same HDD. On Win there is no problem verything works normally.

On Debian I have very similiar problem with touchpad. It does not work at all. Not even after suspend because laptop will not start after suspend so I deactivated it (I had this problem on Ubuntu, too).

Plus there is also nothing like brightness adjustment, but it is probably some missing driver I am not able to find.

I am sorry if I interupted, this is the first time I wrote to discusion.

Revision history for this message
Никола Павловић (nikola825) wrote : Re: [Bug 1612762] Re: Asus K556UB-XX115D Elan Touchpad works only AFTER suspend
Download full text (5.3 KiB)

So, the bug seems to be fixed in 16.06. Thanks for the information.
On Oct 30, 2016 16:44, "jakub" <email address hidden> wrote:

> Hello, I had Ubuntu 16.06 installed on the same laptop ASUS X556UB and
> everything worked very well. It was a clean installation. Unfortunatelly
> I reinstalled it and now I have dualboot Debian 8 Jesie with Windows 10
> on the same HDD. On Win there is no problem verything works normally.
>
> On Debian I have very similiar problem with touchpad. It does not work
> at all. Not even after suspend because laptop will not start after
> suspend so I deactivated it (I had this problem on Ubuntu, too).
>
> Plus there is also nothing like brightness adjustment, but it is
> probably some missing driver I am not able to find.
>
> I am sorry if I interupted, this is the first time I wrote to discusion.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1612762
>
> Title:
> Asus K556UB-XX115D Elan Touchpad works only AFTER suspend
>
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
> After login, the touchpad is detected and shown in xinput --list and
> in /proc/bus/input/devices. But any movements or clicks are not
> detected.
>
> 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/input/devices.
>
> 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/input/devices
> and synclient.
> 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-xorg-input-synaptics 1.8.2-1ubuntu3
> ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
> 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...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Никола Павловић, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1612762/comments/8 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.