Package: hal-info Version: 20090309-1 Severity: normal [ I'm not sure how audio keys are supposed to work, so maybe this is not the right place to report it, but here it goes. ]
When I hit the Fn-F7, Fn-F8, Fn-F9 keys (resp. volume-down, volume-up, mute) on my MSI Wind, nothing seems to happen. I don't get any "setkeycodes" errors in dmesg, and instead get unmapped keycoeds in X: "xev" tells me the three keys generate the X keycodes 174, 176, and 160 (respectively). Following some hints found at http://people.freedesktop.org/~hughsient/quirk/quirk-keymap-try.html, I tried to add a file /etc/hal/fdi/information/foo.fdi: <?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- --> <deviceinfo version="0.2"> <device> <!-- These are raw scancodes produced by the atkbd driver --> <match key="@input.originating_device:info.linux.driver" string="atkbd"> <match key="/org/freedesktop/Hal/devices/computer:system.hardware.vendor" prefix="MICRO-STAR"> <match key="/org/freedesktop/Hal/devices/computer:system.hardware.product" contains_outof="U-100"> <append key="input.keymap.data" type="strlist">00a0:mute</append> <append key="input.keymap.data" type="strlist">00ae:volumedown</append> <append key="input.keymap.data" type="strlist">00b0:volumeup</append> <append key="info.capabilities" type="strlist">input.keymap</append> </match> </match> </match> </device> </deviceinfo> but it didn't seem to make any difference (tho it does appear in lshal, so the match statements seem to work right). I'd love to dig deeper, but as mentioned earlier I have no idea how such keys are *supposed* to work, so I'd be happy to be directed to some info explaining how such keys are supposed to be configured. Stefan -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
