* Re: Bug#561711: udev: Samsung R70/R71 keymap
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
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Martin Pitt @ 2009-12-21 8:25 UTC (permalink / raw)
To: linux-hotplug
Hello Marco,
Marco d'Itri [2009-12-19 20:53 +0100]:
> Subject: Bug#561711: udev: Samsung R70/R71 keymap
> From: Clemens Buchacher <drizzd@aon.at>
Applied, thanks!
> Fn+F5 (blank screen) and Fn+F8 still do not generate events after
> this change, howver.
Seems worth exercising README.keymap.txt for those two then?
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Bug#561711: udev: Samsung R70/R71 keymap
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
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Clemens Buchacher @ 2010-01-04 16:18 UTC (permalink / raw)
To: linux-hotplug
Hi,
Please add me to Cc. I did not receive any notification about my bug report
and I'm responding now only because I found this in the list archives by
accident.
On Mon, Dec 21, 2009 at 09:25:40AM +0100, Martin Pitt wrote:
> > Fn+F5 (blank screen) and Fn+F8 still do not generate events after
> > this change, howver.
>
> Seems worth exercising README.keymap.txt for those two then?
/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? Maybe we should include a hint in README.keymap.txt.
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.
I suppose something like the following patch should fix the problem
permanently. Unfortunately, I was unable to test this, because the debian
package would not build with the new source code (rejected patches and other
issues), and after installing udev from git the kernel hangs at boot,
without leaving any traces in syslog.
Cheers,
Clemens
--o<--
Subject: [PATCH] keymap: add Samsung R70/R71 force-release rule
Signed-off-by: Clemens Buchacher <drizzd@aon.at>
---
| 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
--git a/extras/keymap/95-keyboard-force-release.rules b/extras/keymap/95-keyboard-force-release.rules
index 4d0a877..25bced6 100644
--- a/extras/keymap/95-keyboard-force-release.rules
+++ b/extras/keymap/95-keyboard-force-release.rules
@@ -19,6 +19,6 @@ DRIVER!="atkbd", GOTO="force_release_end"
ENV{DMI_VENDOR}="$attr{[dmi/id]sys_vendor}"
-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"
LABEL="force_release_end"
--
1.6.6.274.gdcca7
^ permalink raw reply related [flat|nested] 6+ messages in thread* Re: Bug#561711: udev: Samsung R70/R71 keymap
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
2010-01-05 15:51 ` Clemens Buchacher
2010-01-05 15:57 ` Martin Pitt
4 siblings, 0 replies; 6+ messages in thread
From: Martin Pitt @ 2010-01-05 8:58 UTC (permalink / raw)
To: linux-hotplug
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Bug#561711: udev: Samsung R70/R71 keymap
2009-12-19 19:53 Bug#561711: udev: Samsung R70/R71 keymap Marco d'Itri
` (2 preceding siblings ...)
2010-01-05 8:58 ` Martin Pitt
@ 2010-01-05 15:51 ` Clemens Buchacher
2010-01-05 15:57 ` Martin Pitt
4 siblings, 0 replies; 6+ messages in thread
From: Clemens Buchacher @ 2010-01-05 15:51 UTC (permalink / raw)
To: linux-hotplug
Hi Martin,
On Tue, Jan 05, 2010 at 09:58:27AM +0100, Martin Pitt wrote:
> 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?
Good point. Yes, that fixes all keys.
Cheers,
Clemens
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Bug#561711: udev: Samsung R70/R71 keymap
2009-12-19 19:53 Bug#561711: udev: Samsung R70/R71 keymap Marco d'Itri
` (3 preceding siblings ...)
2010-01-05 15:51 ` Clemens Buchacher
@ 2010-01-05 15:57 ` Martin Pitt
4 siblings, 0 replies; 6+ messages in thread
From: Martin Pitt @ 2010-01-05 15:57 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
Hello Clemens,
Clemens Buchacher [2010-01-05 16:51 +0100]:
> Good point. Yes, that fixes all keys.
Perfect, thanks for testing. I pushed your patch to udev.
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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread