On Wed, Apr 14, 2010 at 3:31 AM, Trent W. Buck <[email protected]> wrote: > Corentin Chary <[email protected]> > writes: > >> On Tue, Apr 13, 2010 at 1:22 PM, Trent W. Buck <[email protected]> >> wrote: >>> On my 1005P, running Sid with .33 1~exp4 from experimental, some Fn >>> hotkeys generate input. For example, >>> >>> - Fn+F10 (Mute) generates ^[[25~; >>> - Fn+F11 (VolDn) generates ^[[26~; and >>> - Fn+F12 (VolUp) generates nothing >> What's the acpi event associated with Fn+F12 ? > > I get > > $ acpi_listen > > Fn+F10 > > hotkey ASUS010:00 00000013 00000000 > ^[[25~button/mute MUTE 00000080 00000000 > > Fn+F11 > > hotkey ASUS010:00 00000014 00000000 > ^[[26~button/volumedown VOLDN 00000080 00000000 > > Fn+F12 > > hotkey ASUS010:00 00000015 00000001 > button/volumeup VOLUP 00000080 00000000 > >>> This is annoying -- for example, if I'm looking at alsamixer, the ^[ >>> causes alsamixer to quit. >> >> In a standard VT or in an xterm ? > > Sorry, I should've said. I'm running screen in fbcon; no X. > > Running "xinit /usr/bin/xterm -e xev", xev reports the keysyms > XF86AudioMute, XF86AudioLowerVolume and XF86AudioRaiseVolume. > >> Did you try do edit your keymap ? > > I'm not sure what you mean by that, but > > $ egrep -v '^[[:space:]]*(#|$)' /etc/default/console-setup > /etc/default/keyboard > /etc/default/console-setup:VERBOSE_OUTPUT="no" > /etc/default/console-setup:ACTIVE_CONSOLES="/dev/tty[1-6]" > /etc/default/console-setup:CHARMAP="UTF-8" > /etc/default/console-setup:CODESET="Uni2" > /etc/default/console-setup:FONTFACE="Terminus" > /etc/default/console-setup:FONTSIZE="12x6" > /etc/default/console-setup:if [ -f /etc/default/keyboard ]; then > /etc/default/console-setup: . /etc/default/keyboard > /etc/default/console-setup:fi > /etc/default/keyboard:XKBMODEL="pc105" > /etc/default/keyboard:XKBLAYOUT="us" > /etc/default/keyboard:XKBVARIANT="" > /etc/default/keyboard:XKBOPTIONS="ctrl:nocaps" > >> What does showkey / xev tell you when you press Fn+F11 > > $ showkey > Couldn't get a file descriptor referring to the console > > If I run it as root on vt2 (i.e. fbcon, no screen), I get keycode press > and release events for 113, 114 and 114 respectively.
All seems ok and I was able to reproduce the issue (only in screen), but I don't really know what's the best way to fix it. Isn't there any way to "ignore" an input device in screen/fbcon ? -- Corentin Chary http://xf.iksaif.net _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
