[SOLVED] Acer Aspire One: Volume keys don't work

kemmotar · 2012-01-08 22:09:56

Hi!
I install Archlinux on my old Acer Aspire One and I can't set up Fn-Up and Fn-Down to control volume level.
I use this tutorial - https://wiki.archlinux.org/index.php/Acer_Aspire_One

Last edited by kemmotar (2012-01-13 15:34:07)

Trilby · 2012-01-08 22:26:23

Which steps in that wiki did you take? There are various versions depending on your setup.

Are you running X? What wm/de?

First, you should run xev to check the keycode detected when the key(s) are pressed. Xev should give something like the following if you mapped the key properly.

KeyRelease event, serial 41, synthetic NO, window 0x2200001,
    root 0x150, subw 0x2200002, time 718316678, (60,30), root:(724,732),
    state 0x10, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

kemmotar · 2012-01-08 22:46:31

Yes, I'm running X and I'm using i3 wm

I run xev and rewrite .Xmodmap but nothing changed

Trilby · 2012-01-08 23:29:01

And how do you bind XF86Audio* to amixer?

Do you use xbindkeys as described in that wiki?

Trilby · 2012-01-08 23:31:00

Also does alsamixer work for changing volume?

kemmotar · 2012-01-13 15:37:23

Thank you, I skip that part.. My bad)
But why I must do this both - setup an ~/.Xmodmap and xbindkeys?

Trilby · 2012-01-13 15:43:21

I suspect you'd only really need to do the xbindkeys.

xbindkeys binds a keycode to a command - in this case something like 'alsa set master +/-NUM'.

You could do with with the raw key code generated by your volume keys, it just may not look as pretty. Xmodmap basically just 'renames' those keys from their raw keycode values to the XF86Audio* values.

Trilby · 2012-01-13 15:50:31

Also, to follow up - I suspect many of the larger DE's automagically do the key binding from the XF86Audio* to the appropriate actions.

I'm not familiar with i3, but most lighter weight WM's do not manage this automatically for - I suspect - a couple reasons. Most importantly, since they are WM's not DE's there is no expectation or requirement that one uses a specific sound package (in this case alsa). If it automatically bound the keys to alsa, the WM would depend on alsa removing user choice and increasing dependencies. There's nothing necessarily *wrong* with that - but that's more of the DE way of doing things than a WM.

Arch Linux

#1 2012-01-08 22:09:56

[SOLVED] Acer Aspire One: Volume keys don't work

#2 2012-01-08 22:26:23

Re: [SOLVED] Acer Aspire One: Volume keys don't work

#3 2012-01-08 22:46:31

Re: [SOLVED] Acer Aspire One: Volume keys don't work

#4 2012-01-08 23:29:01

Re: [SOLVED] Acer Aspire One: Volume keys don't work

#5 2012-01-08 23:31:00

Re: [SOLVED] Acer Aspire One: Volume keys don't work

#6 2012-01-13 15:37:23

Re: [SOLVED] Acer Aspire One: Volume keys don't work

#7 2012-01-13 15:43:21

Re: [SOLVED] Acer Aspire One: Volume keys don't work

#8 2012-01-13 15:50:31

Re: [SOLVED] Acer Aspire One: Volume keys don't work

Board footer