Bug 65375 - Missing Asus keymap rules in udev
Summary: Missing Asus keymap rules in udev
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-04 20:27 UTC by P. Neidhardt
Modified: 2013-12-16 22:25 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
udev keymap rules for Asus (1.10 KB, text/plain)
2013-06-04 20:27 UTC, P. Neidhardt
Details

Description P. Neidhardt 2013-06-04 20:27:42 UTC
Created attachment 80308 [details]
udev keymap rules for Asus

With Linux 3.9 (commit a935eaecef2b209ad661dadabb4e32b7c9a9b924), the Asus
keyboard driver has changed to be more compliant to the symbol
signification. This has led to some issues with udev. In particular, the
XF86TouchpadToggle (a Fn key) does not work anymore on y Asus X52J. As confirmed
by the kernel developper who did this commit, this is not a kernel regression,
udev is to blame here because of missing udev rules in 95-keymap.rules.

So basically all I did was adding

 ENV{DMI_VENDOR}=="ASUS*", KERNELS=="input*", ATTRS{name}=="Asus Laptop extra buttons", RUN+="keymap $name 0x6B f21"

to the file. I found another similar patch which does not seem to have been ever
submitted/merged:

  https://launchpadlibrarian.net/73337842/95-keymap.rules.patch

Find enclosed the patch containing both the launchpad patch and mine into one
file.
Comment 1 Zbigniew Jedrzejewski-Szmek 2013-06-04 21:47:29 UTC
Applied in http://cgit.freedesktop.org/systemd/systemd/commit/?id=f3dbb13.
Comment 2 nucleo 2013-12-16 22:25:02 UTC
XF86TouchpadToggle event (Fn+F3) missing on Asus EEee PC X101CH after switching from udev keymaps to hwdb. 
Looks like this switching is the only reason why it don't work in Fedora 20 (systemd-208), but works fine in Fedora 19 (systemd-204).


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.