“UbuntuHelp:WifiDocs/Driver/bcm43xx/Feisty”的版本间的差异

2007年11月21日 (三) 17:29的版本

文章出处:

https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx/Feisty

点击翻译:

English

请不要直接编辑翻译本页，本页将定期与来源同步。

Using Broadcom Wireless in Ubuntu Feisty 7.04

As of kernel 2.6.17, there is native support for some Broadcom chipsets. You have to use the fw-cutter tool to suck out the firmware code from a windows driver. The fw-cutter, or firmware cutter, or firmware extractor, does this.

This driver was included into the Linux kernel since kernel version 2.6.17-rc2.

There are two ways to use the Broadcom chipset with Linux:

• Using ndiswrapper. This was the only way of getting support for these devices before Linux kernel 2.6.17-rc2. This will not work on PowerPC.
• Using the native drivers in the kernel. This still requires extracting the firmware (the software that runs on the card itself) from one of a number of places using a tool called fwcutter. If you have bcm43xx hardware that is recognizable to the new kernel and you boot your PC with the Feisty installation CD, you will see error messages about the missing bcm43xx firmware, that show up on the console after the first boot splash screen but before X is started (or with the dmesg command). Following these instructions will fix this problem and you will have a working wireless card.

Forum Support for this Wiki

nickm wrote a howto on this forum for bcm43xx. If you have questions or need additional help please post there.

Using ndiswrapper

If your particular chipset is not supported by the bcm43xx driver in the kernel (as shown on the driver's website) you may need to install a driver using ndiswrapper. Depending on your chipset, you may even need to manually install a newer version of ndiswrapper. Note that if you aren't sure if your card is supported installing bcm43xx-fwcutter cannot hurt anything, is relatively easy, the drivers are free software (except for the firmware), and therefore should be tried first. Ndiswrapper should be used only if the card does not work well with the native drivers.

See UbuntuHelp:WifiDocs/Device/Broadcom BCM4311 rev 01 (ndiswrapper).

(Note: Here's a no-fluff howTo for using a bcm43xx--a bcm4311, to be specific--in Feisty. Also includes WPA configuration.)

Using the native drivers

See also the drivers home page.

Step 1: Obtaining the Firmware

The software that runs on the card itself is loaded onto the device by the driver prior to each use (this happens regardless of the operating system you are running this card on). Although the driver for the card is open source the firmware from the manufacturer is not, and is not allowed to be distributed by anyone but Broadcom, hence why it must be downloaded from their site and extracted from their driver, and why it cannot be distributed in Ubuntu by default.

If you're an Acer laptop user, try those instructions first. If you install everything correctly and still you're not able to connect to any wifi network, you should try to install acer-acpi package. It often helps and you won't be made to install driver using ndiswrapper. Find out more here: https://launchpad.net/acerlaptop-wifi/

After enabling the Universe repository (see UbuntuHelp:Repositories), install the bcm43xx-fwcutter package.

sudo apt-get install bcm43xx-fwcutter

It will ask if you want it to download and extract the firmware, but because the link is currently broken, choose no. Then enter the following to download the recommend driver manually.

wget http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o

Now extract the firmware.

sudo bcm43xx-fwcutter -w /lib/firmware  wl_apsta-3.130.20.0.o 

If that doesn't work, look here

Step 2: Loading module and checking card

Load the module:

sudo modprobe bcm43xx

The device gets loaded as either eth1/eth2. Find out which one it is by doing a

iwconfig

This should return the name of the interface as ethX. Check if you can scan for networks using

sudo iwlist ethX scan

Note: For some reason I could not scan for networks, the result of iwlist would be "no networks found", but when I entered the access point information manually it worked fine.

Step 3: Connecting to your network

Now, Network Manager is by default in Feisty and available on the upper right side of your screen, next to sound applet, etc... You can manage your connections directly by clicking left (to see info, enable or disable networking) or right (to choose a network) on it.

If it doesn't work, you can use the following :

Go to System -> Administration -> Network (if using gnome). click on your wireless card, click Properties, click "enable connection" and enter your wireless network details. Or, if Network Manager is not yet installed, install the following package, with apt-get or Synaptic:-

sudo apt-get install network-manager
sudo apt-get install network-manager-gnome

Or, for kubuntu:-

sudo apt-get install network-manager
sudo apt-get install network-manager-kde

This will install another Network Icon next to your Network Connection icon. This will allow you to manage your wireless connections.

Everything should now work. It should also work every time you turn on your computer without further configuration. Remember that you can use gnome-networking or network-manager, but not both! You have to set your card to roaming mode in gnome-networking to use network-manager if you have already configured it in gnome-networking.

Step 4: Configuration of WPA

This is *not required* with network-manager.

wpa_supplicant is usually installed by default, if not, install the package "wpasupplicant".

- Create the file /etc/wpa_supplicant.conf and insert the following:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
network={
ssid="<your accesspoints essid>"
scan_ssid=1
psk="<your wpa passphrase in plaintext>"
}

- Make this file readable only for root

sudo chmod go-rwx /etc/wpa_supplicant.conf

- Edit /etc/network/interfaces ( This will disable network-manager and may not be required ):

auto ethX
iface ethX inet dhcp
wireless-essid <your accesspoints essid>
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf

- Finally, test it by restarting the wireless interface

sudo ifdown ethX
sudo ifup ethX

Resources

• The Dapper wiki entry: UbuntuHelp:WifiDocs/Driver/bcm43xx/Dapper
• The Edgy wiki entry: UbuntuHelp:WifiDocs/Driver/bcm43xx/Edgy

Bcm43xx as ap

link found on it working as an ap