[Asus UX303LN] F9 disable/enable Touchpad doesn't produce evdev event

[gratefulfrog]

The touchpad disable/enable hotkey (F9) does nothing. This makes it very hard to use the machine since the touchpad is constantly capturing random "mouse movements", making it impossible to enter text in the right place.

When I use the machine I have an external bluetooth mouse, and disable the touhpad in the settings menu, so I can type, but it would be much better to have the option to use the touchpad, and switch it on/off.

Also, if the bluetooth connection is lost, then I can do nothing and have to reboot!

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 219-7ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Jun 12 10:05:56 2015
InstallationDate: Installed on 2015-05-11 (31 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 064e:9700 Suyin Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303LNB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=eba1a0f5-161a-4061-99a4-b5598f7692c1 ro quiet splash vt.handoff=7
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LNB.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LNB
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.:bvrUX303LNB.203:bd12/10/2014:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX303LNB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Martin Pitt (pitti)]

In dmesg I see

[ 15.223526] asus_wmi: Unknown key cf pressed

which we indeed don't have in the "Asus" section of /lib/udev/hwdb.d/60-keyboard.hwdb. We have the scan code "6b" there instead, which presumably applies to older/other models.

 To ensure that this was actually the touchpad toggle key, and to also fix the airplane mode key, can you please install "evtest", run "sudo evtest", select the "Asus WMI" device, press the two broken keys, and copy&paste the output here? Please annotate the output with which line happened on what key press.

Thanks!

[gratefulfrog (gratefulfrog)]

Hi Martin!

Thanks for that reply! I am really happy that you are interested in my annoying problem.

I installed evtest and ran it on all the hotkeys. The atteched file shows the results. I have no idea how to interpret them...

I am available for more inupt and/or debugging actions.

Cheers,
Bob

[Martin Pitt (pitti)]

Thanks. So it seems some of the Fn keys appear through the "Asus WMI hotkeys" device, but others don't. The only other plausible device is "AT Translated Set 2 keyboard" (i. e. the standard keyboard which also sends the letters and numbers). Can you re-run "sudo evtest", select that one, and repeat this exercise for the non-working Fn keys such as F1/F2?

[gratefulfrog (gratefulfrog)]

I ran that device, and the results are slightly different:
F1,F2,F5,F6: no change, no output

F3,F4,F7,F9 : no output, did produce output in previous Asus device test.

F8,F10,F11,F12: now produces output, did not produce output in previous Asus device test

 The results are attached.

Should we bump the status of this bug to confirmed or under-work?

Cheers,
Bob

[Martin Pitt (pitti)]

> F1,F2,F5,F6: no change, no output

OK, that makes it a kernel bug then, reassigning. The driver needs to send evdev events for these keys.

> F3,F4,F7,F9 : no output, did produce output in previous Asus device test.

Yes, that's expected. They are appearing on the WMI device, not the AT keyboard device.

> F8,F10,F11,F12: now produces output, did not produce output in previous Asus device test

OK. But these keys already work.

> The results are attached.

No, they aren't :-( But at this point udev's scope ends anyway, this is a kernel driver bug now.

[Brad Figg (brad-figg)]

This change was made by a bot.

[gratefulfrog (gratefulfrog)]

sorry, I'm trying to attach the 2nd results...

[gratefulfrog (gratefulfrog)]

Hello,

Thank you for your quick reply.

I followed your advice and updated my bios to the most recent one available at the asus website (206).

There is absolutely no change in the hotkey behavior.

I ran the commands:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
UX303LNB.206
01/22/2015

Please let me know what can be done, now.

Cheers,
Bob

[penalvch (penalvch)]

gratefulfrog, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test 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 bug 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 XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, 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.

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[gratefulfrog (gratefulfrog)]

Hi,

Again, thanks for your quick reply.

I tested with the most recent kernel:

linux-image-4.1.0-040100rc8-generic_4.1.0-040100rc8.201506150335_amd64

And the bug remains, exactly as my present kernel.

I am available for further tests as needed.

Thanks for this great support!
Bob

[penalvch (penalvch)]

gratefulfrog, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-input) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.

[gratefulfrog (gratefulfrog)]

Hello,

Thank you for your help.

I sent the email following the instructions verbatim.

However, I do not understand how to do this:

"Please provide a direct URL to your e-mail to the mailing list once you
have made it so that it may be tracked via http://vger.kernel.org/vger-
lists.html . It can take a day for the new e-mail to show up in the
respective archive."

Sorry to have to ask you..
Cheers,
Bob

On Mon, Jun 15, 2015 at 1:12 PM, Christopher M. Penalver
<email address hidden> wrote:
> gratefulfrog, the issue you are reporting is an upstream one. Could you
> please report this problem to the appropriate mailing list (linux-input)
> by following the instructions verbatim at
> https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
>
> Please provide a direct URL to your e-mail to the mailing list once you
> have made it so that it may be tracked via http://vger.kernel.org/vger-
> lists.html . It can take a day for the new e-mail to show up in the
> respective archive.
>
> Thank you for your understanding.
>
> ** Tags removed: kernel-bug-exists-upstream-4.1.0-040100rc8
> ** Tags added: kernel-bug-exists-upstream-4.1-rc8
>
> ** Summary changed:
>
> - [Asus UX303LN] several hotkeys don't produce evdev event
> + [Asus UX303LN] F9 disable/enable Touchpad doesn't produce evdev event
>
> ** Description changed:
>
> - Running Xubuntu on an Asus UX303LN laptop.
> -
> The touchpad disable/enable hotkey (F9) does nothing. This makes it
> very hard to use the machine since the touchpad is constantly capturing
> random "mouse movements", making it impossible to enter text in the
> right place.
>
> When I use the machine I have an external bluetooth mouse, and disable
> the touhpad in the settings menu, so I can type, but it would be much
> better to have the option to use the touchpad, and switch it on/off.
>
> Also, if the bluetooth connection is lost, then I can do nothing and
> have to reboot!
> -
> - I have no idea how to debug this but would be happy to help.
> -
> - Another hotkey that does not work is F2 "airplane mode". This one is of
> - no importance to me, but I mention it for completeness.
> -
> - I am really hoping for a fix!
> -
> - I am a Ubuntu beta-tester from long ago, and helped on the 1st 64bit
> - version!
> -
> - Let me know, please!,
> - Cheers,
> - Bob
> -
> - I have attached all the files specified on the hotkey bug reporting
> - page. I put them in an archive since that seems to be the only option
> - for attaching multiple files?
> -
> - udevadm info --export-db > udev-db.txt
> - dmesg > dmesg.log
> - sudo lsinput > lsinput.log
> - xkbcomp -xkb :0 - > xkbcomp.txt
> - setxkbmap -print > xkbmap.txt
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: udev 219-7ubuntu5
> ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
> Uname: Linux 3.19.0-18-generic x86_64
> ApportVersion: 2.17.2-0ubuntu1.1
> Architecture: amd64
> CurrentDesktop: XFCE
> Date: Fri Jun 12 10:05:56 2015
> InstallationDate: Installed on 2015-05-11 (31 days ago)
> InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
> Lsusb:
> - Bus 002 Device 001: ID 1d6b:0003 Linux Foundat...