From: Dan Williams <dcbw@redhat.com>
To: Arliton Rocha <arliton@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problem: BCM 4313 (brcmsmac) always hard blocked
Date: Wed, 08 Aug 2012 12:59:52 -0500 [thread overview]
Message-ID: <1344448792.18836.14.camel@dcbw.foobar.com> (raw)
In-Reply-To: <CANZ_KY5yLJrHKQ4c30sNpVXPBRRTzwjyUYREcOaX8YP=OAB=Ew@mail.gmail.com>
On Wed, 2012-08-08 at 08:14 -0300, Arliton Rocha wrote:
> Hi devs,
>
> The following card does not work (remains always 'hard blocked'):
> 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313
> 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
>
> There is no a physical lock on the notebook in question.
> I know windows can change only by software.
> When i do this, wireless net (and bluetooth) works fine on linux.
> Ok, install windows, unblock... But, why linux can't do this?
> I have trying a lot of tips about rfkill (unblock all, ...) but
> nothing, remains hard blocked.
> Also i tried, unsuccessfully, map Fn + F12 keys...
BIOS usually controls this sort of thing. Check "rfkill list" and see
if you have a "platform" killswitch. On my HP, that looks like:
0: hp-wifi: Wireless LAN
and when that is blocked, it hardblocks the internal wifi. This switch
is provided by a small driver that talks to your laptop's BIOS. It's
likely that either your laptops device IDs are not added to the correct
kernel driver, or your laptop does things in a different way than
previous ones, and doesn't have a kernel driver yet. But in the end,
this is most likely a kernel rfkill driver bug, not a wifi bug.
What make and model of laptop is this?
Dan
> Someone have an idea?
>
> Hardware information in attachment.
>
> Thanks in advance.
> Best regards.
>
> --
> Arliton Rocha
next prev parent reply other threads:[~2012-08-08 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANZ_KY5-EZ2n54G3P3wnjUdTdVknarnXFK2cj9WobnQemAr5kA@mail.gmail.com>
2012-08-08 11:14 ` Problem: BCM 4313 (brcmsmac) always hard blocked Arliton Rocha
2012-08-08 15:29 ` Arend van Spriel
2012-08-08 17:59 ` Dan Williams [this message]
2012-08-09 0:24 ` Arliton Rocha
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=1344448792.18836.14.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=arliton@gmail.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).