[Asus Eee PC 1000H] Hotkeys don't work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udev (Ubuntu) |
Invalid
|
Medium
|
Martin Pitt |
Bug Description
Hotkeys on Asus Eee PC 1000H with Kubuntu 8.10 doesn't work (acpi_listen see all hotkey presses).
I've attached the output of dmidecode, probably it can be useful.
* Instant Keys doesn't work (I can't assign any of these keys from System Settings -> Keyboard & Mouse)
* WiFi hotkey (nothing happens)
* Fn+F7, Fn+F8, Fn+F9 doesn't works (Fn+F8 should switch between LCD/External monitor but it's seen like the VolumeUP key and change the volume of the PCM channel, but the OSD shows always 0% ad volume :P!)
* Audio Hotkeys (mute, volume up, volume down) doesn't work
I suggest you to visit these sites :
* http://
* http://
Changed in udev (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Martin Pitt (pitti) |
This is a known issue with Ubuntu, xubuntu, and kubuntu versions before 9.04. Upgrading to 9.04 probably will not provide a seamless fix.
In 9.04, the installer selects a 105 key generic keyboard layout. This layout does not support any of the EEEpc specific keys, which makes sense. It *is* a generic layout after all.
The Asus laptop layout offers support for at least some of the EEEpc specific features (I've gotten the instant keys to work, haven't pinned down the Fn-Fkey combos). The problem is, even tho the Ubuntu installer correctly identifies the laptop as an EEEpc, it does not select the correct keyboard layout. Once the user selects the correct layout, getting all the features to work is somewhat confusing, as the user interface does not offer a lot of guidance for a new user.
If you are using 9.04, eee-control 0.9.2 will have issues if you're using the correct keyboard layout. After a suspend, the machine will no longer have keyboard input... I haven't pinned down what the mechanism is, but have contacted the maintainer.
If sound is not working (and from your description it sounds like it isn't), it will be difficult to troubleshoot that portion of your keyboard bug report.