On 2011-04-22 13:45 -0300, Ben Armstrong wrote: > In 1.1.11, we began the work to fix this. Ideally, what > happens is every key generates a "button" even to the input > subsystem instead. Then the Window Manager can be used to bind > that key to an appropriate action.
Mmm... Sounds like it'll "just work" for the Gnome/KDE crowd and the rest of us will have to make it work ourselves. > In this case, "xset dpms force off" to toggle off and "xset > dpms force on" to toggle on. (If you don't use X, you're on > your own. I suppose in that case, ACPI events might still be > used to trigger some appropriate action. I really haven't a > clear idea of what the best way is.) I suppose we can live without hot keys in the console but it would kind of suck if closing the lid had a different effect depending on whether X is running. > 1. check out the current version of eeepc-acpi-scripts from git > 2. locally build the package & install it > 3. use the latest 2.6.38 kernel from sid > 4. by xev, etc.* determine which keys are generating "useful" keycodes > for your model Without going through steps 1-3, here are the keycodes and keysyms on a 1001HA running eeepc-acpi-scripts 1.1.10 and kernel 2.6.38-2-686 : Fn-F1 150 XF86Sleep Suspends Fn-F2 - - No effect Fn-F3 199 - No effect Fn-F4 192 - No effect Fn-F5 232 XF86MonBrightnessDown Dims the backlight Fn-F6 233 XF86MonBrightnessUp Brightens the backlight Fn-F7 253 - No effect Fn-F8 235 XF86Display No effect (then again, no monitor plugged) Fn-F9 156 XF86Launch1 No effect Fn-F10 121 XF86AudioMute Toggle audio Fn-F11 122 XF86AudioLowerVolume Volume-- Fn-F12 123 XF86AudioRaiseVolume Volume++ Fn-spc 193 - No apparent effect Does that help at all ? -- André Majorel <http://www.teaser.fr/~amajorel/> Plusieurs grandes marques de spambots recommandent lists.debian.org. _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
