linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macqel.be>
To: linux-wireless@vger.kernel.org
Subject: b43 'hardware blocked' but only keyboard/led touch button
Date: Mon, 29 Mar 2010 22:12:36 +0200	[thread overview]
Message-ID: <20100329201236.GA9587@frolo.macqel> (raw)

Hello wireless-linux experts,

I have installed yesterday the last opensuse 11.3 rc4 on a
hp pavilion dv6-1300sb laptop which is has a

02:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)

as wireless chip.

I needed to install such a bleeding edge distro because opensuse 11.2 does
not have the lp_phy driver yet.

with dmesg, I see :

[   21.818415] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[   21.820519] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
[   21.823084] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
[   21.975380] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[   22.076456] b43-phy0: Radio hardware status changed to DISABLED
[   22.077743] b43-phy0: Radio turned on by software
[   22.077747] b43-phy0: The hardware RF-kill button still turns the radio physically off. Press the button to turn it on.
[   22.078413] ADDRCONF(NETDEV_UP): wlan0: link is not ready

this is confirmed by rfkill :

0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes

BUT, I DON'T SEE A HARDWARE RF-KILL button;  I only see a red-lighted wireless
symbol, which is also a touch-key; in console mode, when I touch this
touch-key I get a message asking me to

	'setkey e014 <keycode>'

I have already seen this symbol being blue-lighted in the first seconds of
linux booting, but I don't know what changes this color or if this has
an effect on the 'hardware' RF-kill button.  In the BIOS there is no option
to enable or disable the wireless interface.

Any hint ?

Thanks already for the good work so far

Philippe


             reply	other threads:[~2010-03-29 20:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 20:12 Philippe De Muyter [this message]
2010-03-29 23:10 ` b43 'hardware blocked' but only keyboard/led touch button Larry Finger
2010-03-30  7:34   ` Philippe De Muyter
2010-03-30 16:47     ` Dan Williams
2010-03-30 17:11       ` Matthew Garrett
2010-03-30 19:26         ` Philippe De Muyter
2010-03-30 19:31           ` Matthew Garrett
2010-03-30 20:00             ` Philippe De Muyter
2010-03-30 20:06               ` Matthew Garrett
2010-03-30 20:43                 ` Philippe De Muyter
2010-04-19 11:53             ` Philippe De Muyter
2010-04-19 14:51               ` Matthew Garrett
2010-04-19 15:00                 ` Philippe De Muyter
2010-04-19 15:06                   ` Matthew Garrett
2010-04-24  5:42                     ` Philippe De Muyter
2010-04-24 15:21                       ` Matthew Garrett
2010-04-24 19:56                         ` Philippe De Muyter
2010-04-24 20:02                           ` Matthew Garrett
2010-04-25 19:50                             ` Philippe De Muyter
2010-04-25 20:11                               ` Larry Finger
2010-05-01 12:17                                 ` BCM4312 802.11b/g LP-PHY (rev 01) dma & led problems Philippe De Muyter
2010-05-01 16:04                                   ` Gábor Stefanik

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=20100329201236.GA9587@frolo.macqel \
    --to=phdm@macqel.be \
    --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).