From mboxrd@z Thu Jan  1 00:00:00 1970
From: Martin Pitt <martin.pitt@ubuntu.com>
Date: Wed, 25 Jan 2012 09:19:55 +0000
Subject: Re: Udev loads wrong keymap
Message-Id: <20120125091955.GA2930@piware.de>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="8t9RHnE3ZwKMSgU+"
List-Id: <linux-hotplug.vger.kernel.org>
References: <4F1C6B98.5040005@frilling-online.de>
In-Reply-To: <4F1C6B98.5040005@frilling-online.de>
To: linux-hotplug@vger.kernel.org


--8t9RHnE3ZwKMSgU+
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Ajaxas,

ajaxas [2012-01-24 20:28 +0700]:
> At least a week earlier I had some of Sony Vaio Keys working: Volume
> control (Fn+F2: mute, Fn+F3: down, Fn+F4: up) and Brightness control
> (Fn+F5: down, Fn+F6: up). Other Vaio Keys (Fn+F1: touchpad switch,
> Fn+F7: switch video mode, Fn+F12: suspend) never worked.
> At some point (I think after updating to udev-177-1) Brightness
> control keys stopped working. Volume control keys still work.
> Brightness control still works directly via acpi.

Note that between udev 175 and 179 the Sony rules and keymaps did not
change at all. The only bug I am aware of is the one you already
pointed out in your forum post, and you said that the fix [1] did not
help.

> I blame it on udev, however, downgrading to udev-175 doesn't solve the
> problem.

OK, this is consistent with what you and I wrote above.

On your forum post you say that keymap -i actually shows the right key
codes (brightnessup/brightnessdown) when you press the corresponding
keys. Can you confirm that this is still true with the latest udev?
Once that's working, all the udev rules, keymaps, etc. have already
been exercised.

Could it be that you upgraded something else in e. g. GNOME which now
fails to act on the key events? You could try "xev" to see whether you
get proper X11 events for these keys, and try a fresh user account to
ensure it's not some changed configuration of your's.

> However, my Volume control keys seem to be mapped to input/event0
> (keyboard itself):
>=20
> > [root@r2d2 ajaxas]# /lib/udev/keynap -i input/event0

Funny "keynap" typo :)

> > scan code: 0xA0 =A0 key code: mute
> > scan code: 0xAE =A0 key code: volumedown
> > scan code: 0xB0 =A0 key code: volumeup

It's a bit unexpected indeed, I had expected these to also come out of
the "Sony Vaio Module"; does anythign happen on keymap -i input/event1
if you press these keys?

> and these scan codes correspond not to my keymap (0x06, 0x07, 0x08),
> but to /lib/udev/keymaps/force-release/common-volume-keys.

This is a sheer coincidence. common-volume-keys is not applied on
Sony, so that's not relevant here.

> If I change my keymap file (0x09 -> 0x10, 0x0A -> 0x11) and load
> keymap manually, nothing changes. And when I reboot with this changed
> keymap, udev reports this for my Brightness control keys:
>=20
> > [root@r2d2 ajaxas]# /lib/udev/keymap -i input/event1
> > scan code: 0x10 =A0 key code: fn_f5
> > scan code: 0x11 =A0 key code: fn_f6

This just double-confirms that the current keymap is correct and gets
loaded properly.

> Again, nothing works, and keys are not reported as Brightness control
> keys anymore. Here's where I'm lost.

Reported to where? keymap -i certainly seems to get them correct. Are
they lost in xev?

Did you happen to upgrade X.org recently? 1.12 introduces a completely
new input stack, and some distros might already use that (I know
Ubuntu's X.org 1.11 packages have that backported for the multi-touch
stuff, for example).

Thanks,

Martin

[1] http://git.kernel.org/?p=3Dlinux/hotplug/udev.git;a=3Dcommitdiff;h=3De6=
05cf7782fdf1dc2e13b95e906e731d61e6cf12

--=20
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

--8t9RHnE3ZwKMSgU+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJPH8k1AAoJEPmIJawmtHufNZwQAIo+xEzw+jVe1Yjy2ldohmrj
0zjo9D1um5TXLQV6RZRWX1lgUWpK+RNd5QSYE4Yh0nfdMFdwbe/0013tHj6TrsJd
p8Avhf4McaNjsBre6rzoSTwK1v3mASA711IsCS7qQIVvmAIjwfUcIsaw2ZGt4x8q
5s0Pv2CL1SjlxYQP72ozxXce0P5BgDXQa/L5hbE87vo5wnx3HhOBUZUvDTWRtG2x
p3VevjW4bJ3CyaGB8vBHj7//Q/xWNkTjI6buJEu4ZlQVE8IgON+AI+gmq6xz4I1b
wUIlOXHL3hZHw444EbnWJUlemKDoYlDRZIrXxpNlhtGS09yDHIOC09eT+eYM6N4+
iA/v7r1bu+m8A9xiIRpgNSrgmXEg48lWZZdHNIjx0prSmh3ONudbl04pY74v2tzg
QImnxEIELnDebUVntfACmuHmFt0t5l4NmAiNjp1kqElO/Wmu9wfBJfgRakoZuQsg
3u5FvuOscJcxsXwBVykJJcBmSxFFlXHlfmiPxkfqQgyrNm9ODoLiZws33zkHYbWG
bN2Zchokka9CvHFtmDidodA5ybPQU+qVFV5q42oDXR7VaNRTe2Y0UmQh+1K5aFLA
NsskjYYGFSghyAEISEttJZ2imSlMYQANBdmhz1MCK6s1LUN2C72qGFJElGH5hn9U
YUUelJ1EpflsM5iXiUKN
=NxnD
-----END PGP SIGNATURE-----

--8t9RHnE3ZwKMSgU+--