- 1 Introduction
- 2 Determine which driver you need/can use
- 3 Getting the driver
- 4 Troubleshooting
- 4.1 Wi-Fi card does not seem to even exist
- 4.2 Wi-Fi card does not work or show up after kernel upgrade (brcmsmac)
- 4.3 Wi-Fi card does not work/show up (broadcom-wl)
- 4.4 Interfaces swapped (broadcom-wl)
- 4.5 The b43 driver and Linux 3.8+
- 4.6 Suppressing console messages
- 4.7 Interface is showing but does not allow connections
- 4.8 Miscellaneous user notes
Broadcom has been notorious in its support for its Wi-Fi cards on GNU/Linux. Until recently, most Broadcom chips were either entirely unsupported or required the user to tinker with firmware. A limited set of wireless chips were supported by various reverse-engineered drivers (
b43, etc.). The reverse-engineered b43 drivers have been in the kernel since 2.6.24.
In August 2008, Broadcom released the 802.11 Linux STA driver officially supporting Broadcom wireless hardware on GNU/Linux. These are restrictively licensed drivers, but Broadcom promised to work towards a more open approach in the future. Further, they do not work with hidden ESSIDs.
In September 2010, Broadcom finally released fully open source drivers for its hardware. This driver, brcm80211, has been included into the kernel since 2.6.37. With the release of 2.6.39, these drivers have been renamed to
At the time of writing, there are three choices for users with Broadcom Wi-Fi chipsets:
|brcmsmac/brcmfmac||Open-source kernel driver|
|b43||Reverse-engineered kernel driver|
|broadcom-wl||Proprietary Broadcom STA driver|
Determine which driver you need/can use
First, determine your card's PCI-ID. Type the following (case-sensitive) command into a console:
$ lspci -vnn | grep 14e4:
Getting the driver
brcm80211 drivers are included in the kernel. They are named
brcmsmac for PCI cards and
brcmfmac for SDIO devices.
These drivers should be automatically loaded during start-up and no further action should be required of the user. If the driver does not load automatically, simply load it manually.
The drivers are included in the kernel since 2.6.24.
Loading the b43/b43legacy kernel module
Verify which module you need by looking up your device here. You can also check by computer model here. Blacklist the other module (either
b43legacy) to prevent possible problems/confusion. For instructions, see Kernel_modules#Blacklisting.
Install the appropriate AUR.AUR or AUR package from the
If you have a low-power version of a b43-supported device, you will need to install special firmware. A quick way to check whether you have a low-power chip is by running
lspci | grep Broadcom | grep LP-PHY. You can install it by downloading the appropriate package and using
b43-fwcutter as outlined below, or by using this installation script.
To install the LP-PHY firmware, perform the following:
curl -LO http://downloads.openwrt.org/sources/broadcom-wl-184.108.40.206.tar.bz2 tar xjf broadcom-wl-220.127.116.11.tar.bz2 cd broadcom-wl-18.104.22.168/linux b43-fwcutter -w /lib/firmware wl_apsta.o
After installing the firwmare, you can now configure your device.
Loading the wl kernel module
wl module may need to be manually loaded if there are other usable modules present. Before loading the
wl module, remove the
b43 or other module that may have been automatically loaded instead:
# rmmod b43
ssb, if loaded:
# rmmod ssb
# modprobe wl
wl module should automatically load
lib80211_crypt_tkip. Check with
lsmod to see if this is the case. If not, you may need to add one of those two modules as well.
# modprobe lib80211
# modprobe lib80211_crypt_tkip
If you installed the driver directly from Broadcom, you may also need to update the dependencies:
# depmod -a
To make the module load at boot, refer to Kernel modules.
You can also blacklist other modules (to prevent them from interfering) in
/etc/modprobe.d/modprobe.conf. To blacklist a module, refer to Kernel modules#Blacklisting.
Wi-Fi card does not seem to even exist
Some users with newer cards like the Broadcom BCM43241 will experience an issue where lspci or lsusb will not show any trace of the card. A solution to this will be posted when found.
Wi-Fi card does not work or show up after kernel upgrade (brcmsmac)
This is caused by the kernel using the
bcma module instead of the
brcmsmac module. The solution is to blacklist the
bcma module. For instructions, see Kernel_modules#Blacklisting.
Wi-Fi card does not work/show up (broadcom-wl)
Check if you are loading the correct modules. You may need to blacklist the
ssb kernel modules to prevent them from loading automatically. For instructions, see Kernel_modules#Blacklisting.
Check if you updated your module dependencies:
# depmod -a
- Verify that your wireless interface(s) appear using
- You may need to restart your machine to see the device appear in
- If you have recently upgraded your kernel, you need to rebuild the
broadcom-wlpackage with the new kernel installed to update the module.
Interfaces swapped (broadcom-wl)
Users of the
broadcom-wl driver may find their Ethernet and Wi-Fi interfaces have been swapped. See Network configuration#Device_names for solution.
The b43 driver and Linux 3.8+
The b43 driver has some major issues starting with the release of Linux 3.8+, namely that you are unable to see / connect to some access points.
Solution: Try the latest broadcom-wl driver (version 6+), see above.
Suppressing console messages
You may continuously get some verbose and annoying messages during the boot, similar to
phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement) phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement) enabled, active
These do not seem to be suppressible via normal means, such as setting
/etc/systemd/journald.conf. To hide them, you must lower the level at which
dmesg messages are printed to the console. This can be done on start-up by creating a simple systemd service.
Create a file in
brcms_suppression.service or something similar:
[Unit] Description=Broadcom console message suppression script [Service] Type=oneshot RemainAfterExit=yes ExecStart=/bin/sh -c 'dmesg -n 3' [Install] WantedBy=multi-user.target
Like all other systemd services, you can then enable it with
# systemctl enable brcms_suppression
Interface is showing but does not allow connections
Append the following to your kernel command line:
Miscellaneous user notes
- In my Dell Inspiron Laptop, I have a Broadcom BCM4401 Ethernet card and a Broadcom BCM4328 wireless card. If I just remove
b43, I can load the
wldriver, but no wireless card shows up. However, if I first remove the
ssb) driver for my Ethernet card, and then load the
wldriver, I get a wireless device using the name eth0. Afterwards, I can load
b44again, to have an Ethernet eth1 device.
- I could not get the BCM4313 chip on a Lenovo B560 to work before following these steps:
- "Load defaults" in the BIOS. After that, the wireless was working under MS Windows. There are not many options in there, so I do not know what the reset may have changed, but it did the trick.
- Blacklist the
acer_wmimodule. For testing, you can add the following to the kernel line in GRUB:
- I have found that to get the
wldrivers working for the Broadcom 4313 chip, you need to blacklist
- --Admiralspark, 20 June 2011
- If you notice slow wireless speeds when your laptop/netbook is not connected to AC power, you may need to disable Wi-Fi power management by adding the following line (assuming wlan0 is your wireless device)
iwconfig wlan0 power offto
/etc/rc.localand create an empty file
/etc/pm/power.d/wireless. In case you also experience interface swapping (discussed above), you might want to add another line for the second interface name as well. The command will have no effect on the wired interface.
- --Tom.yan, 16 August 2011
- In my case on a HP pavilion netbook DM1 with a BCM4313 chip, with the original kernel brcmsmac driver, the LED didn't work, the power was awful, and it kept loosing the signal all the time, unless very close to the Wi-Fi hotspot. The last Broadcom driver
wlsolved everything. So in some cases, it's actually better than the kernel driver. However, I had to install it in the initramfs image, along with lib80211 and lib80211_crypt_tkip to avoid a recurring kernel panic.
- --Ivanoff, 18 March 2012 *Edit* It's all solved with the latest kernel versions. --Ivanoff (talk) 14:19, 14 December 2013 (UTC)
- On a similar HP DM1 netbook I found the brcmsmac driver did not work either. The kernel panic can also be solved by blacklisting the brcmsmac, b43 and wl drivers. In rc.local you can
modprobe wlwithout problems. On a sidenote: I get hard lockups, without any way to debug because there is nothing in kernel.log. Not sure if related to the wl driver though.
- --Wilco, 5 May 2012
- Likewise, my HP Pavilion g7-1374ca also had problems with stock kernel drivers. I downloaded Broadcom tarball, but it wouldn't compile in 3.4.3. I removed the #include <asm/system.h> line and commented out a line referencing .ndo_set_multicast_list (there's only one). Then I was able to compile and load the module for a 100% strength signal, no lockups so far.
- On a Dell Inspiron N5110 with BCM4313, when the wireless was hardware-off, the system would always hang at boot with the kernel
brcmsmacdriver. Using the
broadcom-wldriver the problem was solved.
- --Nplatis, 14 October 2012
- On a Dell M4700 with BCM4313 got hideously slow "performance" with default driver -- switched to broadcom-wl and got near advertised link rate speed (65 to 72 Mb/sec)...until restarting, then was not able to associate with wireless access point. The solution was to blacklist the kernel modules
- --virtualeyes, 23 February 2013
- On a Lenovo G580 mounting a BCM4313 the proprietary driver module kept crashing because some dependencies were unsatisfied (the same problem found by Ivanoff). What worked for me was to put a file in /etc/modprobe.d/ with the following content:
blacklist brcmsmac blacklist bcma softdep wl pre: lib80211_crypt_tkip lib80211_crypt_ccmp lib80211_crypt_wep
- --zarel, 21 June 2013
- On MacBook Pro late 2013 (MacBookPro11,1) with BCM4360 the proprietary STA driver loses connection after running iwconfig (and possibly other software that calls iw_get_ext(..., ..., SIOCGIWTXPOW, ...)) with error messages
kernel: ERROR @wl_dev_intvar_get : error (-1) kernel: ERROR @wl_cfg80211_get_tx_power : error (-1)
Here's a dirty workaround for the kernel
--- /tmp/wireless.h 2014-05-02 04:38:22.403321811 +0400 +++ /usr/src/linux/include/uapi/linux/wireless.h 2014-05-02 04:29:15.291996332 +0400 @@ -283,7 +283,7 @@ #define SIOCSIWFRAG 0x8B24 /* set fragmentation thr (bytes) */ #define SIOCGIWFRAG 0x8B25 /* get fragmentation thr (bytes) */ #define SIOCSIWTXPOW 0x8B26 /* set transmit power (dBm) */ -#define SIOCGIWTXPOW 0x8B27 /* get transmit power (dBm) */ +//#define SIOCGIWTXPOW 0x8B27 /* get transmit power (dBm) */ #define SIOCSIWRETRY 0x8B28 /* set retry limits and lifetime */ #define SIOCGIWRETRY 0x8B29 /* get retry limits and lifetime */ @@ -294,6 +294,8 @@ #define SIOCSIWPOWER 0x8B2C /* set Power Management settings */ #define SIOCGIWPOWER 0x8B2D /* get Power Management settings */ +#define SIOCGIWTXPOW SIOCGIWPOWER + /* WPA : Generic IEEE 802.11 informatiom element (e.g., for WPA/RSN/WMM). * This ioctl uses struct iw_point and data buffer that includes IE id and len * fields. More than one IE may be included in the request. Setting the generic
- --sbar, 03 May 2014
- On Ahtec PBL01 with wireless controller BCM4313 (using kernel 3.11.0-12 and brcmsmac module) half of times I cannot connect to home wireless network. However I can connect to other networks, for example if I setup my smartphone as access point. What is more confusing is that after connecting to my smartphone network I can switch to my home network and it will connect fine.