[Asus ZenBook UX501VW] Touchpad doesn't have multitouch support

[David DIDIER]

The touchpad isn't recognized as such so there is no multitouch support. xinput displays "FTE1001:00 0B05:0101" instead.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.7.3-040703-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016
 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Sep 9 22:27:19 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
InstallationDate: Installed on 2016-06-01 (100 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
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 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
 Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. N501VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.3-040703-generic root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N501VW
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.2
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Sep 9 22:26:55 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 [drm] Failed to open DRM device for (null): -22
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 12876
 vendor SDC
xserver.version: 2:1.18.3-1ubuntu2.3

[penalvch (penalvch)]

David DIDIER, 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.

[David DIDIER (ddidier)]

Does not work with v4.8-rc6

[penalvch (penalvch)]

David DIDIER, 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.

[David DIDIER (ddidier)]

I gathered all the required informations but I can't subscribe to the list:
553 5.7.1 Hello [98.138.121.68], for your MAIL FROM address <email address hidden> policy analysis reported: Your address is not liked source for email

[penalvch (penalvch)]

David DIDIER, that message would indicate that you would want to switch email domains (ex. gmail, etc.).

[David DIDIER (ddidier)]

Yes but I have only one other account with another provider and that's the one I don't want to put on the internet for everybody to see... why are yahoo domain rejected??? that's insane, and the whole process is just way too complicated even for tech savvy people. so my only option is to open another gmail account just for this?

[penalvch (penalvch)]

David DIDIER, to advise, I don't maintain those resources. I'm only providing a suggestion to WORKAROUND the issue, and move this forward. This is as you like.

[David DIDIER (ddidier)]

Christopher, I'm sorry, I didn't mean to upset you with my rant that wasn't directed at you. But that was really annoying. So I finally sent it successfully to the linux-input mailing list. After one week without answer, I retried, and after another week, I directly emailed Dmitry Torokhov.

Who informed me that the kernel list is to submit a patch or information about recent kernel regression" and that I simply have some hardware that is currently unsupported by the kernel. Then I can try to contact the manufacturer to see if they will be willing to release a driver or I can try to figure out the device and protocol myself. And he gave me a pointer to this issue : https://bugzilla.kernel.org/show_bug.cgi?id=120181.

As the manufacturer is still unclear and I'm not able to reverse engineer the protocol, that settle it I guess... So for anyone willing to buy a ZenBook ux501 and use it with Linux: just don't!

[penalvch (penalvch)]

David DIDIER, no problem on my end. Sometimes you just have to rant it out to move forward. :D

All joking aside, yahoo has been compromised for years, so it may not be a bad idea to move off the platform going forward to better preserve your security.

Despite this, while you didn't get a great outcome in that there is no support, and one would have to wait until a developer works on it and simultaneously nag the vendor to do it, at least you got the scoop on your hardware.

Unfortunately, I'm not able to help further given the above, other than reinforce what was advised by Dmitry.