| 1 |
Hi! I just got my multimedia keys up and running on my inspiron 2200 |
| 2 |
keyboard by following this guide and using xbindkeys. |
| 3 |
http://gentoo-wiki.com/HOWTO_Use_Multimedia_Keys |
| 4 |
|
| 5 |
I'm using a dell inspiron 2200 and I got my volume up and down keys |
| 6 |
recognized using the ff xbindkeys rules. Pretty cool, actually. |
| 7 |
"amixer sset Master 1+" |
| 8 |
XF86AudioRaiseVolume |
| 9 |
"amixer sset Master 1-" |
| 10 |
XF86AudioLowerVolume |
| 11 |
"amixer sset Master toggle" |
| 12 |
XF86AudioMute |
| 13 |
|
| 14 |
my keyboard looks like this |
| 15 |
http://www.laptopreparatie.nl/webshop/catalog/images/i1200_keyboard.jpg |
| 16 |
http://stephan-i.com/osc/images/D8883KB.jpg |
| 17 |
|
| 18 |
I'm basically not having any trouble with the volume keys. However, there |
| 19 |
are also keys for |
| 20 |
fn+eject |
| 21 |
fn+crt/lcd |
| 22 |
fn+wireless |
| 23 |
fn+hibernate |
| 24 |
fn+standy |
| 25 |
|
| 26 |
that don't seem to work |
| 27 |
firstly, I turn on my xev and press them. I get no response. watching my |
| 28 |
kernel messages, I get to see their keycodes in a message like this: |
| 29 |
|
| 30 |
Mar 7 04:00:31 titusx [11428.510000] atkbd.c: Unknown key pressed |
| 31 |
(translated s |
| 32 |
et 2, code 0x85 on isa0060/serio0). |
| 33 |
Mar 7 04:00:31 titusx [11428.510000] atkbd.c: Use 'setkeycodes e005 |
| 34 |
<keycode>' |
| 35 |
to make it known. |
| 36 |
|
| 37 |
I tracked down all the keycodes and was able to make a script of keycodes in |
| 38 |
my /etc/conf.d/local.start |
| 39 |
|
| 40 |
setkeycodes e005 133 |
| 41 |
setkeycodes e006 134 |
| 42 |
setkeycodes e007 135 |
| 43 |
setkeycodes e008 136 |
| 44 |
setkeycodes e009 137 |
| 45 |
setkeycodes e00a 138 |
| 46 |
setkeycodes e00b 139 |
| 47 |
|
| 48 |
(except for fn+standby, which neither gives a keycode in xev nor is detected |
| 49 |
by the kernel in its logs) |
| 50 |
|
| 51 |
I test these out in xev. But I get funky behavior. |
| 52 |
1) the keycode that appears does not match the keycode I gave |
| 53 |
the fn+eject key, for example, I think is e00b. So it should be giving me |
| 54 |
keycode 139. However, xev detects keycode 188. |
| 55 |
|
| 56 |
2) xev reports the key repeatedly being pressed and released endlessly even |
| 57 |
after I press it only once. |
| 58 |
|
| 59 |
KeyPress event, serial 29, synthetic NO, window 0x3200001, |
| 60 |
root 0x5d, subw 0x0, time 2603599, (589,435), root:(599,532), |
| 61 |
state 0x0, keycode 192 (keysym 0x0, NoSymbol), same_screen YES, |
| 62 |
XLookupString gives 0 bytes: |
| 63 |
XmbLookupString gives 0 bytes: |
| 64 |
XFilterEvent returns: False |
| 65 |
|
| 66 |
KeyRelease event, serial 29, synthetic NO, window 0x3200001, |
| 67 |
root 0x5d, subw 0x0, time 2603634, (589,435), root:(599,532), |
| 68 |
state 0x0, keycode 192 (keysym 0x0, NoSymbol), same_screen YES, |
| 69 |
XLookupString gives 0 bytes: |
| 70 |
XFilterEvent returns: False |
| 71 |
|
| 72 |
KeyPress event, serial 29, synthetic NO, window 0x3200001, |
| 73 |
root 0x5d, subw 0x0, time 2603634, (589,435), root:(599,532), |
| 74 |
state 0x0, keycode 192 (keysym 0x0, NoSymbol), same_screen YES, |
| 75 |
XLookupString gives 0 bytes: |
| 76 |
XmbLookupString gives 0 bytes: |
| 77 |
XFilterEvent returns: False |
| 78 |
|
| 79 |
on and on and on forever, until I click on another window to make it lose |
| 80 |
focus or I press another key. |
| 81 |
|
| 82 |
Assigning an action to the key confirms my suspicion. I try setting |
| 83 |
"eject" |
| 84 |
XF86Eject |
| 85 |
|
| 86 |
and no disc I put in stays in. XD |
| 87 |
|
| 88 |
Any ideas? |
| 89 |
-- |
| 90 |
thing. |
Archives
