The Definitive 9.10 Broadcom Solution Guide

[schmolch]

Doesn't work for me.
As soon as i install the bcm-kernel-source my card is no longer been seen.
Without the bcm-kernel-source it sees it but times out connecting repeatingly.

[blingenfelter]

Thanks for all the info. On my Acer Extensa, at first I had trouble, but after installing both drivers (ending with STA), it worked! I wish it worked ootb, though, like some other distros.
Listed here:

http://linux-programming.suite101.co...adcom-wireless

The BCM43xx has been the bane of my linux experience. Can't wait to upgrade soon to a new laptop.

[PetoB]

Hi all,

I read whole this thread and many more, but still I did not find an answer...
I have DELL studio 1555 with wireless DELL 1397 Mini card
...stupid things is taht i had installed Ubuntu on my USB hard drive and I manage up and run wifi (after manually instalation of restricted driver for broadcom), than I decide to run from internal hard derive...

...I did million of installation, try some magic and so, but I not managed wifi... finally I try to run from USB stick, where I have my Live Installation and I was able to run wifi from USB stick, I reboot and install from USB stick, after installation proces and reboot, I can manage just text mode... that is nothing for me

Now (after last installation) I can open Hardware drivers and i can see my driver for my card (which I use also on USB stick), but I am not able to activate, after activate finally nothing happend and driver is not active

...have somebody any idea? I see this card working on Ubuntu 9.10 ...after a week on front of computer I am sceptic that i will manage it, because I want to learn more about Linux and in the future may by switch only to linux...but for that I need linux with internet and I have no chance to use wired connection...

[mark-e-mark]

Terrific guide; thanks for putting it together. I've had the drivers installed for my BCM4322 on Ubuntu 9.10 for some months now, and I've been attempting to diagnose a "Slow SAMBA" issue. After getting SAMBA to where it's not logging errors and mounts shares reliably, I've finally figured out that the sluggish performance on my home wireless network (XP Server shares) is matched by poor performance on the web. Today I went to a newbie "testmyspeed" site and it told me I should get off dial-up.

Since then, I've been after my STA driver, and I compiled the latest WL driver according to instructions at Broadcom (http://www.broadcom.com/docs/linux_sta/README.txt). Since I'm a Windows guy and barely familiar with Unix, I was surprised that I successfully untarred and compiled the source correctly, but the driver is functioning. I can reboot and jump right on my network.

However, I still have ****-poor network speed. I'm writing this from my dual-boot HP dV4 Pavilion 64 bit where I can't watch my own movies unless I reboot to Vista. That's just not how things should be, so I am asking the community for suggestions. I see that mmmmna had success with a re-install, so I'll try that but I don't hold much hope for it. Does anyone know what else I might try?

[drfurly]

I've installed Linux on my Dell Inspiron 1420 laptop (which runs the BCM4312 wireless card) and completely uninstalled Linux on two separate occasions because I couldn't find a way to make my wireless card work. Finally, after some more refined Google searches I came across this thread and my wireless is up to snuff.

Great guide, I'm glad someone finally made a retard-proof walkthru for me.

[Bobmnh]

Broadcom hardware only. Credit to respective solution providers included below. Feel free to chime in if I've missed something.

Broadcom BCM4311/12/21/22 Hardware (STA driver):
NOTE: ASSUMES FRESH INSTALL. FOR LAPTOPS, ONCE THE SYSTEM REBOOTS AFTER INSTALL, REBOOT AGAIN
AND TOGGLE THE WIRELESS BUTTON (YES, IT COULD BE THAT EASY).

Plug into the network via cable:

1. IF WIRED CONNECTION WORKS:
   
   1. Open System -> Admin -> Update Manager
   2. Check for updates, install, and reboot
   3. After reboot, open System -> Admin -> Hardware Drivers
   4. Look for "Broadcom STA wireless driver";
      
      1. IF DRIVER IS PRESENT AND ACTIVATED:
         
         1. Remove network cable, toggle wireless button, and log into network.
         
         
      2. IF DRIVER IS PRESENT BUT NOT ACTIVATED:
         
         1. Activate and reboot;
         2. After reboot, remove network cable, toggle wireless button, and log into network.
         
         
      3. IF DRIVER IS NOT PRESENT:
         
         1. Open System -> Admin -> Synaptic Pkg Mgr
         2. Search for "bcmwl-kernel-source" (if not available, move to step 2)
         
         
         
         1. Right-click and mark for installation
         2. Apply changes and reboot.
         3. Repeat steps 1.3-1.4.2
         
         
      
      
   
   
