Red Hat Bugzilla – Bug 450326
hal/ Fixing non-mapped vendor buttons
Last modified: 2010-03-30 04:32:36 EDT
Description of problem:
The Dell Latitude has a hotkey Fn+F1 to suspend. This doesn't work.
Steps to Reproduce:
On Text Console you see the following messages:
atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
Machine should go to suspend mode
I have backported keyboard quirk from upstream, patch attached. Additionally,
user would need to induce fdi for dell keyboard mapping.
Created attachment 308549 [details]
update spec for BuildRequire
Created attachment 308550 [details]
patch hal to support keymapping
this patch updates hal to support key mapping.
add originating_device property to input device to enable matching keyboard
mapping rules against atkbd.
installs hal-setup-keymap which maps keymapping.
finally, install rules for handling keymapping.
Nice one Ritesh, I was going to do this tomorrow! I'm going to pull all the
30-keymap-* files into hal also, as hopefully the thinkpad bits can be pulled in
+1 from me.
I was wondering if you could provide x86_64 hal rpms similar to i386 ones you
provided on your people page. Thanks if you can. In case you were wondering,
I would like to test them on a laptop that only supports x86_64.
_TEST_ packages uploaded to http://people.redhat.com/rkhadgar/work/bz45036/
This looks like it would affect *many* if not all laptops. Is this a new feature (that laptop keyboards work)? Is there a specific set of laptops that the keymapping was broken and is now fixed by this change?
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.