From mboxrd@z Thu Jan  1 00:00:00 1970
From: Martin Pitt <martin.pitt@ubuntu.com>
Date: Tue, 05 Jan 2010 08:58:27 +0000
Subject: Re: Bug#561711: udev: Samsung R70/R71 keymap
Message-Id: <20100105085827.GA2403@piware.de>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="YZ5djTAD1cGYuMQK"
List-Id: <linux-hotplug.vger.kernel.org>
References: <20091219195300.GA19984@bongo.bofh.it>
In-Reply-To: <20091219195300.GA19984@bongo.bofh.it>
To: linux-hotplug@vger.kernel.org


--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Clemens,

Clemens Buchacher [2010-01-04 17:18 +0100]:
> /lib/udev/keymap correctly reported the keypress events, but xev did not.
> echo 166-245 > /sys/devices/platform/i8042/serio0/force_release finally
> fixed the problem. Is there any way to diagnose this issue without trial =
and
> error?=20

I'm not aware of one. However, on the Samsung NC10 where I tried this
once it helped to switch back and forth to a VT to unbreak X.org and
the stuck key.

> Maybe we should include a hint in README.keymap.txt.

Indeed, I added a note about force-release there now.

> It was a real pain to debug this, especially since I didn't even know whe=
re
> to look, and google returns tons of misleading bug reports concering hal.
> I'm afraid README.keymap.txt is the last place that people find. I have no
> idea what to do about it though.

In Ubuntu bug reports we point people to exercise
https://wiki.ubuntu.com/Hotkeys/Troubleshooting, which also points to
that README (if the problem is a missing keymap or force-release
quirk). I guess other distros need to do/are doing something similar.

> I suppose something like the following patch should fix the problem
> permanently.

> -ENV{DMI_VENDOR}=3D=3D"[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]produ=
ct_name}=3D=3D"*N130*", RUN+=3D"keyboard-force-release.sh $devpath samsung-=
other"
> +ENV{DMI_VENDOR}=3D=3D"[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]produ=
ct_name}=3D=3D"*N130*|*SR70S/SR71S*", RUN+=3D"keyboard-force-release.sh $de=
vpath samsung-other"

This would be equivalent to doing

  echo 130,131,132,134,136,137,179,247,249 > /sys/devices/platform/i8042/se=
rio0/force_release

(which is different to what you wrote originally). Does that work for
you for all keys? If not, we need a new force-release map for your
model.

Thanks,

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

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iEYEARECAAYFAktC/y8ACgkQDecnbV4Fd/IeKwCeOuo0XlfeLl3kl0cNYBpqAsGm
pjcAni0T0DxKfn49l8JsJlVn5XG1Kjb/
=rR2a
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--