[EeePc 1001ha] WiFi Hotkey (Fn-F2) not working on xubuntu 13.04

[andrej]

WiFi adaptor is working fine if I switch it on/off in the BIOS but the Fn-F2 hotkey toggle is not working. Volume and Brighness keys are OK.

Many thanks.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andrey 1624 F.... pulseaudio
CRDA:
 country RU:
  (2402 - 2482 @ 40), (N/A, 20)
  (5735 - 5835 @ 20), (N/A, 30)
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=a9f2c383-c911-44d3-9d26-016d641b06cb
InstallationDate: Installed on 2013-04-25 (3 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
MachineType: ASUSTeK Computer INC. 1001HA
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=1d8abb55-86c6-4f3c-a67e-520aeef267ad ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-19-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 01/05/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1005HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd01/05/2010:svnASUSTeKComputerINC.:pn1001HA:pvrx.x:rvnASUSTeKComputerINC.:rn1005HA:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1001HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1173939/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Steve Langasek (vorlon)]

I'm fairly certain this hotkey is handled in the kernel, not by acpi-support.

You may find it useful to read /usr/share/doc/udev/README.keymap.txt.gz for information about hotkeys are handled, to help see where the keypresses are being lost.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1173939

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[andrej (seubert)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/

[andrej (seubert)]

hi. I installed the latest version of the kernel:

andrey@andrey-1001HA:~$ cat /proc/version
Linux version 3.9.0-030900-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201304291257 SMP Mon Apr 29 17:06:25 UTC 2013

but it does not fix this bug.

[penalvch (penalvch)]

andrej, as per http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_1001HA_Seashell/#support_Download_5 an update is available for your BIOS (1601). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Dmitry Piyavkin (piyavkin)]

It affects me too on ASUS Eee PC 1025CE.
Some other key combinations also not functional. F.e., Fn + F7 (turn off the screen).
Sound volume, mute, brightness though work fine. But only after full install. In the LiveCD mode they don't work properly.

[penalvch (penalvch)]

Dmitry Piyavkin, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.