Broadcom 4306 doesn't work! I cannot connect to any wireless network

[Ricky]

Binary package hint: network-manager

Originally I installed Ubuntu 8.04 beta 1 and it didn't see any wireless card. Then I installed b43-fwcutter and now my wlan card (Broadcom 4306) is recognised and it finds my wireless network, but I cannot connect!
When I write "dmesg" command, this is the result (I only post b43-related messages):

[ 50.648445] Registered led device: b43-phy0:tx
[ 50.650801] Registered led device: b43-phy0:rx
[ 50.651200] Registered led device: b43-phy0:radio
 93.548499] wlan0: Initial auth_alg=0
[ 93.548504] wlan0: authenticate with AP 00:c0:49:e7:e5:00
[ 93.648260] wlan0: authenticate with AP 00:c0:49:e7:e5:00
[ 93.748062] wlan0: authenticate with AP 00:c0:49:e7:e5:00
[ 93.847863] wlan0: authentication with AP 00:c0:49:e7:e5:00 timed out
[ 100.166413] wlan0: Initial auth_alg=0
[ 100.166418] wlan0: authenticate with AP 00:c0:49:e7:e5:00
[ 100.265753] wlan0: authenticate with AP 00:c0:49:e7:e5:00
[ 100.365555] wlan0: authenticate with AP 00:c0:49:e7:e5:00
[ 100.465359] wlan0: authentication with AP 00:c0:49:e7:e5:00 timed out

Description: Ubuntu hardy (development branch)
Release: 8.04
Kernel: 2.6.24-12 (but I also installed 2.6.24-13 but it doesn't work neither)

[Simone Crescenzo (simone.crescenzo-deactivatedaccount)]

i can confirm with an olidata stainer w2800 and broadcom 4318

[lylepratt (lylepratt)]

I am having the exact same issue. I have been waiting and waiting for an update to fix it to no avail. It used to work fine with Edgy.

[kjbull (eeck)]

I have the same issue with kernel 2.6.24-16-generic, the hardy release kernel. My broadcom bcm4306 rev. 03 worked fine in gutsy, using the bcm43xx driver. When I boot into the 2.6.22 gutsy kernel, and modprobe bcm43xx, the card works. However, neither the new b43 or b43legacy drivers seem to work properly. I have the firmware installed, and can set the essid using iwconfig, but whenever I try to get a dhcp address, using either dhclient or knetworkmanager, it fails. I think that this is not a network manager bug, but a driver bug, given that dhclient fails as well as network manager. I get similar dmesg results as the original post.

[Henrik Hodne (henrik-hodne)]

I have exactly the same issue as kjbull!

[f37u5g0d (enovak)]

I have the exact same bug as described in the original post. Also when I reboot I have to re-enable the restricted B43 driver in hardware drivers each time before wireless shows up at all.

[Quicksilver_Johny (quicksilverjohny)]

Exact same issue with a Broadcom 4306 which workd with little difficulty since... dapper?
A solution is really needed here.

[Roger Magnesved (rogz)]

I also have that problem with a Broadcom 4306 Rev 03 card. google revealed this http://www.linuxwireless.org/en/users/Drivers/b43#bcm43xx.2Cb43legacy.2Cb43.2Csoftmac.2C...thefullstory
which states

"4306 and 4309 cards with a MAC core revision of 4 or less should also use b43legacy."

and a bit further down

"always build both b43 and b43legacy (and get firmware for both too). The kernel autoloader will automatically do the right thing and load the correct driver for your device."

Which makes me wonder, the "Rev 03" printed during boot is not the MAC core revision or there is a bug with selecting the correct kernel driver for the cards with MAC core revision < 4. I tried putting the b43 driver as blacklisted, but that didn't give me a b43legacy driver loaded at all and modprobe for the driver didn't help that much either.

I can attach output from lspci and friends in a later post if needed for further fault isolation.

[Ricky (ricky485)]

I have resolved the problem with my broadcom 4306 card using this guide:

1) sudo gedit /etc/init.d/bcm43xxfix.sh

Write in the file:

         #! /bin/sh

         rmmod b43legacy
         rmmod b43
         rmmod bcm43xx
         rmmod ssb
         modprobe bcm43xx

2) cd /etc/init.d/ && sudo chmod 755 bcm43xxfix.sh
3) sudo update-rc.d bcm43xxfix.sh defaults
4) sudo gedit /etc/modprobe.d/blacklist

