From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: schwaahed <schwaahed@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Centrino Ultimate-N 6300 AGN rfkill always Soft blocked
Date: Mon, 15 Apr 2013 09:39:32 -0500 [thread overview]
Message-ID: <1366036772.2404.3.camel@dcbw.foobar.com> (raw)
In-Reply-To: <1366032132.8361.19.camel@jlt4.sipsolutions.net>
On Mon, 2013-04-15 at 15:22 +0200, Johannes Berg wrote:
> On Fri, 2013-04-12 at 17:04 -0500, Dan Williams wrote:
> > On Thu, 2013-04-11 at 20:03 -0400, schwaahed wrote:
> > > Hello,
> > >
> > > I have an HP Elitebook 8460w laptop containing a Centrino Ultimate-N
> > > 6300 AGN (linux-3.8.6 iwlwifi module - firmware version 9.221.4.1
> > > build 25532)
> >
> > I notice that your 'rfkill list all' dumps below don't contain an entry
> > for hp-wmi. Is that module loaded on your machine? It's needed at
> > least for earlier models of the Elitebook, up at least until the xx40
> > series. Perhaps it needs to be updated for your laptop? You might ask
> > on the general kernel lists if anyone knows how rfkill is supposed to
> > work for the 8460 and if hp-wmi supports it, or if some other mechanism
> > is used.
>
> Yeah it seems not loaded, but how then does the soft block affect hard
> block? All very odd, but almost certainly a platform rather than a wifi
> issue.
On my 2530p and a lot of other laptops, blocking the BIOS
"switch" (either physically or softblock) hardblocks phy0. I guess the
BIOS twiddles a GPIO that's connected to the mPCI-E module's rfkill
line/GPIO?
Which leads to the problem we've talked about a long time ago; you can't
treat phy0 hardblock as a physical block that cannot be soft-unblocked,
because some other switch might actually control it's state. We tried
to gray-out the "Enable Wireless" when hardblocked (since logically you
can't soft-unblock something that's hardblocked), but it turns out you
can't do that because unblocking BIOS switches might un-hardblock the
phy0 wifi switch... (and the kernel doesn't describe these
dependencies, because, well, that's laptop-specific and would never be
up-to-date).
Dan
next prev parent reply other threads:[~2013-04-15 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 0:03 Centrino Ultimate-N 6300 AGN rfkill always Soft blocked schwaahed
2013-04-12 22:04 ` Dan Williams
2013-04-15 13:22 ` Johannes Berg
2013-04-15 14:39 ` Dan Williams [this message]
2013-04-15 15:31 ` Johannes Berg
2013-04-15 15:50 ` schwaahed
2013-04-15 16:34 ` Dan Williams
2013-04-16 1:17 ` schwaahed
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=1366036772.2404.3.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=schwaahed@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.