regression after "asus-wmi: update wlan LED through rfkill led trigger"

regression after "asus-wmi: update wlan LED through rfkill led trigger"

[Oleksij Rempel]

Hello all,

i have regression on Asus Zenbook UX32A after this patch:

commit 6cae06e603339f99334bc6b276e2ac619cf0d476
Author: AceLan Kao <acelan.kao@canonical.com>
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 <acelan.kao@canonical.com>
     Signed-off-by: Matthew Garrett <mjg@redhat.com>


Symptoms are fallowing:
- hot keys: F3, F4 (keyboard led); F10, F11, F12 (sound) - are not working.
- keyboard back light is off
- brightness keys (F5, F6) are working but with some issues. For example 
if you press it with short intervals, then it works ok. If you hold this 
buttons, thin it accumulate all calls and will fire them all after some 
time.

I also have similar machine "Asus Zenbook UX32E", without this problem.

-- 
Regards,
Oleksij

Re: regression after "asus-wmi: update wlan LED through rfkill led trigger"

[Oleksij Rempel]

Am 20.06.2013 08:58, schrieb AceLan Kao:
> Hi,
>
> Yes, controlling the wifi led function affects many asus users.
> And I already had a fix for this.
> https://bugzilla.kernel.org/show_bug.cgi?id=46791
>
> Please blacklist asus-wmi driver before the patch appears in the distro.
> kernel.
> Sorry about the inconvenience.

no problem. i reverted this patch for now.
Thank you for your work.

-- 
Regards,
Oleksij