From: Michael Larabel <michael.larabel@phoronix.com>
To: linux-wireless@vger.kernel.org
Subject: b43: Radio Hardware Status Disabled
Date: Fri, 23 May 2008 23:03:55 -0400 [thread overview]
Message-ID: <4837859B.3050100@phoronix.com> (raw)
With a Linksys WUSB600N and NetGear WNDA3100, which both appear to
utilize a Broadcom 4311 chipset, the radio hardware status always seems
to get set to disabled immediately after the wireless interface is
started and are never re-enabled.
This is happening with the b43 driver (found in Linux 2.6.25.3 kernel)
on Fedora 9. Below is the dmesg and lspci output.
dmesg | grep b43
b43-phy0: Broadcom 4311 WLAN found
b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 8
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
input: b43-phy0 as /devices/virtual/input/input10
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 32-bit DMA initialized
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
b43-phy0 debug: Wireless interface started
b43-phy0: Radio hardware status changed to DISABLED
b43-phy0 debug: Adding Interface type 2
05:00.0 Network controller [0280]: Broadcom Corporation BCM94311MCG wlan mini-PCI [14e4:4311] (rev 01)
Subsystem: Dell Unknown device [1028:0007]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at c0200000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 2
Capabilities: [58] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
Capabilities: [d0] Express Legacy Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [13c] Virtual Channel <?>
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
Anything to get these cards working?
Michael
next reply other threads:[~2008-05-24 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-24 3:03 Michael Larabel [this message]
2008-05-28 0:21 ` b43: Radio Hardware Status Disabled John W. Linville
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=4837859B.3050100@phoronix.com \
--to=michael.larabel@phoronix.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 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.