linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#561711: udev: Samsung R70/R71 keymap
Date: Tue, 05 Jan 2010 08:58:27 +0000	[thread overview]
Message-ID: <20100105085827.GA2403@piware.de> (raw)
In-Reply-To: <20091219195300.GA19984@bongo.bofh.it>

[-- Attachment #1: Type: text/plain, Size: 1955 bytes --]

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? 

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 where
> 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}=="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}=="*N130*", RUN+="keyboard-force-release.sh $devpath samsung-other"
> +ENV{DMI_VENDOR}=="[sS][aA][mM][sS][uU][nN][gG]*", ATTR{[dmi/id]product_name}=="*N130*|*SR70S/SR71S*", RUN+="keyboard-force-release.sh $devpath samsung-other"

This would be equivalent to doing

  echo 130,131,132,134,136,137,179,247,249 > /sys/devices/platform/i8042/serio0/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
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2010-01-05  8:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 19:53 Bug#561711: udev: Samsung R70/R71 keymap Marco d'Itri
2009-12-21  8:25 ` Martin Pitt
2010-01-04 16:18 ` Clemens Buchacher
2010-01-05  8:58 ` Martin Pitt [this message]
2010-01-05 15:51 ` Clemens Buchacher
2010-01-05 15:57 ` Martin Pitt

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=20100105085827.GA2403@piware.de \
    --to=martin.pitt@ubuntu.com \
    --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).