Touchpad not working on Asus Zenbook UX305CA-FC022T

[Pelle van der Scheer]

New install of Ubuntu 15.10

Touchpad is not working, using usb mouse.

Tested mainstream kernel upto 4.4-rc1, still not working.

Asus Zenbook UX305CA-FC022T

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-18-generic 4.2.0-18.22
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pelle 1532 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Nov 21 16:02:10 2015
InstallationDate: Installed on 2015-11-20 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUSTeK COMPUTER INC. UX305CA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed root=UUID=199cbad3-e17e-4549-b0ba-8eedbbbc3795 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.149.2
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305CA.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305CA
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.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305CA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[penalvch (penalvch)]

Pelle van der Scheer, thank you for reporting this and helping make Ubuntu better.

Could you please boot into the latest mainline kernel, and then post your dmesg as an attachment (not compressed/tarred)?

[Pelle van der Scheer (pellesimon)]

here you go

uname -a
Linux tree 4.4.0-rc1-phoronix #3 SMP Wed Nov 18 10:31:11 EST 2015 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Pelle van der Scheer, could you please advise to where you downloaded the 4.4-rc1 kernel from?

[Pelle van der Scheer (pellesimon)]

I got it from here: https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.4-rc1-Ubuntu-Spin

(The builds at ubuntu kernel are failing)

[penalvch (penalvch)]

Pelle van der Scheer, could you please test http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/ and advise to the results?

[Pelle van der Scheer (pellesimon)]

I had tested that kernel as well, the touchpad doesnt work.

$ uname -a
Linux tree 4.3.0-040300-generic #201511020949 SMP Mon Nov 2 14:50:44 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

see dmesg attachment

[penalvch (penalvch)]

Pelle van der Scheer, 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 venue (Dmitry Torokhov CC linux-input)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

[Pelle van der Scheer (pellesimon)]

Tested on v4.4-rc2+cod1-wily, still no luck

[Pelle van der Scheer (pellesimon)]

Still not working on 4.4.0-040400rc4-generic

[Pelle van der Scheer (pellesimon)]

upstream bug report:

https://bugzilla.kernel.org/show_bug.cgi?id=108581

[Pelle van der Scheer (pellesimon)]

Hello Christopher,

I think it is the same problem (see my dmesg, the i2c error messages are the samen)

As you instructed, I have posted a message on the mailing list on 22-november (http://www.spinics.net/lists/linux-input/msg42240.html) but have had no response.

A similar issue has been reported on the mailing list as well (http://www.spinics.net/lists/linux-input/msg42217.html)

According to your instructions, after a week if there is no response from the mailing list a bug report should be placed on https://bugzilla.kernel.org/index.cgi, as there is already one, I do not see a point in posting another one.

[Pelle van der Scheer (pellesimon)]

Chrisopher, as per your instructions I have reported a bug upstream: https://bugzilla.kernel.org/show_bug.cgi?id=109211

[Pelle van der Scheer (pellesimon)]

still not working on rc5

[Griffin (griffinciluffo)]

I am also on rc5 and it still does not work. Ive search and tried many different solutions on the internet but none have worked. I cant seem to much related to ELAN1000. Is there anything we try besides waiting for a new kernel?

[Pelle van der Scheer (pellesimon)]

not working on rc6

[Pelle van der Scheer (pellesimon)]

I have the touchpad working on Fedora Rawhide (development version), it seems related to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1275718

The fix will come in mainline kernel 4.5

[Kulcsár Gergő (kulcsar-gergo)]

I've got an Asus e403SA notebook with the same elan touchpad. My experiences are different from the others. I'm on Ubuntu 15.10 with stock 4.2.x kernel. The touchpad works as a ps/2 mouse without multitouch and recognised as ELAN1000:xxx. With 4.3 or 4.4 kernel everything works fine (recognision, multitouch) but after a while (minutes, sometimes hours) the touchpad freezes.

In the syslog appears these:

Jan 5 20:55:27 darkslide-notebook kernel: [ 1531.867948] i2c_designware 808622C
1:03: Unknown Synopsys component type: 0x00000000
Jan 5 20:55:27 darkslide-notebook kernel: [ 1531.893399] i2c_designware 808622C
1:03: timeout in enabling adapter
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892319] i2c_designware 808622C
1:03: controller timed out
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892334] i2c_designware 808622C
1:03: Unknown Synopsys component type: 0x00000000
Jan 5 20:55:28 darkslide-notebook kernel: [ 1532.892343] elan_i2c i2c-ELAN1000:00: failed to read report data: -110

Do I need to submit a new ticket or is my problem is because of the same driver bug?

[penalvch (penalvch)]

Kulcsár Gergő, it will help to at least be able to track you hardware if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.