[Asus K501UW] FTE1001 touchpad detected as mouse

Bug #1620811 reported by Egor on 2016-09-06
56
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Low
Unassigned

Bug Description

Following the bug reporting documentation here:
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

The touchpad on Asus K501UW laptop is detected as a mouse, so I can't access touchpad features such as two-finger scrolling or use two-finger tap as right mouse button. The touchpad is recognized in xinput-list as "FTE1001:00 0B05:0101".

UPD: I was unable to identify the touchpad manufacturer. I assumed it was FocalTech but all of their touchpads are PS/2, while mine is i2c. The only label it currently has is "asus touchpad".

The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64 with kernel 3.19, and there the touchpad does not work at all (does not function even as a mouse).

The bug is resemblant of #1372609.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: boot/vmlinuz-4.4.0-31-generic]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: e2 3605 F.... pulseaudio
CurrentDesktop: MATE
Date: Tue Sep 6 15:13:50 2016
HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
InstallationDate: Installed on 2016-09-05 (1 days ago)
InstallationMedia: Ubuntu-MATE 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 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 003: ID 0bda:57ed Realtek Semiconductor Corp.
 Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. K501UW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic N/A
 linux-firmware 1.157.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K501UW.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K501UW
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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K501UW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Egor (nevvy) wrote :
Egor (nevvy) wrote :
Egor (nevvy) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed

I have the same touchpad on my Asus Zenbook UX501 and I can confirm that it isn't recognized as such by the latest kernels installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7 nor 4.7.2
And the function key to enable or disable the touchpad is not recognized as well (tested with xev).

Egor, thank you for reporting this and helping make Ubuntu better.

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: bios-outdated-300
removed: focaltech touchpad
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete

David DIDIER, it will help immensely 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.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Egor (nevvy) wrote :

The problem persists in 4.8-rc5 (the latest currently available).

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.8-rc5
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Egor, 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.

summary: - Focaltech touchpad detected as mouse on Asus K501UW laptop
+ [Asus K501UW] Focaltech touchpad detected as mouse
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Egor (nevvy) wrote :

Christopher, thank you for the detailed instructions.

The letter in the mailing list: http://www.spinics.net/lists/linux-input/msg46766.html

Egor (nevvy) wrote :

UPD: I was probably wrong in claiming that this is a FocalTech touchpad. All of their touchpads are PS/2 (and allegedly fully supported starting with kernel 4.1), while my touchpad is i2c.

FTE pnpid stands for Frontline, according to http://www.uefi.org/sites/default/files/resources/PNPID_List.pdf, while Focaltech is FTS. However, Frontline support says they do not produce touchpads and never did.

In the end the only label the touchpad currently has is "asus touchpad".

description: updated
summary: - [Asus K501UW] Focaltech touchpad detected as mouse
+ [Asus K501UW] FTE1001 touchpad detected as mouse
Sergio Daniel (serguitus) wrote :

I think this link is usefull, I'm also experiencing this with K501UW
https://bugzilla.kernel.org/show_bug.cgi?id=120181

Egor (nevvy) wrote :

Beta version of the DKMS driver for FTE1001 touchpad (written by Brendan McGrath, Victor Vlasenko and Frederik Wenigwieser) is available here: https://github.com/vlasenko/hid-asus-fte-dkms

The driver seems to work well; everyone is welcome to try it out and report any issues to github.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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