From: Tobias Frilling <tobias@frilling-online.de>
To: linux-hotplug@vger.kernel.org
Subject: Udev loads wrong keymap
Date: Sun, 22 Jan 2012 20:04:03 +0000 [thread overview]
Message-ID: <4F1C6BB3.9010904@frilling-online.de> (raw)
In-Reply-To: <4F1C6B98.5040005@frilling-online.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Since the upgrade from 175 to 178 udev does not load the correct keymap
file on my Samsung netbook.
Keys like BrightnessUp/Down and a bunch of others do not work.
The correct keymap is samsung-other and it should be loaded from
95-keymap.rules, line 141:
ENV{DMI_VENDOR}="[sS][aA][mM][sS][uU][nN][gG]*", RUN+="keymap $name
samsung-other"
$ cat /sys/class/dmi/id/{sys_vendor,product_name}
SAMSUNG ELECTRONICS CO., LTD.
N145P/N250P/N260P
Manual loading of the keymap (# /lib/udev/keymap -i input/event0
samsung-other) fixes the issue.
Other users reported similar bugs, see
https://bugs.archlinux.org/task/28049
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJPHGutAAoJEEDINPnaM7l+TUwH/3ugfyTQaqddHfNjE7K5+Yr0
4F2ZwORtGvdXGKtTWZNIj1lMuWxMpr4oNID9XScGYnIeaJnwokeeiIXpogZgTea3
EufWGpB9TTLKMHIUqlqmkuM4Thl+b8z5++xyf6O85mvDwfiwq9RSOx7XtXRf6cgq
TrZ6pUWdLBcvsvcr8w6K1p7zaF86L9ZogAGxTDRR9owaly+61G5AgEhQ44HxUsK2
satti7kJX8NWyyBm7Uq8tLnHTAoOidZrr918WjJdl7JCHlc5aiT3T54f+GKZWcwm
y1ssI79U0+WZy8qGAN4P0MjcPr/QBzH7MbRgScbbz60kaj5CyP/vEQtB9pvsCHA=9ZTt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-01-22 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 20:03 Udev loads wrong keymap Tobias Frilling
2012-01-22 20:04 ` Tobias Frilling [this message]
2012-01-22 20:08 ` Kay Sievers
2012-01-22 20:37 ` Kay Sievers
2012-01-22 20:49 ` Kay Sievers
2012-01-23 4:33 ` Kay Sievers
2012-01-24 13:28 ` ajaxas
2012-01-25 9:19 ` Martin Pitt
2012-01-25 13:51 ` ajaxas
2012-01-25 14:18 ` Robby Workman
2012-01-25 15:53 ` ajaxas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F1C6BB3.9010904@frilling-online.de \
--to=tobias@frilling-online.de \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).