From: Florian Heyer <heyho@flanto.de>
To: Joey Lee <jlee@novell.com>
Cc: ike.pan@canonical.com, platform-driver-x86@vger.kernel.org
Subject: Re: Wifi switch not working, linux on IdeaPad S205
Date: Mon, 20 Jun 2011 12:58:52 +0200 [thread overview]
Message-ID: <4DFF27EC.9080804@flanto.de> (raw)
In-Reply-To: <4DFFA92F020000230002E786@novprvlin0050.provo.novell.com>
On 06/20/2011 12:10 PM, Joey Lee wrote:
> But,
> here have a question:
>
> The phy0 killswitch didn't set to hard blocked, did wireless LAN still
> can be used at this moment? even hardware switch is off?
Hello Joey,
i tested again:
First with acer-wmi inserted (as always boot-state of wifi button is on):
switching to off "rfkill list" is:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
6: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: yes
(phy0-hard blocked goes to "yes" after 1 or 2 seconds, maybe yesterday i
didn't wait long enough). Wifi doesn't work in this state, i checked.
Switching to on "rfkill list" is:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
6: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
7: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Wifi now works!
After removing acer-wmi (so i loaded it only for initialisation),
switching to off "rfkill list" is:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
Back to on:
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
5: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
wifi works in state "on"- so acer-wmi is really needed only for
initialisation.
ideapad-laptop is _not_ loaded, the wifi switch works correctly nonetheless.
> I thought the real situation back to BT on, Wireless on, right?
yes, after switching to on everything is back to state after
initialisation (wifi works).
regards
--
Florian Heyer - heyho@flanto.de
next prev parent reply other threads:[~2011-06-20 10:59 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 [this message]
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
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=4DFF27EC.9080804@flanto.de \
--to=heyho@flanto.de \
--cc=ike.pan@canonical.com \
--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