From: Jonathan Nieder <jrnieder@gmail.com>
To: Ike Panhc <ike.pan@canonical.com>
Cc: joeyli <jlee@suse.com>,
Carlos Corbacho <carlos@strangeworlds.co.uk>,
mjg@redhat.com, platform-driver-x86@vger.kernel.org,
Dmitry Torokhov <dtor@mail.ru>,
Corentin Chary <corentincj@iksaif.net>,
Thomas Renninger <trenn@suse.de>,
Seth Forshee <seth.forshee@canonical.com>,
Andrey <andrey.k.p@gmail.com>
Subject: Re: [PATCH v2] acer-wmi: No wifi rfkill on Lenovo machines
Date: Sat, 11 Feb 2012 13:10:44 -0600 [thread overview]
Message-ID: <20120211191044.GA7265@burratino> (raw)
In-Reply-To: <1328258799-19665-1-git-send-email-ike.pan@canonical.com>
Hi,
Ike Panhc wrote:
> We have several reports which says acer-wmi is loaded on ideapads
> and register rfkill for wifi which can not be unblocked.
>
> Since ideapad-laptop also register rfkill for wifi and it works
> reliably, it will be fine acer-wmi is not going to register rfkill
> for wifi once VPC2004 is found.
[...]
> Signed-off-by: Ike Panhc <ike.pan@canonical.com>
> ---
> drivers/platform/x86/acer-wmi.c | 30 +++++++++++++++++++++++++++++-
> 1 files changed, 29 insertions(+), 1 deletions(-)
Thanks! As described at <http://bugs.debian.org/655941>, without this
patch, Andrey was not able to use wifi, getting the following message
in the kernel log instead:
iwlagn 0000:03:00.0: RF_KILL bit toggled to enable radio.
rfkill list gave
2: acer-wireless: Wireless LAN
Soft blocked: yes
Hard blocked: no
regardless of the state of the actual radio kill switch. Unloading
the acer_wmi was a workaround. With this patch, wifi works without
needing to unload acer_wmi, so:
Tested-by: Andrey <andrey.k.p@gmail.com> # Ideapad Z570
He tested against the 3.2.y tree.
When applying this, please consider cc-ing stable@ so people using
point releases can benefit from the fix, too.
Happily,
Jonathan
next prev parent reply other threads:[~2012-02-11 19:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 6:31 [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines Lee, Chun-Yi
2012-01-09 8:01 ` Carlos Corbacho
2012-01-09 10:00 ` joeyli
2012-01-09 22:15 ` Carlos Corbacho
2012-01-11 4:26 ` joeyli
2012-01-11 16:54 ` Ike Panhc
2012-01-12 0:21 ` joeyli
2012-01-25 1:18 ` Ike Panhc
2012-01-20 2:44 ` joeyli
2012-01-25 1:29 ` Ike Panhc
2012-01-25 1:57 ` [PATCH] acer-wmi: No wifi rfkill on Lenovo machines Ike Panhc
2012-01-25 2:14 ` Ike Panhc
2012-01-26 2:53 ` joeyli
2012-02-03 8:46 ` [PATCH v2] " Ike Panhc
2012-02-03 8:55 ` Ike Panhc
2012-02-06 9:55 ` joeyli
2012-02-11 19:10 ` Jonathan Nieder [this message]
2012-02-21 9:22 ` [PATCH resend] " Jonathan Nieder
2012-03-14 21:53 ` [PATCH 3.0.y] " Jonathan Nieder
2012-03-14 22:02 ` Greg KH
2012-03-14 22:17 ` Jonathan Nieder
2012-03-16 4:03 ` Ike Panhc
2012-03-16 6:11 ` joeyli
2012-03-16 17:20 ` Greg KH
2012-03-19 2:08 ` joeyli
2012-03-19 12:40 ` Andrey
2012-03-19 14:48 ` Jonathan Nieder
2012-01-24 0:04 ` [PATCH] acer-wmi: check wireless capability on AMW0_GUID2 machines joeyli
-- strict thread matches above, loose matches on Subject: below --
2012-02-06 10:04 [PATCH v2] acer-wmi: No wifi rfkill on Lenovo machines Joey Lee
2012-02-06 11:04 ` Ike Panhc
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=20120211191044.GA7265@burratino \
--to=jrnieder@gmail.com \
--cc=andrey.k.p@gmail.com \
--cc=carlos@strangeworlds.co.uk \
--cc=corentincj@iksaif.net \
--cc=dtor@mail.ru \
--cc=ike.pan@canonical.com \
--cc=jlee@suse.com \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=trenn@suse.de \
/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