2. IF WIRED CONNECTION DOES NOT WORK:
   
   1. From LiveCD (solution provided by jomtois here - edited for clarity):
      
      1. Open Sytem -> Admin -> Synaptic Package Mgr
      2. Ensure 9.10 LiveCD is in the drive
      3. In Synaptic Package Mgr, open Settings -> Repositories -> Ubuntu Software
      4. Check "Installable from CD-ROM/DVD" and close
      5. Reload (disregard connectivity errors)
      6. Search for "bcmwl-kernel-source"
      7. Right-click and mark for installation
      8. Apply changes and reboot
      9. Repeat steps 1.3 thru 1.4.2
      
      
   2. From LiveUSB:
      
      1. Navigate to pool -> main -> d -> dkms
      2. Run "dkms_2.1.0.1-0ubuntu1_all.deb"
      3. Navigate to pool -> restricted -> b -> bcmwl
      4. Run "bcmwl-kernel-source_5.10.91.9+bdcom-0ubuntu4_i386.deb"
      5. Reboot
      6. Repeat steps 2.1.6 thru 2.1.9 and 1.3 thru 1.4.2
      
      
   
   

Broadcom BCM4301/03/06/09 Hardware (B43 driver):
NOTE: IF YOUR CARD IS A BCM4306 REV 2, OR ONLY HAS 802.11B CAPABILITY, IT USES
B43LEGACY. ALL OTHER MODELS USE B43. THE STEPS BELOW WILL 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.
ADDITIONAL INFO HERE. ASSUMES FRESH INSTALL. FOR LAPTOPS, ONCE THE SYSTEM REBOOTS
AFTER INSTALL, REBOOT AGAIN AND TOGGLE THE WIRELESS BUTTON (YES, IT COULD BE THAT
EASY).

Plug into the network via cable:

1. IF WIRED CONNECTION WORKS:
   
   1. Open System -> Admin -> Update Manager
   2. Check for updates, install, and reboot
   3. After reboot, open System -> Admin -> Hardware Drivers
   4. Look for "Broadcom B43 wireless driver";
      
      1. IF DRIVER IS PRESENT AND ACTIVATED:
         
         1. Remove network cable, toggle wireless button, and log into network.
         
         
      2. IF DRIVER IS PRESENT BUT NOT ACTIVATED:
         
         1. Activate and reboot;
         2. After reboot, remove network cable, toggle wireless button, and log into network.
         
         
      3. IF DRIVER IS NOT PRESENT:
         
         1. Open System -> Admin -> Synaptic Pkg Mgr
         2. Search for "b43-fwcutter" (if not available, move to step 2)
         3. Right-click and mark for installation
         4. Apply changes (answer yes when asked "Fetch and install firmware?")
         5. Reboot
         6. Repeat steps 1.3 thru 1.4.2
         
         
      
      
   
   
2. IF WIRED CONNECTION DOES NOT WORK:
   
   1. From LiveCD (based on solution provided by jomtois here - edited for clarity):
      
      1. Open Sytem -> Admin -> Synaptic Package Mgr
      2. Ensure 9.10 LiveCD is in the drive
      3. In Synaptic Package Mgr, open Settings -> Repositories -> Ubuntu Software
      4. Check "Installable from CD-ROM/DVD" and close
      5. Reload (disregard connectivity errors)
      6. Search for "b43-fwcutter"
      7. Right-click and mark for installation
      8. Apply changes (answer yes when asked "Fetch and install firmware?")
      9. Reboot
      10. Repeat steps 1.3 thru 1.4.2
      
      
   2. From LiveUSB:
      
      1. Navigate to pool -> main -> d -> dkms
      2. Run "dkms_2.1.0.1-0ubuntu1_all.deb"
      3. Navigate to pool -> restricted -> b -> bcmwl
      4. Run "bcmwl-kernel-source_5.10.91.9+bdcom-0ubuntu4_i386.deb"
      5. Reboot
      6. Repeat steps 2.1.6 thru 2.1.9 and 1.3 thru 1.4.2
      
      
   
   

Transfer Files from Another Computer
NOTE: IF NECESSARY, THE STA AND B43 PACKAGES CAN BE
DOWNLOADED USING THE LINKS BELOW. BE SURE TO INCLUDE THE
APPROPRIATE DEPENDENCIES.

STA Driver Source
http://packages.ubuntu.com/da/karmic/bcmwl-kernel-source

