Horror [2009-12-23 14:35 -0000]: > scan code: 0xB0 key code: volumeup > scan code: 0xAE key code: volumedown > scan code: 0x38 key code: leftalt > scan code: 0x52 key code: kp0 > scan code: 0x4F key code: kp1 > scan code: 0x50 key code: kp2 > scan code: 0x48 key code: kp8 > scan code: 0xA0 key code: mute > scan code: 0x45 key code: numlock > scan code: 0x46 key code: scrolllock > scan code: 0x39 key code: space > scan code: 0x02 key code: 1 > scan code: 0x01 key code: esc
These all work already. > Here are just, the keys that unemployed there is not defined. = ( I don't understand this sentence, sorry. You mean that the keys which do not work do not give any output in keymap -i? Then they must be on a different input device. Perhaps you can just try each input/event1 to input/event10 (or so, depending on how many you have) and see whether the non-working keys produce output on any of it? If you mean that the keys which are not working produce output which says "key code: unknown", then that is precisely what I need to know, and what we are trying to fix. :-) For those, please make a note which functionality those keys should have. -- fn keys don't work on samsung R508 https://bugs.launchpad.net/bugs/498880 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
