This article details how to install and setup a Broadcom wireless network device.
- 1 History
- 2 Driver selection
- 3 Installation
- 4 Troubleshooting
- 4.1 Setting broadcom-wl in monitor mode
- 4.2 Device inaccessible after kernel upgrade
- 4.3 Device with broadcom-wl driver not working/showing
- 4.4 Interfaces swapped with broadcom-wl
- 4.5 Interface is showing but not allowing connections
- 4.6 Suppressing console messages
- 4.7 Device BCM43241 not detected
- 4.8 Device BCM43241 EFI Vars
- 4.9 Connection is unstable with some routers
- 4.10 No 5GHz for BCM4360 (14e4:43a0) / BCM43602 (14e4:43ba) devices
- 4.11 Device works intermittently
- 4.12 SSH freeze for BCM4331 with b43
Broadcom has a noted history with its support for Wi-Fi devices regarding GNU/Linux. For a good portion of its initial history, Broadcom devices were either entirely unsupported or required the user to tinker with the firmware. The limited set of wireless devices that were supported were done so by a reverse-engineered driver. The reverse-engineered
b43 driver was introduced in the 2.6.24 kernel.
In August 2008, Broadcom released the 802.11 Linux STA driver officially supporting Broadcom wireless devices on GNU/Linux. This is a restrictively licensed driver and it does not work with hidden ESSIDs, but Broadcom promised to work towards a more open approach in the future.
In September 2010, Broadcom released a fully open source driver. The brcm80211 driver was introduced in the 2.6.37 kernel and in the 2.6.39 kernel it was sub-divided into the
The types of available drivers are:
|brcm80211||Kernel driver mainline version (recommended)|
|b43||Kernel driver reverse-engineered version|
|broadcom-wl||Broadcom driver with restricted license|
To know what driver(s) are operable on the computer's Broadcom wireless network device, the device ID and chipset name will need to be detected. Cross-reference them with the driver list of supported brcm80211 and b43 devices.
$ lspci -vnn -d 14e4:
The kernel contains two built-in open-source drivers: brcmfmac for native FullMAC and brcmsmac for mac80211-based SoftMAC. They should be automatically loaded when booting.
- brcmfmac supports newer chipsets, and supports AP mode, P2P mode, or hardware encryption.
- brcmsmac only supports old chipsets like BCM4313, BCM43224, BCM43225.
Two reverse-engineered open-source drivers are built-in to the kernel: b43 and b43legacy. b43 supports most newer Broadcom chipsets, while the b43legacy driver only supports the early BCM4301 and BCM4306 rev.2 chipsets. To avoid erroneous detection of your WiFi card's chipset, blacklist the unused driver.
Both of these drivers require non-free firmware to function. InstallAUR, AUR, or AUR depending on the chipset.
- If unsure which firmware package you need, check the output of
dmesgand search for "b43". If you see a message like
Loading firmware b43/ucode4.fw, you need either AUR or AUR. If you see a message like
Loading firmware b43legacy/ucode4.fw, you need the AUR package.
- BCM4306 rev.3, BCM4311, BCM4312 and BCM4318 rev.2 have been noticed to experience problems with b43-firmware. Use AUR or AUR for these cards instead.
- BCM4331 noticed to have problems with b43-firmware-classic. Use AUR for this card instead, or switch to the mentioned below for a more stable experience.
There are two variants of the restrictively licensed driver:
- the regular variant:
- the DKMS variant:
- is kernel agnostic. This means it supports different kernels you may use (e.g. AUR).
- is kernel-release agnostic, too. It will be automatically rebuilt after every kernel upgrade or fresh installation. If you use or another kernel release dependant variant (e.g. AUR), it may happen that kernel upgrades break wireless from time to time until the packages are in sync again.
- will need the package for the installed kernel(s) in order to build the module. Those packages are optional to the DKMS package and will need to be installed manually.
An Internet connection is the ideal way to install the broadcom-wl driver; many newer laptops with Broadcom cards forgo Ethernet ports, so a USB Ethernet adapter or Android tethering may be helpful. If you have neither, you'll need to first install the group during installation. Then, use another Internet-connected computer to download and the driver tarball from the AUR, and install them in that order.
Install the appropriate driver for your system architecture from Broadcom's website. After this, to avoid driver/module collisions with similar modules and make the driver available, do:
# rmmod b43 # rmmod ssb # modprobe wl
The wl module should automatically load lib80211 or lib80211_crypt_tkip otherwise they will have to be manually loaded.
If the driver does not work at this point, you may need to update dependencies:
# depmod -a
Setting broadcom-wl in monitor mode
Monitor mode is used to capture 802.11 frames over the air. This can be useful for diagnosing issues on a network or testing the security of your wireless network. Often, monitor mode is required to capture certain frames for wireless penetration testing, but it may be unethical or even illegal to capture frames on any network you do not own, manage or have permission to perform penetration testing against.
To set broadcom-wl in monitor mode you have to set 1 to
# echo 1 > /proc/brcm_monitor0
It will create a new network interface called
To work in monitor mode, use this newly created network interface.
Device inaccessible after kernel upgrade
Since the 3.3.1 kernel the bcma module was introduced. If using a brcm80211 driver be sure it has not been blacklisted. It should be blackisted if using a b43 driver.
If you are using, uninstall and reinstall it after upgrading your kernel or switch to package.
Device with broadcom-wl driver not working/showing
Be sure the correct modules are blacklisted and occasionally it may be necessary to blacklist the brcm80211 drivers if accidentally detected before the wl driver is loaded. Furthermore, update the modules dependencies
depmod -a, verify the wireless interface with
ip addr, kernel upgrades will require an upgrade of the non-DKMS package.
Interfaces swapped with broadcom-wl
Users of the broadcom-wl driver may find their Ethernet and Wi-Fi interfaces have been swapped. See Network configuration#Network interfaces for an answer.
Interface is showing but not allowing connections
Append the following kernel parameter:
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
To disable those messages, increase the loglevel of printk messages that get through to the console - see Silent boot#sysctl.
Device BCM43241 not detected
This device will not display with either
lsusb; there is no known solution yet.
Device BCM43241 EFI Vars
As per the driver page it may be necessary to copy the efi vars before the driver will operate correctly. However the expected path depends on your system.
$ dmesg | grep bcrm
... Direct firmware load for bcrm/your driver.your device failed with error -2
Write the efi vars into the referenced location, e.g. on a thinkpad tablet:
$ cat /sys/firmware/efi/efivars/nvram-74b00bd9-805a-4d61-b51f-43268123d113 > /lib/firmware/brcm/brcmfmac43241b5-sdio.LENOVO-20C1002PUK.txt
Connection is unstable with some routers
If no other approaches help, install previous driver version., or use a
No 5GHz for BCM4360 (14e4:43a0) / BCM43602 (14e4:43ba) devices
Issue appears to be linked to a channel issue. Changing the wireless channel to a lower channel number (like 40 or, if your router show MHz instead of channel numbers, like 5200 MHz or 5280 MHz) seems to allow connection to 5GHz bands. If your router has the same SSID for the 2.4GHZ and 5GHZ, this can fix problems with your wireless connection being unstable or very slow.
Device works intermittently
In some cases (e.g. using BCM4331 and rfkill.AUR), wifi connection works intermittently. One way to fix this is to check if the card is hard-blocked or soft-blocked by kernel, and if it is, unblock it with
SSH freeze for BCM4331 with b43
TheAUR driver has been observed hanging in ssh sessions with BCM4331. Installing and removing b43 solves it.