From: Ike Panhc <ike.pan@canonical.com>
To: Joey Lee <jlee@novell.com>
Cc: heyho@flanto.de, platform-driver-x86@vger.kernel.org
Subject: Re: Wifi switch not working, linux on IdeaPad S205
Date: Thu, 16 Jun 2011 17:58:04 +0800 [thread overview]
Message-ID: <4DF9D3AC.1050502@canonical.com> (raw)
In-Reply-To: <4DF908DA020000230002E497@novprvlin0050.provo.novell.com>
On 06/15/2011 05:32 PM, Joey Lee wrote:
> 於 四,2011-06-09 於 16:36 +0800,Ike Panhc 提到:
>
> But Florian said the Fn+F5 doesn't work to him, as you said, the _Q2B
> works when GWSS is not zero:
>
> Method (_Q2B, 0, NotSerialized) /* wifi key? */
> {
> Store (0x2B, P80H)
> If (LEqual (GWSS, 0x00)) {} /* on issue machine, GWSS is 0 */
> Else
> {
> If (WLPS) /* if have wireless */
> {
> Store (WRST, WLEN) /* write wireless RF state to EC */
> }
>
I see your point. IMHO this is ok. When the radio switch is off, it shall
be no different on every soft block modes.
> 於 二,2011-05-31 於 15:02 +0200,Florian Heyer 提到:
>> On 05/31/2011 11:42 AM, Joey Lee wrote:
>>> Just checked your DSDT, it declared the AMW0 methods, I agreed Ike's
>>> suggestion that will be better you direct test acer-wmi on your machine.
>>>
>>> Please modprobe acer-wmi driver, then try to turn on/off bluetooth or
>>> wireless device by rfkill.
>>
>> Hello Joey,
>>
>> here are some findings with acer_wmi. I execute the following steps from
>> top to bottom, and only after the last step my wifi works. After each
>> step you find the output of "rfkill list":
>>
>> after booting (no ideapad_laptop, no acer_wmi):
>> 0: hci0: Bluetooth
>> Soft blocked: no
>> Hard blocked: no
>> 1: phy0: Wireless LAN
>> Soft blocked: no
>> Hard blocked: yes
>>
>
> When system boot, wireless is hard blocked by default.
>
Read the reply mail from Florian. This is a problem because hard blocked
shall be no when the radio switch is on. Since phy0 is registered by wifi
driver, I think this is not generic design.
next prev parent reply other threads:[~2011-06-16 9:58 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 22:50 Wifi switch not working, linux on IdeaPad S205 Joey Lee
2011-05-31 23:42 ` Florian Heyer
2011-06-01 2:08 ` Joey Lee
2011-06-02 8:42 ` Florian Heyer
2011-06-02 19:16 ` Joey Lee
2011-06-03 12:49 ` Florian Heyer
2011-06-07 13:48 ` Joey Lee
2011-06-09 8:36 ` Ike Panhc
2011-06-15 9:32 ` Joey Lee
2011-06-15 9:42 ` Florian Heyer
2011-06-17 13:09 ` Joey Lee
2011-06-17 15:03 ` Florian Heyer
2011-06-17 22:50 ` Joey Lee
2011-06-19 16:15 ` Florian Heyer
2011-06-18 0:38 ` Joey Lee
2011-06-19 15:23 ` Florian Heyer
2011-06-20 10:10 ` Joey Lee
2011-06-20 10:58 ` Florian Heyer
2011-06-21 10:16 ` Joey Lee
2011-06-24 21:03 ` Florian Heyer
2011-06-27 8:17 ` Joey Lee
2011-06-22 9:28 ` Ike Panhc
2011-06-24 21:28 ` Florian Heyer
2011-06-27 8:17 ` Joey Lee
2011-06-30 14:26 ` Ike Panhc
2011-06-30 15:03 ` Florian Heyer
2011-07-01 8:24 ` Ike Panhc
2011-06-16 9:58 ` Ike Panhc [this message]
2011-06-17 10:58 ` Joey Lee
[not found] <4DAB18C3.7010106@flanto.de>
[not found] ` <4DAB9566.7010601@canonical.com>
2011-04-28 8:42 ` Florian Heyer
2011-05-31 6:02 ` Ike Panhc
2011-05-31 6:28 ` Joey Lee
2011-05-31 6:38 ` Ike Panhc
2011-05-31 7:26 ` Florian Heyer
2011-05-31 9:42 ` Joey Lee
2011-05-31 13:02 ` Florian Heyer
2011-05-31 13:58 ` Joey Lee
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=4DF9D3AC.1050502@canonical.com \
--to=ike.pan@canonical.com \
--cc=heyho@flanto.de \
--cc=jlee@novell.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