Replace in this file

         # replaced by b43 and ssb.
         blacklist bcm43xx

with

         # replaced by b43 and ssb.
         # blacklist bcm43xx

5) reboot

Let me know if it works also for you

[f37u5g0d (enovak)]

I tried the above method and it didn't work :(. I now have wireless recognized in the nm-applet :) but no networks are listed (and there should be at least 2). Also there is no longer a b43 option listed in the hardware drivers manager. The output of dmesg is alot (and I mean ALOT) of this entry over and over again:

"[ 548.561014] bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed."

Each at ascending system times (I'm assuming that's what that first number in the bracket is).
What should I do? Is that file part of the firmware extract or something?

[f37u5g0d (enovak)]

Also I just noticed that sudo lshw -C network gives this:
" *-network:0 DISABLED
       description: Wireless interface
       product: BCM4306 802.11b/g Wireless LAN Controller
       vendor: Broadcom Corporation
       physical id: 9
       bus info: pci@0000:00:09.0
       logical name: eth0
       version: 03
       serial: 00:0f:66:70:6b:e7
       width: 32 bits
       clock: 33MHz
       capabilities: bus_master ethernet physical wireless
       configuration: broadcast=yes driver=bcm43xx driverversion=2.6.24-16-generic latency=64 link=no module=bcm43xx multicast=yes wireless=IEEE 802.11b/g
  *-network:1
       description: Ethernet interface
       product: VT6102 [Rhine-II]
       vendor: VIA Technologies, Inc.
       physical id: 12
       bus info: pci@0000:00:12.0
       logical name: eth1
       version: 78
       serial: 00:19:21:01:05:07
       size: 100MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.4.3 duplex=full ip=10.124.12.68 latency=64 link=yes maxlatency=8 mingnt=3 module=via_rhine multicast=yes port=MII speed=100MB/s"

Why does it say network:0 is disabled?

[Roger Magnesved (rogz)]

According to http://www.linuxwireless.org/en/users/Drivers/b43#devicefirmware it seems like you'll have to use version 006 of fwcutter to extract the firmware for the 3.130.20.0 firmware version. The version shipped with Hardy is 011, so if you want to try Rickys solution, you'll have to install the older fwcutter and use it to extract the firmware.

[f37u5g0d (enovak)]

Adding fwcutter verison 006 had no effect on Ricky's solution for me.

[Roger Magnesved (rogz)]

Did you extract the firmware with version 006 too? I'm just asking since I forgot it myself the first time I tested.

[f37u5g0d (enovak)]

Yeah I extracted the firmware and everything. Thanks for asking
though. I would hate to find out 3 weeks from now that I had forgotten
and that's why it wasn't working.

-ED

Roger Svensson wrote:
> Did you extract the firmware with version 006 too? I'm just asking since
> I forgot it myself the first time I tested.
>
> --
> Broadcom 4306 doesn't work! I cannot connect to any wireless network
> https://bugs.launchpad.net/bugs/210373
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[f37u5g0d (enovak)]

2 Days ago I was poking around add/remove applications and I found "Windows Wireless Drivers" with the description "Ndiswrapper driver installation tool." Just for shits and giggles I installed it and located the drivers for it. When I restarted the computer wireless worked! I don't know why or how but it does now! I think it must have been included someone in one of the recent updates. (I didn't have to do anything with restricted drivers. In fact I don't even have that in my main menu any more.) So, for what it's worth, I got BCM4306 working under 8.04 using the ndiswrapper utility in add/remove applications.

[Joshua D. Curry (joshua-curry)]

Here is a temp fix that uses the ndiswrapper:

http://blog.roberthallam.org/2008/04/broadcom-4318-ubuntu-hardy-heron-ndiswrapper/

I had to use the gui software manager to remove b43-fwcutter b/c aptitude and apt-get would not remove it. After that, the instructions worked no problem.

You may want a link to the 4306 drivers, I found them here:

http://www.wireless-driver.com/download/broadcom/Broadcom-4306-driver-download.htm

I hope that this gets fixed naively..... I wish that all of these licensing issues could be resolved so I wouldn't have to do this each time that I upgrade ubuntu.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[f37u5g0d (enovak)]

I was able to get by broadcom 4306 to work using ndiswrapper but I had
to have have an updated version of ubuntu 8.04. I am not sure which
update it was but I know that a fresh install of ubuntu 8.04 will not be
able to use ndiswrapper.

On Thu, 2008-08-28 at 23:42 -0500, Leann Ogasawara wrote:
> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
> upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
> appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
> There are one of two ways you should be able to test:
>
> 1) If you are comfortable installing packages on your own, the linux-
> image-2.6.27-* package is currently available for you to install and
> test.
>
> --or--
>
> 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer
> 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4.
> Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.
> You should then be able to test via a LiveCD.
>
> Please let us know immediately if this newer 2.6.27 kernel resolves the
> bug reported here or if the issue remains. More importantly, please
> open a new bug report for each new bug/regression introduced by the
> 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please
> specifically note if the issue does or does not appear in the 2.6.26
> kernel. Thanks again, we really appreicate your help and feedback.
>
> ** Tags added: cft-2.6.27
>
> --
> Broadcom 4306 doesn't work! I cannot connect to any wireless network
> https://bugs.launchpad.net/bugs/210373
> You received this bug notification because you are a direct subscriber
> of the bug.

[stephen (stephenl42)]

Hi, I'm seeing the same problem in 8.04.

As per Leann's suggestion, above, I upgraded to 8.10 Alpha5. The problem is still present for me.

After reboot, I noticed a line in dmesg warning about old drivers, so I went to linuxwireless.org and manually installed the drivers. After further reboot, here are relevant bits of dmesg:

[ 4.355128] b43-pci-bridge 0000:00:0c.0: PCI INT A -> Link[LNK2] -> GSI 10 (level, low) -> IRQ 10
[ 18.669201] b43-phy0: Broadcom 4306 WLAN found
[ 42.770613] input: b43-phy0 as /class/input/input9
[ 42.840153] firmware: requesting b43/ucode5.fw
[ 42.946222] firmware: requesting b43/pcm5.fw
[ 42.998054] firmware: requesting b43/b0g0initvals5.fw
[ 43.006970] firmware: requesting b43/b0g0bsinitvals5.fw
[ 43.128127] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 43.279668] Registered led device: b43-phy0::tx
[ 43.280763] Registered led device: b43-phy0::rx
[ 43.281529] Registered led device: b43-phy0::radio
[ 43.602970] NET: Registered protocol family 17
[ 45.816239] b44: eth0: Link is up at 100 Mbps, full duplex.
[ 45.816266] b44: eth0: Flow control is off for TX and off for RX.
[ 60.670453] NET: Registered protocol family 10
[ 60.674947] lo: Disabled Privacy Extensions
[ 60.680535] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 70.323483] wlan0: authenticate with AP 00:09:5b:69:cb:61
[ 70.520071] wlan0: authenticate with AP 00:09:5b:69:cb:61
[ 70.720163] wlan0: authenticate with AP 00:09:5b:69:cb:61
[ 70.921726] wlan0: authentication with AP 00:09:5b:69:cb:61 timed out

FYI this machine (laptop) is dual-boot with the Other operating system, which works, so I know the AP is configured correctly.

'uname -a' gives:
Linux limpet 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux

At this point I'm not quite sure how to proceed. I'm pretty comfortable with kernel hacking, and willing to try any suggestions/patches/whatever, however I'm new to Ubuntu (and to the bcm4306!) so will need my hand holding.

best regards,
stephen

[stephen (stephenl42)]

okay, to follow-on from my last post. I managed to get things working as follows:

I downloaded the latest 8.10 alpha 6, deleted the old partitions and performed a CLEAN INSTALL.

by default there is NO FIRMWARE installed.

I had to manually follow the instructions on: http://linuxwireless.org/en/users/Drivers/b43#devicefirmware
(b43-cutter utility NOT installed by default)

----------------------------------------------------------------------

Use version 011 of b43-fwcutter.
Download, extract the b43-fwcutter tarball and build it:

wget http://bu3sch.de/b43/fwcutter/b43-fwcutter-011.tar.bz2
tar xjf b43-fwcutter-011.tar.bz2
cd b43-fwcutter-011
make
cd ..

Use version 4.80.53.0 of Broadcom's proprietary driver.
Download and extract the firmware from this driver tarball:

export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
tar xjf broadcom-wl-4.80.53.0.tar.bz2
cd broadcom-wl-4.80.53.0/kmod
sudo ../../b43-fwcutter-011/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.o

----------------------------------------------------------------------

then I did "modprobe -r b43; modprobe b43" then got prompted for key.. but STILL TIMED OUT.

then I followed the excellent instructions from Larry Finger here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182716

I dumped the contents of my SPROM, manually modifed (in my case, this was changing the low-order board flags from 0x000f to 0x000e).

after a reboot, things sprang into life.

So... a heads-up. Whatever kernel is shipping with 8.10alpha6 (2.6.27-3) would still appear to be broken.

My earlier offer to test and debug still stands... for the moment... now that I got this working, I'm going to start using this machine soon... so shout quickly if you want me to test anything :-)

best regards,
stephen

[zeddock (zeddock)]

I am just using 4306/3 on a newly installed release of 8.10.
Seems after a reboot I can not connect to a wireless network that I can see, Using restricted driver.

zeddock

[Luis Davila (luisfer)]

hi, i have a similar problem with my BCM4306 (Dell Latitude D600), but in my case my wireless card is recognized and I can see the networks and at the first time after boot i can connected me to network without problem BUT after some minutes i loss connection and impossible to reconnect, only solution 'reboot'. I use Kubuntu 8.10 with Kernel 2.6.27-8 (same problem even with 2.6.27-7)
the dmesg output is:
~~~~~~~~~~~~~~~~~~~~~~~~~
[ 34.908052] firmware: requesting b43/ucode5.fw
[ 35.003334] firmware: requesting b43/pcm5.fw
[ 35.130271] firmware: requesting b43/b0g0initvals5.fw
[ 35.219630] firmware: requesting b43/b0g0bsinitvals5.fw
[ 35.364045] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 984.415699] wlan0: authenticate with AP 00:0c:f6:48:52:56
[ 984.417313] wlan0: authenticated
[ 984.417332] wlan0: associate with AP 00:0c:f6:48:52:56
[ 984.419360] wlan0: RX AssocResp from 00:0c:f6:48:52:56 (capab=0x411 status=0 aid=2)
[ 984.419378] wlan0: associated
[ 1041.085657] b43-phy0 ERROR: PHY transmission error
[ 1044.213038] b43-phy0 ERROR: PHY transmission error
[ 1044.228048] b43-phy0 ERROR: PHY transmission error
[ 1044.253364] b43-phy0 ERROR: PHY transmission error
[ 1044.261300] b43-phy0 ERROR: PHY transmission error
[ 1044.274102] b43-phy0 ERROR: PHY transmission error
[ 1044.295744] b43-phy0 ERROR: PHY transmission error
[ 1061.204274] wlan0: No ProbeResp from current AP 00:0c:f6:48:52:56 - assume out of range
[ 1062.090604] wlan0: authenticate with AP 00:0c:f6:48:52:56
[ 1062.288282] wlan0: authenticate with AP 00:0c:f6:48:52:56
[ 1062.488072] wlan0: authenticate with AP 00:0c:f6:48:52:56
[ 1062.688255] wlan0: authentication with AP 00:0c:f6:48:52:56 timed out

and the message "assume out of range" is not true in my case because even closer to AP i have the lost connection.

With Hardy (all kernels of hardy) my wireless card works greats, easy and automatically and more (with the hardware assistant) but is not the case for Ibex... It's not the same Firmware:
hardy FW version 351.126
ibex FX version 410.2160
I tested to blacklist b43 and modprobe b43legacy but my card is not recognized.

Another problem, when i test without Knetwork-manager, only with command-line dhclient don't work, So, apparently is not a problem from knetwork-manager...

[Kenrro (kenrro)]

Same problem here, I can see the networks but I'm unable to connect, and it doesn't matter if it the Authentication/Encryption is Enabled or disabled on the router, its always the same result, this is my info:

Laptop hp pavilion ze5500 series,
Ubuntu 8.10 Intrepid Ibex (fresh install with restricted drivers enabled)

$ uname -a
Linux my-laptop 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux

$ lspci | grep 4306
00:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 02)

$ lsmod | grep b43
b43legacy 128156 0
rfkill 17176 3 rfkill_input,b43legacy
mac80211 216820 1 b43legacy
led_class 12164 1 b43legacy
input_polldev 11912 1 b43legacy
ssb 40580 1 b43legacy

$ dmesg | grep b43
[ 3.712092] b43-pci-bridge 0000:00:09.0: enabling device (0000 -> 0002)
[ 3.712504] b43-pci-bridge 0000:00:09.0: PCI INT A -> Link[LNK3] -> GSI 10 (level, low) -> IRQ 10
[ 16.154813] b43legacy-phy0: Broadcom 4306 WLAN found
[ 16.176122] b43legacy-phy0 debug: Found PHY: Analog 1, Type 2, Revision 1
[ 16.176148] b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
[ 16.200147] b43legacy-phy0 debug: Radio initialized
[ 34.859552] input: b43legacy-phy0 as /devices/virtual/input/input8
[ 35.148067] firmware: requesting b43legacy/ucode4.fw
[ 35.194982] firmware: requesting b43legacy/pcm4.fw
[ 35.205596] firmware: requesting b43legacy/b0g0initvals2.fw
[ 35.324252] b43legacy-phy0: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27)
[ 35.400576] b43legacy-phy0 debug: Chip initialized
[ 35.402834] b43legacy-phy0 debug: 30-bit DMA initialized
[ 35.405335] Registered led device: b43legacy-phy0:radio
[ 35.405404] b43legacy-phy0 debug: Wireless interface started
[ 35.415374] b43legacy-phy0 debug: Adding Interface type 2

~$ dmesg | grep wlan0
[ 36.212536] wlan0: authenticate with AP 00:1d:5a:bf:ad:91
[ 36.412822] wlan0: authenticate with AP 00:1d:5a:bf:ad:91
[ 36.612085] wlan0: authenticate with AP 00:1d:5a:bf:ad:91
[ 36.812070] wlan0: authentication with AP 00:1d:5a:bf:ad:91 timed out
... then it repeats...

$ lspci -vvn | grep 43 -A7
00:09.0 0280: 14e4:4320 (rev 02)
 Subsystem: 0e11:00e7
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 64
 Interrupt: pin A routed to IRQ 10
 Region 0: Memory at d0002000 (32-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: b43-pci-bridge
 Kernel modules: ssb

00:0a.0 0607: 1217:6972
 Subsystem: 103c:0850
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 168
--
01:05.0 0300: 1002:4337
 Subsystem: 103c:0850
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B+ DisINTx-
 Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >T...

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[lylepratt (lylepratt)]

Well. It looks like this bug was NEVER FIXED. I just installed 9.10 on the same laptop i was having problems with before (clean install, havnt used the laptop in a year or so). Wifi still has the same issues (can see wireless networks but can't connect).

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Lars Noodén (larsnooden)]

The bugg appears to still be present in Ubuntu 10.04.1 LTS on very old compaq nx9000, it is possible to see a network using

K Menu
 ->System Settings
 ->Network Connections
 ->Wireless
 ->Add
 ->Scan

but not to actually connect to it even after installing b43-fwcutter.

  https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx.

# uname -a
Linux compax 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:12:52 UTC 2010 i686 GNU/Linux

# lspci -vvnn|grep 14e4
00:09.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 02)

# modprobe -l|grep b43
kernel/drivers/net/wireless/b43/b43.ko
kernel/drivers/net/wireless/b43legacy/b43legacy.ko

# lshw -C network
  *-network:0
       description: Network controller
       product: BCM4306 802.11b/g Wireless LAN Controller
       vendor: Broadcom Corporation
       physical id: 9
       bus info: pci@0000:00:09.0
       version: 02
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list
       configuration: driver=b43-pci-bridge latency=64
       resources: irq:10 memory:d0002000-d0003fff
  *-network:1
       description: Ethernet interface
       product: DP83815 (MacPhyter) Ethernet Controller
       vendor: National Semiconductor Corporation
       physical id: 12
       bus info: pci@0000:00:12.0
       logical name: eth0
       version: 00
       serial: 00:0d:9d:44:8e:c5
       size: 100MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list rom ethernet physical tp mii fibre 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=natsemi driverversion=2.1 duplex=full ip=10.123.20.33 latency=90 link=yes maxlatency=52 mingnt=11 multicast=yes port=twisted pair speed=100MB/s
       resources: irq:10 ioport:2c00(size=256) memory:d0007000-d0007fff memory:3c000000-3c00ffff(prefetchable)
  *-network
       description: Wireless interface
       physical id: 2
       logical name: wlan0
       serial: 00:90:4b:43:53:3e
       capabilities: ethernet physical wireless
       configuration: broadcast=yes multicast=yes wireless=IEEE 802.11bg

# dmesg | grep wlan0
[ 14.708392] ADDRCONF(NETDEV_UP): wlan0: link is not ready