From: Oleksij Rempel <linux@rempel-privat.de>
To: platform-driver-x86@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net,
Corentin Chary <corentin.chary@gmail.com>,
AceLan Kao <acelan.kao@canonical.com>,
Matthew Garrett <mjg@redhat.com>
Subject: regression after "asus-wmi: update wlan LED through rfkill led trigger"
Date: Thu, 20 Jun 2013 08:44:03 +0200 [thread overview]
Message-ID: <51C2A4B3.8090708@rempel-privat.de> (raw)
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
next reply other threads:[~2013-06-20 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 6:44 Oleksij Rempel [this message]
[not found] ` <CAMz9Wg9V+RXk78Yb8TCuzLV=CienKK6Mz0SRd7b7LeO2sci07A@mail.gmail.com>
2013-06-20 8:19 ` regression after "asus-wmi: update wlan LED through rfkill led trigger" Oleksij Rempel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51C2A4B3.8090708@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=acelan.kao@canonical.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox