Arch Linux

youngmit

Member

Registered: 2009-09-04

Posts: 13

Volume keys on Thinkpad T420s don't appear as normal events [solved]

I am having issues getting my volume keys to work properly on a new installation on a Thinkpad T420s and Im running into a snag. When i try to inspect the keycode associated with my volume keys using xev, i get this:

FocusIn event, serial 33, synthetic NO, window 0x1600001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 33, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0 

while other interesting keys look more like

KeyPress event, serial 33, synthetic NO, window 0x1600001,
    root 0x15d, subw 0x1600002, time 11122692, (44,34), root:(45,54),
    state 0x0, keycode 179 (keysym 0x1008ff81, XF86Tools), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0x1600001,
    root 0x15d, subw 0x1600002, time 11122792, (44,34), root:(45,54),
    state 0x0, keycode 179 (keysym 0x1008ff81, XF86Tools), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

so it appears that Xorg isnt treating the volume keys like other multimedia keys... any idea why this might be?

I tried the same keys in showkey in a console and got keycode 114 and 115 for volume up and volume down, respectively, so the kernel is obviously picking them up, just Xorg is doing something strange with them.

Any help would be appreciated. Thanks!

Last edited by youngmit (2012-04-25 22:20:53)

youngmit

Member

Registered: 2009-09-04

Posts: 13

Re: Volume keys on Thinkpad T420s don't appear as normal events [solved]

nevermind i actually figured it out. I had the keys bound in my awesome config to volume commands that didnt work. i had copied my config from my previous ubuntu installation and needed to add -c 0 to the amixer command for it to work since alsa is configured differently on the new system. crisis averted! :-)