B43 Driver Source
http://packages.ubuntu.com/karmic/b43-fwcutter

Cheers.

Thank You very much. I just installed Ubuntu yesterday and I couldn't connect with the wireless. I have a Broadcom adapter which didn't have a driver. Update Manager installed 233MB worth of files.

Thanks again.
Bobmnh

[Sacrin]

Hi, new to Linux and the forum. I recently installed 9.10 on two computers - both have broadcom wifi cards. I followed these instructions for both - worked great on my netbook, not so great on the second.

One of my computers (Dell XPS w/ 4322 card & 9.10 64) does not connect at start up. I have to manually delete the automatic connection and re-connect every boot. The connection also sometimes disconnects, and I have to go through the same process. However, when the connection holds, it seems to be at a similar speed to the other computer.

Suggestions??? I saw someone posted a similar problem with their 4322, but I didn't understand what to do or if he had results.

Edit: the other computer seems to have the same problem - getting frustrating. BTW, wifi connection is a WPA through an Edimax N router.

[Canada Lee]

I am running Ubuntu Karmic 9.10 (fresh install) on an Acer Aspire 3000 laptop with a Broadcom BCM4318 Airforce One 54g Rev 02 wireless...

I have wireless connectivity with the B43 driver showing up in the Hardware Drivers application. I have used fwcutter, and can't be certain it completed and downloaded the necessary firmware, as there is a known bug relating to it, where it has a YES / NO question about downloading the firmware, and once selecting YES it exits...without any explanations as to success or failure...search for that fwcutter bug, and you'll know what I mean.

Anyways, what I am experiencing like so many others with broadcom's are experiencing is connectivity with random disconnects. I have been trying to troubleshoot this for months, and I think we need to be digging deeper...not looking on the surface... Here's what I've found out...

Need to have a controlled environment, so...
Laptop is running on AC with battery disconnected to rule out any power saving modes or functions attempting to interfere with operation. Also, screen saver has been deactivated, and in power saving settings it is set while on AC to leave monitor on and never turn it off.

