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:
signature.asc
Description: Digital signature
