Differences between revisions 52 and 53
⇤ ← Revision 52 as of 2009-03-04 17:44:47 →
Size: 13390
Editor: GeoffSimmons
Comment: Add driver IRC channel, amend etchnhalf apt-cache cmd, reorder blacklist
← Revision 53 as of 2009-03-16 03:30:59 → ⇥
Size: 13444
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||<tablestyle="width: 100%;" style="border: 0px hidden">~-[:DebianWiki/EditorGuide#translation:Translation(s)]: none-~||<style="text-align: right;border: 0px hidden"> (!) [:/Discussion:Discussion]|| ||<tablestyle="width: 100%;" style="border: 0px hidden">~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: none-~||<style="text-align: right;border: 0px hidden"> (!) [[/Discussion|Discussion]]||
Line 7: Line 7:
[[TableOfContents(3)]] <<TableOfContents(3)>>
Line 11: Line 11:
The page ["HowToIdentifyADevice/PCI"] explains how to identify a PCI device. For example: The page [[HowToIdentifyADevice/PCI]] explains how to identify a PCI device. For example:
Line 20: Line 20:
<!> '''The [:HowToIdentifyADevice/PCI#pci-id:PCI-Id] isn't sufficient to determine the Broadcom chipset within.''' The relevant driver has built-in logic to probe the actual chipset. <!> '''The [[HowToIdentifyADevice/PCI#pci-id|PCI-Id]] isn't sufficient to determine the Broadcom chipset within.''' The relevant driver has built-in logic to probe the actual chipset.
Line 22: Line 22:
The page ["HowToIdentifyADevice/USB"] explains how to identify a USB device. For example: The page [[HowToIdentifyADevice/USB]] explains how to identify a USB device. For example:
Line 37: Line 37:
 * [#b43 b43] ([#supported_b43 supported devices])  * [[#b43|b43]] ([[#supported_b43|supported devices]])
Line 40: Line 40:
 * [#b43 b43legacy] ([#supported_b43legacy supported devices])  * [[#b43|b43legacy]] ([[#supported_b43legacy|supported devices]])
Line 43: Line 43:
 * [#rndis_wlan rndis_wlan] ([#supported_rndis supported devices])  * [[#rndis_wlan|rndis_wlan]] ([[#supported_rndis|supported devices]])
Line 46: Line 46:
 * [#bcm43xx bcm43xx] ([#supported_bcm43xx supported devices])  * [[#bcm43xx|bcm43xx]] ([[#supported_bcm43xx|supported devices]])
Line 51: Line 51:
More information on b43/b43legacy can be found on the Linux Wireless [http://wireless.kernel.org/en/users/Drivers/b43#b43andb43legacy b43 driver page]. bcm43xx is no longer developed. Note that bcm43xx, b43 and b43legacy '''do not''' support any USB devices based on Broadcom wireless chipsets. More information on b43/b43legacy can be found on the Linux Wireless [[http://wireless.kernel.org/en/users/Drivers/b43#b43andb43legacy|b43 driver page]]. bcm43xx is no longer developed. Note that bcm43xx, b43 and b43legacy '''do not''' support any USB devices based on Broadcom wireless chipsets.
Line 55: Line 55:
 * [#ndiswrapper NDISwrapper] plus the relevant Windows NDIS driver. This is a workaround for devices not supported natively by Linux, such as USB devices based on Broadcom wireless chipsets (other than the BCM4320 USB).

[[Anchor(b43)]]		  * [[#ndiswrapper|NDISwrapper]] plus the relevant Windows NDIS driver. This is a workaround for devices not supported natively by Linux, such as USB devices based on Broadcom wireless chipsets (other than the BCM4320 USB).

<<Anchor(b43)>>
Line 61: Line 61:
 . <!> [:DebianEtch:Etch] users: These drivers are not present in the stock 2.6.18 kernel.
 . Install an [:EtchAndAHalf:] kernel: {{{apt-cache search linux-image-2.6- | grep etchnhalf}}} and install a package appropriate for your system.		  . <!> [[DebianEtch|Etch]] users: These drivers are not present in the stock 2.6.18 kernel.
 . Install an [[EtchAndAHalf]] kernel: {{{apt-cache search linux-image-2.6- | grep etchnhalf}}} and install a package appropriate for your system.
Line 82: Line 82:
 1. The necessary kernel module should be [:Modules:automatically loaded]. If necessary, it can be manually loaded via either: {{{  1. The necessary kernel module should be [[Modules|automatically loaded]]. If necessary, it can be manually loaded via either: {{{
Line 93: Line 93:
 1. [:WiFi/HowToUse:Configure] your wireless interface as appropriate.  1. [[WiFi/HowToUse|Configure]] your wireless interface as appropriate.
Line 100: Line 100:
[[Anchor(rndis_wlan)]] <<Anchor(rndis_wlan)>>
Line 104: Line 104:
 . <!> [:DebianEtch:Etch] users: This driver is not present in the stock 2.6.18 kernel.
 . Install a 2.6.26 kernel from [:Backports:Debian Backports]. Once your sources are configured: {{{apt-cache search linux-image-2.6.26}}} and install a package appropriate for your system.		  . <!> [[DebianEtch|Etch]] users: This driver is not present in the stock 2.6.18 kernel.
 . Install a 2.6.26 kernel from [[Backports|Debian Backports]]. Once your sources are configured: {{{apt-cache search linux-image-2.6.26}}} and install a package appropriate for your system.
Line 108: Line 108:
The rndis_wlan driver supports wireless RNDIS[[FootNote(Microsoft's unofficial CDC ACM variant, see [wiki:WikiPedia:USB_communications_device_class USB CDC on Wikipedia].)]] chipsets, of which the Broadcom 4320 USB chipset is the only one known at this time. This driver does not require firmware to be installed. The rndis_wlan driver supports wireless RNDIS<<FootNote(Microsoft's unofficial CDC ACM variant, see [wiki:WikiPedia:USB_communications_device_class USB CDC on Wikipedia].)>> chipsets, of which the Broadcom 4320 USB chipset is the only one known at this time. This driver does not require firmware to be installed.
Line 118: Line 118:
 1. The necessary kernel module should be [:Modules:automatically loaded]. If necessary, it can be manually loaded via: {{{  1. The necessary kernel module should be [[Modules|automatically loaded]]. If necessary, it can be manually loaded via: {{{
Line 127: Line 127:
 1. [:WiFi/HowToUse:Configure] your wireless interface as appropriate.  1. [[WiFi/HowToUse|Configure]] your wireless interface as appropriate.
Line 130: Line 130:
 * This driver does not support connections to hidden ["WPA"] networks at this time.
 * If you are attempting to use a Belkin !F5D7051 device, [:KernelModuleBlacklisting:blacklist] the {{{rt2500usb}}} module as advised earlier and execute {{{modprobe -r rt2500usb}}} to unload it.
 * [http://wireless.kernel.org/en/users/Drivers/rndis_wlan#knownproblems Known problems] with this driver are documented on its homepage.

[[Anchor(bcm43xx)]]		  * This driver does not support connections to hidden [[WPA]] networks at this time.
 * If you are attempting to use a Belkin !F5D7051 device, [[KernelModuleBlacklisting|blacklist]] the {{{rt2500usb}}} module as advised earlier and execute {{{modprobe -r rt2500usb}}} to unload it.
 * [[http://wireless.kernel.org/en/users/Drivers/rndis_wlan#knownproblems|Known problems]] with this driver are documented on its homepage.

<<Anchor(bcm43xx)>>
Line 140: Line 140:
 . <!> You are required to install the DebPkg:etch-volatile/bcm43xx-fwcutter package from the [:DebianVolatile:Debian Volatile] repository due to bug Bug:437488. Installing the DebPkg:etch/bcm43xx-fwcutter package ''will fail'' to download firmware if requested.  . <!> You are required to install the DebPkg:etch-volatile/bcm43xx-fwcutter package from the [[DebianVolatile|Debian Volatile]] repository due to bug Bug:437488. Installing the DebPkg:etch/bcm43xx-fwcutter package ''will fail'' to download firmware if requested.
Line 152: Line 152:
 1. The necessary kernel module should be [:Modules:automatically loaded]. If necessary, it can be manually loaded via: {{{  1. The necessary kernel module should be [[Modules|automatically loaded]]. If necessary, it can be manually loaded via: {{{
Line 161: Line 161:
 1. [:WiFi/HowToUse:Configure] your wireless interface as appropriate.  1. [[WiFi/HowToUse|Configure]] your wireless interface as appropriate.
Line 165: Line 165:
  * Ensure that you have installed the DebPkg:etch-volatile/bcm43xx-fwcutter package from [:DebianVolatile:Debian Volatile].   * Ensure that you have installed the DebPkg:etch-volatile/bcm43xx-fwcutter package from [[DebianVolatile|Debian Volatile]].
Line 167: Line 167:
 * Your device may be detected (or better supported) with the [#b43 b43 or b43legacy driver].

[[Anchor(ndiswrapper)]]		  * Your device may be detected (or better supported) with the [[#b43|b43 or b43legacy driver]].

<<Anchor(ndiswrapper)>>
Line 172: Line 172:
 * Etch users: Before resorting to NDISwrapper, try using the [#b43 b43/b43legacy drivers].  * Etch users: Before resorting to NDISwrapper, try using the [[#b43|b43/b43legacy drivers]].
Line 190: Line 190:
Kernel module and NDIS driver installation is described on the [:NdisWrapper:NDISwrapper] page. Kernel module and NDIS driver installation is described on the [[NdisWrapper|NDISwrapper]] page.
Line 195: Line 195:
[[Anchor(supported_b43)]] <<Anchor(supported_b43)>>
Line 197: Line 197:
The page ["HowToIdentifyADevice/PCI"] explains how to identify a PCI device. The page [[HowToIdentifyADevice/PCI]] explains how to identify a PCI device.
Line 201: Line 201:
[[Anchor(supported_b43legacy)]] <<Anchor(supported_b43legacy)>>
Line 203: Line 203:
The page ["HowToIdentifyADevice/PCI"] explains how to identify a PCI device. The page [[HowToIdentifyADevice/PCI]] explains how to identify a PCI device.
Line 207: Line 207:
[[Anchor(supported_rndis)]] <<Anchor(supported_rndis)>>
Line 209: Line 209:
The page ["HowToIdentifyADevice/USB"] explains how to identify a USB device. The page [[HowToIdentifyADevice/USB]] explains how to identify a USB device.
Line 230: Line 230:
[[Anchor(supported_bcm43xx)]] <<Anchor(supported_bcm43xx)>>
Line 244: Line 244:
{i} Although listed above, the BCM4311 is only supported by this driver from kernel 2.6.20.6. Use of the [#b43 b43 driver] is recommended. {i} Although listed above, the BCM4311 is only supported by this driver from kernel 2.6.20.6. Use of the [[#b43|b43 driver]] is recommended.
Line 249: Line 249:
 * [:WiFi/HowToUse:How to use a WiFi interface]
 * [:NdisWrapper:NDISwrapper]		  * [[WiFi/HowToUse|How to use a WiFi interface]]
 * [[NdisWrapper|NDISwrapper]]
Line 253: Line 253:
 * [http://www.linuxwireless.org/en/users/Drivers/b43] - b43, b43legacy homepage;
  * [http://www.linuxwireless.org/en/users/Drivers/b43#devicefirmware b43 and b43legacy] - device firmware
  * irc://irc.freenode.net/bcm-users - driver ["IRC"] channel
 * [http://www.linuxwireless.org/en/users/Drivers/rndis_wlan] - rndis_wlan homepage
 * [http://bcm43xx.berlios.de/] - bcm43xx homepage		  * [[http://www.linuxwireless.org/en/users/Drivers/b43]] - b43, b43legacy homepage;
  * [[http://www.linuxwireless.org/en/users/Drivers/b43#devicefirmware|b43 and b43legacy]] - device firmware
  * irc://irc.freenode.net/bcm-users - driver [[IRC]] channel
 * [[http://www.linuxwireless.org/en/users/Drivers/rndis_wlan]] - rndis_wlan homepage
 * [[http://bcm43xx.berlios.de/]] - bcm43xx homepage

Translation(s): none

(!) ?Discussion

Broadcom 43xx wireless devices

This page describes how to enable support for WiFi devices based on Broadcom 4303, 4306, 4309, 4311, 4312, 4318 and 4320 chipsets on Debian systems.

Contents

  1. Broadcom 43xx wireless devices
    1. Device Identification
      1. PCI (includes PCIe, Mini PCI, Cardbus)
      2. USB
    2. Drivers
      1. b43 and b43legacy
      2. rndis_wlan
      3. bcm43xx (Etch with 2.6.18 kernel only)
      4. NDISwrapper
    3. Supported Devices
      1. b43
      2. b43legacy
      3. rndis_wlan
      4. bcm43xx
    4. See Also
    5. External Links

Device Identification

PCI (includes PCIe, Mini PCI, Cardbus)

The page HowToIdentifyADevice/PCI explains how to identify a PCI device. For example: 

update-pciids
lspci -nn

Your Broadcom PCI wireless device should be listed: 

0c:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN [14E4:4311] (rev 01)

<!> The PCI-Id isn't sufficient to determine the Broadcom chipset within. The relevant driver has built-in logic to probe the actual chipset.

USB

The page HowToIdentifyADevice/USB explains how to identify a USB device. For example: 

update-usbids
lsusb

Your Broadcom USB wireless device should be listed: 

Bus 003 Device 006: ID 050d:7051 Belkin Components F5D7051 54g USB Network Adapter

Drivers

There are multiple drivers supporting Broadcom wireless LAN chipsets.

Linux native drivers:

  • b43 (supported devices)

    • The new driver for modern 802.11g and 802.11a chipsets.
    • Introduced in kernel 2.6.24.

  • b43legacy (supported devices)

    • For legacy 802.11b-only devices and the BCM4306 revision 2 chipset.
    • Introduced in kernel 2.6.24.

  • rndis_wlan (supported devices)

    • For devices with the BCM4320 USB chipset only.

    • Introduced in kernel 2.6.25.

  • bcm43xx (supported devices)

    • Included in mainline kernels from 2.6.17-rc2.
    • Disabled in Debian 2.6.24 and later kernels.
    • Removed from the mainline kernel in 2.6.26.

More information on b43/b43legacy can be found on the Linux Wireless b43 driver page. bcm43xx is no longer developed. Note that bcm43xx, b43 and b43legacy do not support any USB devices based on Broadcom wireless chipsets.

Using Windows' binary drivers:

  • NDISwrapper plus the relevant Windows NDIS driver. This is a workaround for devices not supported natively by Linux, such as USB devices based on Broadcom wireless chipsets (other than the BCM4320 USB).

b43 and b43legacy

For 2.6.24 and later kernels. Both drivers are included as modules in Debian kernel images.

  • <!> Etch users: These drivers are not present in the stock 2.6.18 kernel.

  • Install an EtchAndAHalf kernel: apt-cache search linux-image-2.6- | grep etchnhalf and install a package appropriate for your system.

  • Restart your system with this kernel before continuing.

The b43 driver supports modern Broadcom 802.11g wireless chipsets. The b43legacy driver supports Broadcom 802.11b-only devices and BCM4306 revision 2 chipsets.

The b43 driver requires version 4 firmware, whereas the b43legacy driver requires version 3 firmware. All firmware must be downloaded separately, which can be performed by the b43-fwcutter package during installation.

  1. Add a "contrib" component to /etc/apt/sources.list for your Debian version, for example: 

    # Debian Lenny/5.0
deb http://ftp.us.debian.org/debian lenny main contrib non-free

    or 

    # Debian Etch/4.0
deb http://ftp.us.debian.org/debian etch main contrib non-free

  2. Update the list of available packages and install the b43-fwcutter and wireless-tools packages: 

    aptitude update
aptitude install b43-fwcutter wireless-tools

    If you have an Internet connection available, allow the b43-fwcutter package to fetch and extract firmware.

  3. The necessary kernel module should be automatically loaded. If necessary, it can be manually loaded via either: 

    modprobe b43

    or 

    modprobe b43legacy

  4. Verify your device has an available interface: 

    iwconfig

  5. Raise the interface to activate the radio, for example: 

    ifconfig wlan0 up

  6. Configure your wireless interface as appropriate.

Troubleshooting

  • Examine the kernel ring buffer (dmesg) to verify the required firmware files are being loaded by the driver. Lack of firmware is the usual reason for the "SIOCSIFFLAGS: No such file or directory" error message.

    • Run dpkg-reconfigure -plow b43-fwcutter to fetch and extract firmware again. Firmware will only be fetched if not already present in the /lib/firmware/[b43|b43legacy] directories on your system.

    • If necessary, firmware can be manually acquired and extracted using the b43-fwcutter utility, see http://wireless.kernel.org/en/users/Drivers/b43#firmwareinstallation

rndis_wlan

For 2.6.25 and later kernels. This is included as a module in Debian kernel images.

  • <!> Etch users: This driver is not present in the stock 2.6.18 kernel.

  • Install a 2.6.26 kernel from Debian Backports. Once your sources are configured: apt-cache search linux-image-2.6.26 and install a package appropriate for your system.

  • Restart your system with this kernel before continuing.

The rndis_wlan driver supports wireless RNDIS1 chipsets, of which the Broadcom 4320 USB chipset is the only one known at this time. This driver does not require firmware to be installed.

  • {i} Belkin F5D7051 users: Due to the inclusion of its vendor and device IDs, an Ralink RT2500USB driver will be incorrectly loaded for this device. Please blacklist the rt2500usb module before continuing, see KernelModuleBlacklisting.

  1. Install the wireless-tools package: 

    aptitude update
aptitude install wireless-tools
  2. Physically connect the device to your system.

  3. The necessary kernel module should be automatically loaded. If necessary, it can be manually loaded via: 

    modprobe rndis_wlan

  4. Verify your device has an available interface: 

    iwconfig

  5. Raise the interface to activate the radio, for example: 

    ifconfig wlan0 up

  6. Configure your wireless interface as appropriate.

Troubleshooting

  • This driver does not support connections to hidden WPA networks at this time.

  • If you are attempting to use a Belkin F5D7051 device, blacklist the rt2500usb module as advised earlier and execute modprobe -r rt2500usb to unload it.

  • Known problems with this driver are documented on its homepage.

bcm43xx (Etch with 2.6.18 kernel only)

For kernels earlier than 2.6.24. This is included as a module in Debian kernel images.

The bcm43xx driver requires firmware which must be downloaded separately (can be performed by the etch-volatile/bcm43xx-fwcutter package during installation).

  1. Add the Debian Volatile repository (including the "contrib" component) to your /etc/apt/sources.list file, for example: 

    # Debian Volatile (Etch/4.0)
deb http://volatile.debian.org/debian-volatile etch/volatile main contrib non-free

  2. Update the list of available packages and install the etch-volatile/bcm43xx-fwcutter and etch/wireless-tools packages: 

    aptitude update
aptitude install bcm43xx-fwcutter wireless-tools

    If you have an Internet connection available, allow the etch-volatile/bcm43xx-fwcutter package to fetch and extract firmware.

  3. The necessary kernel module should be automatically loaded. If necessary, it can be manually loaded via: 

    modprobe bcm43xx

  4. Verify your device has an available interface: 

    iwconfig

  5. Raise the interface to activate the radio, for example: 

    ifconfig eth1 up

  6. Configure your wireless interface as appropriate.

Troubleshooting

  • Examine the kernel ring buffer (dmesg) to verify the required firmware files are being loaded by the driver. Lack of firmware is the usual reason for the "SIOCSIFFLAGS: No such file or directory" error message.

    • Ensure that you have installed the etch-volatile/bcm43xx-fwcutter package from Debian Volatile.

    • Run dpkg-reconfigure -plow bcm43xx-fwcutter to fetch and extract firmware again. Firmware will only be fetched if not already present in the /lib/firmware directory on your system.

  • Your device may be detected (or better supported) with the b43 or b43legacy driver.

NDISwrapper

  • This should only be used as a last resort, if the device is not supported by the native drivers (eg. Broadcom USB devices, other than the BCM4320 USB).

  • Etch users: Before resorting to NDISwrapper, try using the b43/b43legacy drivers.

Blacklist native drivers

If loaded, the bcm43xx and b43/b43legacy drivers will conflict with NDISwrapper. To unload and disable:

Lenny, Etch with 2.6.24 kernel

modprobe -r b43
modprobe -r b43legacy
echo -e blacklist b43\\nblacklist b43legacy >> /etc/modprobe.d/blacklist.local

Etch with 2.6.18 kernel

modprobe -r bcm43xx
echo blacklist bcm43xx >> /etc/modprobe.d/blacklist.local

Installation

Kernel module and NDIS driver installation is described on the NDISwrapper page.

Supported Devices

b43

The page HowToIdentifyADevice/PCI explains how to identify a PCI device.

b43legacy

The page HowToIdentifyADevice/PCI explains how to identify a PCI device.

rndis_wlan

The page HowToIdentifyADevice/USB explains how to identify a USB device.

The following list is based on the alias fields of  modinfo rndis_wlan on Lenny. 

  • USB: 0411:004B MelCo., Inc. (Device name unknown)
USB: 0411:00BC MelCo., Inc. (Device name unknown)
USB: 050D:011B Belkin Components (Device name unknown)
USB: 0A5C:D11B Broadcom Corp. (Device name unknown)
USB: 0B05:1717 ASUSTek Computer, Inc. (Device name unknown)
USB: 0BAF:0111 U.S. Robotics (Device name unknown)
USB: 0BAF:011B U.S. Robotics Wireless MAXg Adapter
USB: 13B1:000E Linksys (Device name unknown)
USB: 13B1:0014 Linksys (Device name unknown)
USB: 13B1:0026 Linksys (Device name unknown)
USB: 1690:0715 Askey Computer Corp. [hex] Voyager 1055 Laptop Adapter
USB: 1799:011B (Vendor name unknown) (Device name unknown)

    http://wireless.kernel.org/en/users/Drivers/rndis_wlan#supportedchips - supported devices

bcm43xx

The following list is based on the alias fields of  modinfo bcm43xx on Etch. 

  • PCI: 14E4:4301 Broadcom Corporation BCM4303 802.11b Wireless LAN Controller
PCI: 14E4:4307 Broadcom Corporation BCM4307 802.11b Wireless LAN Controller
PCI: 14E4:4318 Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller
PCI: 14E4:4319 Broadcom Corporation BCM4311 [AirForce 54g] 802.11a/b/g PCI Express Transceiver
PCI: 14E4:4320 Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller
PCI: 14E4:4324 Broadcom Corporation BCM4309 802.11a/b/g
PCI: 14E4:4325 Broadcom Corporation BCM43xG 802.11b/g

{i} Although listed above, the BCM4311 is only supported by this driver from kernel 2.6.20.6. Use of the b43 driver is recommended.

See Also

CategoryHardware | CategoryWireless

  1. Microsoft's unofficial CDC ACM variant, see [wiki:USB_communications_device_class USB CDC on Wikipedia]. (1)