I have a big torrent downloading, and my wifi led light is flashing, and I have System Monitor running to show a graph of SENT & RECEIVED...when I see the LED light stop flashing (sometimes it may be off, or it may be on - but its state will remain constant, as in if its off, it stays off and doesnt fluctuate, if on, it stays on and doesnt fluctuate...and when I say the led may be off and stays in that state, I mean the wifi is on, but the led is blinking on and off to represent data xfer and the light just happened to be in the off state when it got HUNG UP.

When the led light gets stuck in whatever state, I know its about to loose connectivity, so I go to my terminal, and I >> ping -c 1 -I wlan0 www.google.com << and sure enough, the ping fails...so I do a >> sudo ifconfig wlan0 down << and if the led was stuck in the ON state, I will see the led go out, and the network manager starts scanning (it wont connect though till)...I then do a >> sudo ifconfig wlan0 up << and then the led light comes up...and the networking manager is still scanning and connects.

So...you dont have to do a reboot to get back your network connectivity...
So I made a little wireless script to KEEP-ALIVE the connection, and if lost, do the DOWN and UP command...sounds like it'd work you think...but makes me think something else may be causing the wireless to BE IGNORED...

Here's my keep-alive script...
#!/bin/bash
while [ 1 = 1 ]
do
if [[ ! `ping -c 1 -I wlan0 www.google.co.uk` ]]; then
echo "$(date)"
ifconfig wlan0 down
sleep 5s
ifconfig wlan0 up
sleep ${1}s
fi
done

I place it in my /usr/local/bin folder, make it executable...open a term, and run it with
sudo keep-alive 60
the 60 can be whatever you want it to be, it tells it to wait 60 seconds then ping, then wait 60 seconds then ping...it will run till you stop it with a CTRL-C...if a ping fails it will DROP the wlan0 interface, wait 5 seconds and then bring it back UP. It will also echo in the terminal the ping failure and the time and date.

Thing I noticed, the terminal window is open, my keep-alive is running (I even had it echoing the successful pings every 60 secs) and I can see my cursor blinking in the terminal window...but when I notice the wifi led light not blinking, I know it is going to loose connectivity...and the cursor in the terminal has stopped blinking, and the clock on the top panel has stopped updating...everything on the screen is frozen to a snapshot of when the wifi was working...if I hit the mouse touchpad, the cursor in the terminal starts blinking, the clock in the top panel updates, my torrent display updates. Its like the display went to sleep...and me touching the pad woke it...and it wasnt ASLEEP long enough for loss of connectivity, I know this cuz I waited longer before hitting the touchpad, and when that woke it, then I see a bubble saying disconnected from my network...and then the network manager scanning...and it wont connect, then my keep-alive script drops the wlan and brings it up, and then the netman scanning connects...

You have to remember, I have told it not to spin down hard drives, never to turn off or blank the display, nor screensaver.

But I know my keep-alive script was frozen, everything was frozen...no heavy CPU usage, just like asleep. and me touching the pad woke it from that sleep, and it continued where it was before the sleep...

What makes it sleep like that? What components of Ubuntu perform that job? It cant be the wifi driver just stopped communicating to the kernal, cuz me waking it by swiping my finger on the mouse touchpad should not be able to influence a modem communication driver...

On the other hand, a power savings mode, inactivity, screensavers and so on can be influenced by user input to interrupt their behavior.

So even when power savings is off, something is suspending things...and it is not at constant intervals, it is at random intervals. There is no overheating going on here, and the cpu in not throttling. I am using only max of 10% when torrent is dloading. And if there was overheating or throttling, who ever heard of influencing their state by swiping the touchpad!

Anybody know where to look for something that is making the kernal or some other area going to sleep?

[Canada Lee]

Also, I have followed instructions from the following site to set up my firmware, as that site seemed to relate different scenarios for the b43legacy the b43 and the b43xx drivers, while other sites seem to only use the b43 for all scenarios...

http://wireless.kernel.org/en/users/.../b43#fw-b43-lp

I had the same connectivity with random disconnects before using the b43 provided by the Hardware Devices application, and after following that website.

No change in random disconnects...but it never disconnects when I'm at the laptop using it...because my every move keeps the computer in a state of being awake.

Its only once I have left it alone, that it seems to go to sleep and when it does, everything even the screen display, and the wifi led light, just freezes or pauses...and will stay that way...and my keep-alive program wont save it, cuz it has stopped doing pings, cuz its been paused.

I set it to echo the time and date of each successful ping every 60 seconds, and it would, and it would...but then when the wifi led light's state gets stuck, I know the prob is happening again, and sure enough, no more successful pings, no more failed pings being echoe'd to the screen...clock aint updating...touch the pad...everything on the display updates, then a min later a failed ping (3 mins after the last ping shown on screen - a ping should be happening every 60 seconds)...then a bubble for disconnected network...then the netman scanning, then cuz my prog did a DOWN & UP, connection.

But I shouldnt have to be here to wake it from sleep. There is no setting in the BIOS for this.

Someone must have an idea where to look?!

[dushy4]

Broadcom hardware only. Credit to respective solution providers included below. Feel free to chime in if I've missed something.

Broadcom BCM4311/12/21/22 Hardware (STA driver):
NOTE: ASSUMES FRESH INSTALL. FOR LAPTOPS, ONCE THE SYSTEM REBOOTS AFTER INSTALL, REBOOT AGAIN
AND TOGGLE THE WIRELESS BUTTON (YES, IT COULD BE THAT EASY).

Plug into the network via cable:

1. IF WIRED CONNECTION WORKS:
   
   1. Open System -> Admin -> Update Manager
   2. Check for updates, install, and reboot
   3. After reboot, open System -> Admin -> Hardware Drivers
   4. Look for "Broadcom STA wireless driver";
      
      1. IF DRIVER IS PRESENT AND ACTIVATED:
         
         1. Remove network cable, toggle wireless button, and log into network.
         
         
      2. IF DRIVER IS PRESENT BUT NOT ACTIVATED:
         
         1. Activate and reboot;
         2. After reboot, remove network cable, toggle wireless button, and log into network.
         
         
      3. IF DRIVER IS NOT PRESENT:
         
         1. Open System -> Admin -> Synaptic Pkg Mgr
         2. Search for "bcmwl-kernel-source" (if not available, move to step 2)
         
         
         
         1. Right-click and mark for installation
         2. Apply changes and reboot.
         3. Repeat steps 1.3-1.4.2
         
         
      
      
   
   
2. IF WIRED CONNECTION DOES NOT WORK:
   
   1. From LiveCD (solution provided by jomtois here - edited for clarity):
      
      1. Open Sytem -> Admin -> Synaptic Package Mgr
      2. Ensure 9.10 LiveCD is in the drive
      3. In Synaptic Package Mgr, open Settings -> Repositories -> Ubuntu Software
      4. Check "Installable from CD-ROM/DVD" and close
      5. Reload (disregard connectivity errors)
      6. Search for "bcmwl-kernel-source"
      7. Right-click and mark for installation
      8. Apply changes and reboot
      9. Repeat steps 1.3 thru 1.4.2
      
      
   2. From LiveUSB:
      
      1. Navigate to pool -> main -> d -> dkms
      2. Run "dkms_2.1.0.1-0ubuntu1_all.deb"
      3. Navigate to pool -> restricted -> b -> bcmwl
      4. Run "bcmwl-kernel-source_5.10.91.9+bdcom-0ubuntu4_i386.deb"
      5. Reboot
      6. Repeat steps 2.1.6 thru 2.1.9 and 1.3 thru 1.4.2
      
      
   
   

Broadcom BCM4301/03/06/09 Hardware (B43 driver):
NOTE: IF YOUR CARD IS A BCM4306 REV 2, OR ONLY HAS 802.11B CAPABILITY, IT USES
B43LEGACY. ALL OTHER MODELS USE B43. THE STEPS BELOW WILL 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.
ADDITIONAL INFO HERE. ASSUMES FRESH INSTALL. FOR LAPTOPS, ONCE THE SYSTEM REBOOTS
AFTER INSTALL, REBOOT AGAIN AND TOGGLE THE WIRELESS BUTTON (YES, IT COULD BE THAT
EASY).

Plug into the network via cable:

1. IF WIRED CONNECTION WORKS:
   
   1. Open System -> Admin -> Update Manager
   2. Check for updates, install, and reboot
   3. After reboot, open System -> Admin -> Hardware Drivers
   4. Look for "Broadcom B43 wireless driver";
      
      1. IF DRIVER IS PRESENT AND ACTIVATED:
         
         1. Remove network cable, toggle wireless button, and log into network.
         
         
      2. IF DRIVER IS PRESENT BUT NOT ACTIVATED:
         
         1. Activate and reboot;
         2. After reboot, remove network cable, toggle wireless button, and log into network.
         
         
      3. IF DRIVER IS NOT PRESENT:
         
         1. Open System -> Admin -> Synaptic Pkg Mgr
         2. Search for "b43-fwcutter" (if not available, move to step 2)
         3. Right-click and mark for installation
         4. Apply changes (answer yes when asked "Fetch and install firmware?")
         5. Reboot
         6. Repeat steps 1.3 thru 1.4.2
         
         
      
      
   
   
2. IF WIRED CONNECTION DOES NOT WORK:
   
   1. From LiveCD (based on solution provided by jomtois here - edited for clarity):
      
      1. Open Sytem -> Admin -> Synaptic Package Mgr
      2. Ensure 9.10 LiveCD is in the drive
      3. In Synaptic Package Mgr, open Settings -> Repositories -> Ubuntu Software
      4. Check "Installable from CD-ROM/DVD" and close
      5. Reload (disregard connectivity errors)
      6. Search for "b43-fwcutter"
      7. Right-click and mark for installation
      8. Apply changes (answer yes when asked "Fetch and install firmware?")
      9. Reboot
      10. Repeat steps 1.3 thru 1.4.2
      
      
   2. From LiveUSB:
      
      1. Navigate to pool -> main -> d -> dkms
      2. Run "dkms_2.1.0.1-0ubuntu1_all.deb"
      3. Navigate to pool -> restricted -> b -> bcmwl
      4. Run "bcmwl-kernel-source_5.10.91.9+bdcom-0ubuntu4_i386.deb"
      5. Reboot
      6. Repeat steps 2.1.6 thru 2.1.9 and 1.3 thru 1.4.2
      
      
   
   

Transfer Files from Another Computer
NOTE: IF NECESSARY, THE STA AND B43 PACKAGES CAN BE
DOWNLOADED USING THE LINKS BELOW. BE SURE TO INCLUDE THE
APPROPRIATE DEPENDENCIES.

STA Driver Source
http://packages.ubuntu.com/da/karmic/bcmwl-kernel-source

B43 Driver Source
http://packages.ubuntu.com/karmic/b43-fwcutter

Cheers.

thanks a lot dear,,,,,,, i tried to activate drivers for my lenovo s10 2 2-3 onths back. i dont see this page and after days of hassle,i failed. today i come across your post,,,do exactly as you said and finally,,,,,,,,wifi works.

(though while insalling bcmwl-kernel-source it failed to get 3 packages which i installed manually).

thanks a ton again,,,,,,,,