Asus K54C wireless led is always off

the patch is sent upstream for review. This bug is opened for SRU for Oneric once it gets merged mainline.

upstream nack'ed this patch and asked for quirking and handling the led trigger in a correct way. need more work.

Since I can't find a machine with this wifi card to test, this patch is not verified yet...
Kernel packages for test can be found at http://people.canonical.com/~jesse/lp901105/

finally, we will update the wlan LED through rfkill led trigger

The patch for this issue is discussing in the platform-x86 mailing list
http://www.spinics.net/lists/platform-driver-x86/msg03652.html

patch is accepted by asus-wmi driver maintainer

The attachment "0001-Add-a-quirk-of-wlan-LED-for-certain-Asus-WLAN-cards.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

@AceLan -- I don't see this in Quantal as yet. Perhaps you could send this patch up to the kernel-team@ list.

Andy, this patch requires another commit in rfkill(linux-wireless),
once they all enter linus' tree, I'll send the request to kernel-team.

Quantal and Precise SRU sent

Patch has not landed in Quantal, reset to Confirmed.

Yes, the SRU was rejected because that patch was in linux-next, not in mainstream kernel tree at that time.
I'll re-submit it soon.

I just check the status of the patches, there is one commit not in linus' tree yet.
I just wrote to the maintainer of the platform-x86 tree to ask him to submit the queued patch.
Once the commit get merged into mainstream kernel, I'll submit the SRU.

The patch is still in platform-x86 maintainer's tree, for requiring another patch goes into linus' tree first.
I think this patch will land on 3.8 kernel soon.

The required patches are in 3.5 and 3.8 mainstream kernel.

commit 06d7de831dab8b93adb86e039a2f3d36604a9197
Author: AceLan Kao <email address hidden>
Date: Thu Jul 26 09:51:08 2012 +0800

    Revert "rfkill: remove dead code"

    This reverts commit 2e48928d8a0f38c1b5c81eb3f1294de8a6382c68.

    Those functions are needed and should not be removed, or
    there is no way to set the rfkill led trigger name.

    Signed-off-by: AceLan Kao <email address hidden>
    Signed-off-by: Johannes Berg <email address hidden>

commit 6cae06e603339f99334bc6b276e2ac619cf0d476
Author: AceLan Kao <email address hidden>
Date: Fri Jul 27 16:51:59 2012 +0800

    asus-wmi: update wlan LED through rfkill led trigger

    For those machines with wapf=4, BIOS won't update the wireless LED,
    since wapf=4 means user application will take in chage of the wifi and bt.
    So, we have to update wlan LED status explicitly.

    But I found there is another wireless LED bug in launchpad and which is
    not in the wapf=4 quirk.
    So, it might be better to set wireless LED status explicitly for all
    machines.

    BugLink: https://launchpad.net/bugs/901105

    Signed-off-by: AceLan Kao <email address hidden>
    Signed-off-by: Matthew Garrett <email address hidden>

Acelan, 6cae06e603339f99334bc6b276e2ac619cf0d476 is not yet in Raring, could you cherry-pick it for Raring kernel?

This bug was fixed in the package linux - 3.9.0-0.2

---------------
linux (3.9.0-0.2) saucy; urgency=low

  [ Tim Gardner ]

  * Enable extras packaging for amd64/i386.
    Fixes build depenencies with brittany and linux-meta.
 -- Tim Gardner <email address hidden> Mon, 29 Apr 2013 05:37:01 -0600

This change appears to break UX32VD function keys

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173107