Wireless NIC on / off key does not work on ASUS A6Km

Bug #42590 reported by elele
16
Affects Status Importance Assigned to Milestone
acpi-support (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

The ASUS A6Km notebook has a button (Fn + F2) for turning the Wireless NIC on / off. This button does not work on the latest Dapper / AMD64. Pressing it simply does nothing.

Revision history for this message
Paul Sladen (sladen) wrote :

Can you follow the guidelines at:

  https://wiki.ubuntu.com/LaptopTestingTeam/HotkeyResearch

and try to discover whether it generates an ACPI event or a keypress (or something else). Currently we only have a match for:

  /etc/acpi/events/asus-wireless: hotkey ATKD 0000005d

can you do a:

  sudo tail -0f /var/log/acpid

when you press the button and paste the output.

Changed in acpi-support:
assignee: nobody → sladen
status: Unconfirmed → Needs Info
Revision history for this message
elele (elele-deactivatedaccount) wrote :

Thanks Paul,

I followed HotkeyResearch guidelines, but unfortunately didn't get any usefull information. Acpid doesn't log any events on the Fn+F2 keypress and showkey just captured the 0x9c from Enter release.

This notebook also has a wlan indication LED, but that doesn't seem to work either. Actually /proc/acpi/asus/wled is set at '1', but the led never lights up. Also 'acpitool -n 1' or echoing directly to /proc/acpi/asus/wled don't help.

I'm going to try some BIOS updates and also check on how things work on Windows side. Maybe the NIC key / LED communicate through the wlan card (Intel 2200BG) driver or something...

Revision history for this message
elele (elele-deactivatedaccount) wrote :

Seems like the wireless NIC hotkey and LED are controlled on Windows by a small program called Wireless Console 2 (wcourier.exe). Without it the NIC hotkey / LED don't work.

No indication on how the communication is done though... could be anything I guess. :/

Revision history for this message
elele (elele-deactivatedaccount) wrote :

While searching through /proc/acpi, I noticed that /proc/acpi/asus/info displays this information:

Asus Laptop ACPI Extras Driver 0.29
Model reference : M2E
SFUN value : 0x08f7
DSDT length : 29207
DSDT checksum : 227
DSDT revision : 1
OEM id : 1ABZX
OEM table id : 1ABZX001
OEM revision : 0x1
ASL comp vendor id : INTL
ASL comp revision : 0x2002026

So the notebook is falsely recognized as M2E and not A6Km... could this be the reason the NIC key / LED doesn't work?

Revision history for this message
joar (joar-bolstad) wrote :

I have the same trouble as Antti. The kernels BCM 43xx driver correctly identifies the cars, but the fn+f2 doesn't power up/down the radio, so the card can't find any AP's etc. Running Dapper i386 6.06 LTS. The file(?) /proc/acpi/asus/info seems empty though... (quite newbie as you probably recon).

Basically ACPI doesn't trap the keycombo (tried acpi_listen amongst others). How to programatically power up the radio I have no idea how to do.

Paul Sladen (sladen)
Changed in acpi-support:
assignee: sladen → nobody
Revision history for this message
Mephisto (ferrylandzaat) wrote :

The helper script gives the following error for me:
/usr/share/acpi-support/state-funcs: line 44: echo: write error: Invalid argument
I'm using the ndiswrapper driver, cause the native driver does not support 54M at all, and is terribly slow anyway. It does not have a device/rf_kill in /sys, which is used by the new feisty acpi script. This used to work in an older version of ubuntu, not sure when it stopped working, as i dont use the key very frequently.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for acpi-support (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.