Difference between revisions of "Broadcom wireless"

From ArchWiki
Jump to: navigation, search
m (Wi-Fi card does not seem to even exist: mark for expansion)
m (Troubleshooting)
 
(84 intermediate revisions by 37 users not shown)
Line 1: Line 1:
 +
[[Category:Wireless networking]]
 +
[[ja:Broadcom ワイヤレス]]
 
[[zh-CN:Broadcom wireless]]
 
[[zh-CN:Broadcom wireless]]
[[Category:Wireless Networking]]
+
{{Related articles start}}
== Introduction ==
+
{{Related|Wireless}}
 +
{{Related articles end}}
 +
This article details how to install and setup a Broadcom wireless network device.
  
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 ({{ic|brcm4xxx}}, {{ic|b43}}, etc.). The reverse-engineered [http://wireless.kernel.org/en/users/Drivers/b43 {{ic|b43}}] drivers have been in the kernel since 2.6.24.
+
== History ==
  
In August 2008, Broadcom released the [http://www.broadcom.com/support/802.11/linux_sta.php 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.
+
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 {{ic|b43}} driver was introduced in the 2.6.24 kernel.
  
In September 2010, Broadcom [http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418 finally released] fully open source drivers for its hardware. This driver, [http://wireless.kernel.org/en/users/Drivers/brcm80211 {{ic|brcm80211}}], has been included into the kernel since 2.6.37. With the release of 2.6.39, these drivers have been renamed to {{ic|brcmsmac}} and {{ic|brcmfmac}}.
+
In August 2008, Broadcom released the [http://www.broadcom.com/support/802.11/linux_sta.php 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.
  
At the time of writing, there are three choices for users with Broadcom Wi-Fi chipsets:
+
In September 2010, Broadcom [http://thread.gmane.org/gmane.linux.kernel.wireless.general/55418 released] a fully open source driver. The [http://wireless.kernel.org/en/users/Drivers/brcm80211 brcm80211] driver was introduced in the 2.6.37 kernel and in the 2.6.39 kernel it was sub-divided into the {{ic|brcmsmac}} and {{ic|brcmfmac}} drivers.
  
{| class="wikitable" border="1" cellpadding="5" cellspacing="0"
+
The types of available drivers are:
! Driver !! Description
+
 
 +
{| class="wikitable"
 +
! Driver     !! Description
 
|-
 
|-
|brcmsmac/brcmfmac || Open source kernel driver
+
| brcm80211  || Kernel driver open-source version
 
|-
 
|-
|b43 || Reversed engineered kernel driver
+
| b43         || Kernel driver reverse-engineered version
 
|-
 
|-
|broadcom-wl || Proprietary Broadcom STA driver
+
| broadcom-wl || Broadcom driver restricted-license
 
|}
 
|}
  
== Determine which driver you need/can use ==
+
== Driver selection ==
  
First, determine your card's [[Wikipedia:PCI_configuration_space|PCI-ID]]. Type the following (case-sensitive) command into a console:
+
To know what driver(s) are operable on the computer's Broadcom wireless network device, the [[Wikipedia:PCI configuration space|device ID]] and chipset name will need to be detected. Cross-reference them with the driver list of supported [https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#supported_chips brcm80211] and [https://wireless.wiki.kernel.org/en/users/Drivers/b43#list_of_hardware b43] devices.
$ lspci -vnn | grep 14e4:
+
  
Then check your card against this [http://linuxwireless.org/en/users/Drivers/b43#Supported_devices list of supported b43 devices] and this [http://linuxwireless.org/en/users/Drivers/brcm80211#Supported_Chips list of supported brcm80211 devices].
+
$ lspci -vnn -d 14e4:
  
== Getting the driver ==
+
== Installation ==
  
=== brcmsmac/brcmfmac ===
+
=== brcm80211 ===
The {{ic|brcm80211}} drivers are included in the kernel. They are named {{ic|brcmsmac}} for PCI cards and {{ic|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 [[Kernel modules#Loading|load]] it manually.
+
The kernel contains two built-in open-source drivers: '''brcmsmac''' for PCI backends and '''brcmfmac''' for SDIO/USB backends. They should be automatically loaded when booting.
  
{{Note|1=Since {{pkg|linux}}>=3.3.1, the {{ic|brcmsmac}} driver depends on the {{ic|bcma}} module; therefore, make sure the {{ic|bcma}} module is not [[Kernel_modules#Blacklisting|blacklisted]].}}
+
=== b43 ===
  
{{Note|[http://wireless.kernel.org/en/users/Drivers/brcm80211 wireless.kernel.org] states that brcm80211 does not support older PCI/PCI-E chips with SSB backplane.}}
+
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, [[Kernel_modules#Blacklisting|blacklist]] the unused driver.
  
=== b43/b43legacy ===
+
Both of these drivers require non-free firmware to function. Install {{aur|b43-firmware}}, {{aur|b43-firmware-classic}} or {{aur|b43-firmware-legacy}} from the [[AUR]].
The drivers are included in the kernel since 2.6.24.
+
  
==== Loading the b43/b43legacy kernel module ====
+
{{Note|
Verify which module you need by looking up your device [http://wireless.kernel.org/en/users/Drivers/b43#Known_PCI_devices here]. You can also check by computer model [http://linuxwireless.org/en/users/Drivers/b43/devices here]. Blacklist the other module (either {{ic|b43}} or {{ic|b43legacy}}) to prevent possible problems/confusion. For instructions, see [[Kernel_modules#Blacklisting]].
+
* BCM4306 rev.3, BCM4311, BCM4312 noticed to have problems with '''b43-firmware'''. Use {{aur|b43-firmware-classic}} for these cards instead.
 +
* BCM4331 noticed to have problems with '''b43-firmware-classic'''. Use {{aur|b43-firmware}} for this card instead.
 +
}}
  
Install the appropriate {{AUR|b43-firmware}} or {{AUR|b43-firmware-legacy}} package from the [[AUR]].
+
=== broadcom-wl ===
  
You can now configure your device.
+
Install {{aur|broadcom-wl}} or its [[DKMS]] variant {{aur|broadcom-wl-dkms}} from the [[AUR]] for the restrictively licensed driver.
  
{{Note|1=If the b43 module appears to be loaded and functional but the device is inaccessible, you may need to [[Kernel_modules#Blacklisting|blacklist]] the {{ic|bcma}} module.  See [[Broadcom_wireless#Wi-Fi_card_does_not_work_or_show_up_after_kernel_upgrade_.28brcmsmac.29|Section 4.1]]. If that does not help, you might have to recompile the kernel with the {{ic|CONFIG_B43_BCMA_EXTRA}} option set to use b43. This option was introduced to avoid race conditions between the modules and is at least needed for cards with the BCM4322, BCM43224 and BCM43225 chipsets.}}
+
{{Tip|If you use {{AUR|broadcom-wl}}, kernel upgrades may break wireless from time to time, and you may need to uninstall & reinstall the package. Using {{AUR|broadcom-wl-dkms}} helps avoid this.}}
  
=== broadcom-wl ===
+
==== Offline installation ====
{{Warning|Even though this driver has matured a lot throughout the years and works quite well now, its usage is recommended only when neither of the two open-source drivers support your device. Please refer to project [http://linuxwireless.org/en/users/Drivers/b43/#Supported_devices b43's] page for list of supported devices.}}
+
For users of the {{ic|broadcom-wl}} driver, there is a PKGBUILD available in the [[Arch User Repository|AUR]] named {{AUR|broadcom-wl}}. There is also a newer version available (supporting more recent cards), see {{AUR|broadcom-wl-dkms}}.
+
  
==== Loading the wl kernel module ====
+
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 {{grp|base-devel}} group during installation. Then, use another Internet-connected computer to download {{pkg|linux-headers}} and the driver tarball from the AUR, and install them in that order.
The {{ic|wl}} module may need to be manually loaded if there are other usable modules present. Before loading the {{ic|wl}} module, remove the {{ic|b43}} or other module that may have been automatically loaded instead:
+
# rmmod b43
+
  
Also unload {{ic|ssb}}, if loaded:
+
==== Manually ====
# rmmod ssb
+
  
{{Note|Failure to unload {{ic|ssb}} may result in the wireless interface not being created.}}
+
{{Warning|This method is not recommended. Drivers that are un-tracked can become problematic or nonfunctional on system updates.}}
  
Load the {{ic|wl}} module
+
Install the appropriate driver for your system architecture from [https://www.broadcom.com/support/?gid=1 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
 
  # modprobe wl
  
The {{ic|wl}} module should automatically load {{ic|lib80211}} or {{ic|lib80211_crypt_tkip}}. Check with {{ic|lsmod}} to see if this is the case. If not, you may need to add one of those two modules as well.
+
The ''wl'' module should automatically load ''lib80211'' or ''lib80211_crypt_tkip'' otherwise they will have to be manually loaded.
# modprobe lib80211
+
  
or
+
If the driver does not work at this point, you may need to update dependencies:
# modprobe lib80211_crypt_tkip
+
  
If you installed the driver directly from Broadcom, you may also need to update the dependencies:
 
 
  # depmod -a
 
  # depmod -a
  
To make the module load at boot, refer to [[Kernel modules]].
+
To make the module load at boot, refer to [[Kernel modules]]. It is recommending that you [[Kernel_modules#Blacklisting|blacklist]] conflicting modules.
  
You can also blacklist other modules (to prevent them from interfering) in {{ic|/etc/modprobe.d/modprobe.conf}}. To blacklist a module, refer to [[Kernel modules#Blacklisting]].
+
== Troubleshooting ==
  
{{Note|Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] does not work with blacklisting {{ic|b43}} and {{ic|ssb}}.}}
+
=== Setting broadcom-wl in monitor mode ===
  
== Troubleshooting ==
+
To set broadcom-wl in monitor mode you have to set 1 to {{ic|/proc/brcm_monitor0)}}:
=== Wi-Fi card does not seem to even exist ===
+
  
{{Expansion|no solution provided}}
+
# echo 1 > /proc/brcm_monitor0
  
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.
+
It will create a new network interface called {{ic|prism0}}.
  
=== Wi-Fi card does not work or show up after kernel upgrade (brcmsmac) ===
+
To work in monitor mode, use this newly created network interface.
  
This is caused by the kernel using the {{ic|bcma}} module instead of the {{ic|brcmsmac}} module. The solution is to blacklist the {{ic|bcma}} module. For instructions, see [[Kernel_modules#Blacklisting]].
+
=== Device inaccessible after kernel upgrade ===
{{Note|This affects only Linux kernels 3.0, 3.1, and 3.2. Since kernel 3.3, the {{ic|brcmsmac}} module actually uses {{ic|bcma}}, so {{ic|bcma}} needs to be unblacklisted or the Wi-Fi interface will not appear.}}
+
  
=== Wi-Fi card does not work/show up (broadcom-wl) ===
+
Since the 3.3.1 kernel the '''bcma''' module was introduced. If using a '''brcm80211''' driver be sure it has not been [[Kernel_modules#Blacklisting|blacklisted]]. It should be blackisted if using a '''b43''' driver.
Check if you are loading the correct modules. You may need to blacklist the {{ic|brcm80211}}, {{ic|b43}}, and {{ic|ssb}} kernel modules to prevent them from loading automatically. For instructions, see [[Kernel_modules#Blacklisting]].
+
  
{{Note|You may not have to blacklist the {{ic|brcm80211}} driver; although as of 2011-06-20, it will still default to loading the {{ic|brcm80211}} module before the {{ic|wl}} driver, which prevents {{ic|wl}} from being used.}}
+
If you are using {{aur|broadcom-wl}}, uninstall and reinstall it after upgrading your kernel.
  
Check if you updated your module dependencies:
+
=== Device with broadcom-wl driver not working/showing ===
# depmod -a
+
  
* Verify that your wireless interface(s) appear using {{ic|ip addr}}.
+
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 {{ic|depmod -a}}, verify the wireless interface with {{ic|ip addr}}, kernel upgrades will require an upgrade of the non-[[DKMS]] package.
* You may need to restart your machine to see the device appear in {{ic|iwconfig}} or {{ic|ip addr}}.
+
* If you have recently upgraded your kernel, you need to rebuild the {{ic|broadcom-wl}} package with the new kernel installed to update the module.
+
  
=== Interfaces swapped (broadcom-wl) ===
+
=== Interfaces swapped with broadcom-wl ===
Users of the {{ic|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+ ===
+
Users of the broadcom-wl driver may find their Ethernet and Wi-Fi interfaces have been swapped. See [[Network configuration#Device names|device naming]] for an answer.  
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.
+
=== Interface is showing but not allowing connections ===
 +
 
 +
Append the following [[kernel parameter]]:
 +
 
 +
b43.allhwsupport=1
  
 
=== Suppressing console messages ===
 
=== Suppressing console messages ===
Line 123: Line 119:
 
  enabled, active
 
  enabled, active
  
These do not seem to be suppressible via normal means, such as setting {{ic|MaxLevelConsole}} in {{ic|/etc/systemd/journald.conf}}. To hide them, you must lower the level at which {{ic|dmesg}} messages are printed to the console. This can be done on start-up by creating a simple [[systemd]] service.
+
To disable those messages, increase the loglevel of printk messages that get through to the console - see [[Silent boot#sysctl]].
  
Create a file in {{ic|/etc/systemd/system/}} called {{ic|brcms_suppression.service}} or something similar:
+
=== Device BCM43241 non-detected ===
{{hc|brcms_suppression.service|
+
<nowiki>
+
[Unit]
+
Description=Broadcom console message suppression script
+
  
[Service]
+
This device will not display with either {{ic|lspci}} nor {{ic|lsusb}}; there is no known solution yet. Please remove this section when resolved.
Type=oneshot
+
RemainAfterExit=yes
+
ExecStart=/bin/sh -c 'dmesg -n 3'
+
  
[Install]
+
=== Connection is unstable with some routers ===
WantedBy=multi-user.target
+
</nowiki>
+
}}
+
  
Like all other systemd services, you can then enable it with
+
If no other approaches help, install {{Pkg|linux-lts}}, or use a [[Downgrading packages|previous driver version]].
# systemctl enable brcms_suppression
+
 
+
=== Miscellaneous user notes ===
+
{{Poor writing|This section must be rewritten impersonally, very likely as a FAQ or Troubleshooting section (also remove or update out-of-date information). See also [[Help:Style]].|section=Allowing user signatures on main article pages in limited situations?}}
+
 
+
* In my Dell Inspiron Laptop, I have a Broadcom BCM4401 Ethernet card and a Broadcom BCM4328 wireless card. If I just remove {{ic|b43}}, I can load the {{ic|wl}} driver, but no wireless card shows up. However, if I first remove the {{ic|b44}} (and {{ic|ssb}}) driver for my Ethernet card, and ''then'' load the {{ic|wl}} driver, I get a wireless device using the name ''eth0''. Afterwards, I can load {{ic|b44}} again, 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 {{ic|acer_wmi}} module. For testing, you can add the following to the kernel line in GRUB: {{ic|1=acer_wmi.disable=1}}
+
 
+
* I have found that to get the {{ic|wl}} drivers working for the Broadcom 4313 chip, you need to blacklist {{ic|brcm80211}} along with {{ic|b43}} and {{ic|ssb}}.
+
:--[[User:Admiralspark|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) {{ic|iwconfig wlan0 power off}} to {{ic|/etc/rc.local}} and create an empty file {{ic|/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.
+
:--[[User:Tom.yan|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 {{ic|wl}} solved everything. So in some cases, it's actually better than the kernel driver. However, I had to install it in the [[Mkinitcpio|initramfs image]], along with lib80211 and lib80211_crypt_tkip to avoid a recurring kernel panic.
+
:--[[User:Ivanoff|Ivanoff]], 18 March 2012
+
 
+
* 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 {{ic|modprobe wl}} without 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.
+
:--[[User:Wilco|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 {{ic|brcmsmac}} driver. Using the {{ic|broadcom-wl}} driver the problem was solved.
+
:--[[User:Nplatis|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 [[Kernel modules#Blacklisting|blacklist]] the kernel modules {{ic|dell_wmi}} and {{ic|cfg80211}}.
+
:--[[User:virtualeyes|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 [[User:Ivanoff|Ivanoff]]). What worked for me was to put a file in /etc/modprobe.d/ with the following content:
+
{{hc|/etc/modprobe.d/10_wl.conf|
+
blacklist brcmsmac
+
blacklist bcma
+
softdep wl pre: lib80211_crypt_tkip lib80211_crypt_ccmp lib80211_crypt_wep
+
}}
+
:--[[User:zarel|zarel]], 21 June 2013
+

Latest revision as of 16:24, 26 March 2016

Related articles

This article details how to install and setup a Broadcom wireless network device.

History

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 brcmsmac and brcmfmac drivers.

The types of available drivers are:

Driver Description
brcm80211 Kernel driver open-source version
b43 Kernel driver reverse-engineered version
broadcom-wl Broadcom driver restricted-license

Driver selection

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:

Installation

brcm80211

The kernel contains two built-in open-source drivers: brcmsmac for PCI backends and brcmfmac for SDIO/USB backends. They should be automatically loaded when booting.

b43

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. Install b43-firmwareAUR, b43-firmware-classicAUR or b43-firmware-legacyAUR from the AUR.

Note:
  • BCM4306 rev.3, BCM4311, BCM4312 noticed to have problems with b43-firmware. Use b43-firmware-classicAUR for these cards instead.
  • BCM4331 noticed to have problems with b43-firmware-classic. Use b43-firmwareAUR for this card instead.

broadcom-wl

Install broadcom-wlAUR or its DKMS variant broadcom-wl-dkmsAUR from the AUR for the restrictively licensed driver.

Tip: If you use broadcom-wlAUR, kernel upgrades may break wireless from time to time, and you may need to uninstall & reinstall the package. Using broadcom-wl-dkmsAUR helps avoid this.

Offline installation

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 base-devel group during installation. Then, use another Internet-connected computer to download linux-headers and the driver tarball from the AUR, and install them in that order.

Manually

Warning: This method is not recommended. Drivers that are un-tracked can become problematic or nonfunctional on system updates.

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

To make the module load at boot, refer to Kernel modules. It is recommending that you blacklist conflicting modules.

Troubleshooting

Setting broadcom-wl in monitor mode

To set broadcom-wl in monitor mode you have to set 1 to /proc/brcm_monitor0):

# echo 1 > /proc/brcm_monitor0

It will create a new network interface called prism0.

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 broadcom-wlAUR, uninstall and reinstall it after upgrading your kernel.

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 device naming for an answer.

Interface is showing but not allowing connections

Append the following kernel parameter:

b43.allhwsupport=1

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 non-detected

This device will not display with either lspci nor lsusb; there is no known solution yet. Please remove this section when resolved.

Connection is unstable with some routers

If no other approaches help, install linux-lts, or use a previous driver version.