eeePC/AspireOne/HP/DELL mini Atheros AR5006x/5007eg 破戒疑难解答

冰火冰火

我用虚拟机，没办法了

ljg819031

还是要支持一下才行

frankywei

这是几个意思

linyonghai

usersSupport
) Y; v4 I6 P5 b/ \/ w5 NDrivers
, i+ C: n* [8 ^9 X) i2 W$ O% |& y9 s8 XDevices
Download
) s5 M: I! I6 |5 W3 q- x% fDocumentation
3 a0 z% H6 T# fvendorsdevelopers
b43 and b43legacy
. t6 B% w' {/ \) ]' HThe b43 drivers (bcm43xx in mainline kernels, b43 and b43legacy in wireless-2.6 and 2.6.24 and later) are drivers for the 802.11 B/G family of wireless chips Broadcom produces. The choice of which driver your card uses depends on the revision level of the 802.11 core. This number is read by driver ssb, and the correct choice for your device is made at that point. Note: If your card is a BCM4306 Rev 2, or only has 802.11b capability, it uses b43legacy. All other models use b43.


目录
# U" M5 f# D2 {2 Q
- i& \$ z6 {0 e  ^. `( q; Bb43 and b43legacy
FAQ - Frequently asked questions
caveats
/ O* Z( }" [) ?  [! e) ~9 QKnown PCI devices
Supported chip types
2 [' i5 {! N+ x3 P- B; sSupported in wireless-testing/compat-wireless-2.6
unsupported chips
available devices
features
& z! p: b- J  m# L% U: adonations
; K* B0 N! c/ n5 Hsupport
device firmware
) [( X* \4 u1 h9 x# efirmware installation
bug reporting
bcm43xx, b43legacy, b43, softmac,... the full story
related tools
external links


FAQ - Frequently asked questions
" i7 B& ?( h" l6 |  APlease read this whole document and the FAQ before asking any questions to the developers.
' W9 c6 [, [% R0 E5 a# r) @

caveats
All Broadcom chips require firmware that is loaded onto the wireless chip before it can operate. See below.
9 ?- T, [9 @7 e$ b' Q0 D& C
If you have an USB device with Broadcom chip, please try the RNDIS driver. The b43/b43legacy driver will never support this device.
8 Z! m  w3 g9 l1 ]

- H3 H: g% [  r) [Known PCI devices
. r% |: U+ Z! U5 W* [! Q0 z& j) EWhether a PCI device is supported by the b43/b43legacy driver can be found out with the lspci command:

4 H5 e" C6 f/ E' N9 u
lspci -vnn | grep 14e4The command will result in a string similiar to this example:


0001:01:01.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02)You should ignore anything, except the last part inside of the [ ] brackets. In the table below you can check whether your device is supported.

" U6 h2 C, D: @* G) G% F  EPCI-ID
State
Chip
Driver

) D- Y: c8 }" c# u: S" ~5 X14e4:4301
supported
) c. _; A. _  @ BCM4301?
# |  N4 \8 ~% X0 e) U b43legacy

- C& T% W# Y! C* [% n) b14e4:4306
supported
BCM4306
5 w* q9 K0 Q! B. W) r4 s b43legacy?

14e4:4307
. ?$ \+ A: q4 I& K% l supported
BCM4306
  D% m0 {6 c: w4 z/ X4 u- g b43
2 ^& `7 s* A0 ?2 z4 o) O/ \
( y; T/ O$ V" R) M: C14e4:4311
) N3 q9 R0 L9 ?- T* ` supported
; l* J. L& R3 Q$ J. F; A% Y* R7 ? BCM4311
! z! K* p: T" u- N b43
5 {* h: L6 A3 N( r- d+ v
  k3 W5 |. L/ O# q$ r14e4:4312
4 E4 s( r4 Y" Z4 D) `4 Z! ` supported (802.11g only)
BCM4312 802.11a/b/g
. l2 D* `7 J, L( ^ b43
) ?5 v5 i' j4 c7 j  ^% A3 E1 D
8 X" }5 D& d' Q3 j( W; ^14e4:4312
/ i) S0 ]9 |/ B9 q not supported - ID is duplicated
BCM4312 802.11b/g
1 u+ o* |0 S* z' ^# W  S9 o b43

4 m, R4 w' Z* b2 f+ o: y14e4:4315
in progress
7 M# p7 N2 ?. g9 v BCM4312 802.11b/g - low power
  m, n( X9 {5 L1 n; B b43

14e4:4318
supported
: s) {+ S0 E/ ~0 v2 J BCM4318
b43
' n4 m3 n+ b( z. S
; B5 X: W4 @; `7 ?! {14e4:4319
" t4 o+ F( o* N8 N' A' ~ supported
8 y5 ~8 O. }1 Q$ R# t BCM4311?
b43

; K; }$ y! j; q2 m  ~8 B4 A/ d14e4:4320
supported
/ i% ^2 l8 w" M' ^/ n) S. } BCM4306
  |1 q5 }) g  E5 H) i) N  h b43
6 _3 N/ x$ X/ D  o" f' T
14e4:4321
. ?" N' Y# N/ |# V- I) u$ s2 p not supported
?
+ X$ X+ ?: Z) @9 ?( i4 _$ m b43
$ |' ~) s1 Q/ u. b" e  G/ X
14e4:4324
not supported?
, p7 v5 z4 w0 n ?
) u# C" Q9 W- q8 `( m1 t6 b b43

/ k4 X* u- g- G2 ^& K14e4:4325
* Q: d. ^5 Z; h) h1 { not supported
* Z  O8 S. r1 V1 w' A ?
, G, I! ]* k, _' a$ z) S! ?$ J% S7 u0 N b43

14e4:4328
not supported
?
b43
% \3 T/ I" b" D; e- t
1 T4 O, s/ v. @14e4:4329
not supported
9 A' v2 \" D) Z  V) g) S1 Z1 ] ?
b43

14e4:432b
not supported?
- U) h: [0 O& w7 }; e ?
b43
9 ^2 g1 E6 L/ a5 M

Note that the PCI-ID is _not_ in direct correlation with the Chip-ID. The Chip-ID is printed to the kernel log by the b43 driver on startup (example):


b43-phy0: Broadcom 4318 WLAN foundOften the PCI-ID equals the Chip-ID, but that's not always the case and it's a constant source of confusion.


Supported chip types
bcm4303 (802.11b-only chips, uses b43legacy)
1 b% q1 \) T0 Q) Jbcm4306 (Rev. 2 uses b43legacy, Rev. 3 uses b43)
; M7 K+ n+ ^5 H  w1 E( vbcm4309 (only the 2.4GHz part)
bcm4311 rev 1 / bcm4312
bcm4311 rev 2 / bcm4312 (needs patches for 2.6.24)
7 k0 X' a4 V- o. H- Jbcm4312 with a/b/g (only the 2.4GHz part and no low-power LP-PHY devices)
) ^1 I; ^+ x" D( c6 lbcm4318

: ~( j; V# R: }: p, CSupported in wireless-testing/compat-wireless-2.6
BCM4312 802.11b/g, AKA BCM 4310 USB - This device has an LP PHY. Work on this device has begun, and the device now works in wireless-testing (and will be supported in 2.6.32), but performance is sub-par, due to the lack of calibration support. Note: This card uses the PCI-E bus, despite its name.
: ]. P$ }+ V" J- d7 n8 R4 D( ?BCM4313 802.11b/g - This device also has an LP PHY. The same probably applies to other LP-PHY devices.
" P$ x8 f3 m! }" h# T# y, K* e
unsupported chips
! u2 [+ c. J( y. Y. iThe 802.11a part of the 4309 and 4312 is not supported.
+ R- g5 {6 r/ g" {$ V, LBCM 4322 802.11a/b/g/n (Has PCI-ID 0x432B) - This device has an N Phy. There is no support for any Draft 802.11n features. We are working on it.
BCM 4321 (Has PCI-IDs 0x4328 and 0x4329) - These devices have N Phys. There is no support for any Draft 802.11n features. We are working on it.

available devices
Please see the device list.

! d% l& }6 X+ S1 S2 M- I
3 ?5 P+ k+ Z+ V: p! q* A8 Yfeatures

working
Station mode
Mesh networking mode (b43 only)
Access Point mode
# J  U! _* Q* l/ vAd-Hoc (IBSS) mode (b43 only)
, p% s* r& P2 r5 y) XMonitor and Promisc mode.
# S% `  X9 u. p2 ~5 t/ ?"Monitor while operating" and multiple monitor interfaces.
In-Hardware traffic de/encryption (relieves your CPU).
LEDs to signal card state and traffic.
4 Y2 q4 r  E4 B& c% f- b4 f3 P8 o! z2 [In-Hardware MAC address filter (b43 only; impossible on b43legacy hardware)
Packet injection (with radiotap; no FCS injection currently though hardware supports it - a radiotap flag is being discussed for this)
7 J. e. G! b+ Q8 V2 p: [" wBluetooth coexistance protection, if the bluetooth card is physically connected to the wireless chip. (Does not protect against external BT dongles)
% F& b3 A  ]; ^4 c+ CProbably something we forgot to add here.
$ o% U4 r" m+ Y% w- c4 I
not working yet
3 ]* w8 e9 X2 X3 d; C$ U# S- OIEEE 802.11n
  Z0 p: ~  \" u% }4 _) P  S/ W: TInterference mitigation.
3 P- P" f, B" l5 h' pProbably something else that's not listed under "Works".
AP mode using 4318 because of packet loss in high transmission rates. Hard to debug & fix.

7 M& f/ l0 J) t# O- C. T( w2 q! K
donations
* H4 E$ C; ^# t4 ^! MMany people have donated money, hardware or other services to make this driver possible. Thanks! Please see the donations page for details.
0 W8 F! W9 K2 D+ `

support
# n; ]* ~, C1 JIRC channel
irc.freenode.net #bcm-users (English please)
Mailing list
3 h+ e( Z' l: @5 h* z' y2 Chttp://lists.berlios.de/mailman/listinfo/bcm43xx-dev

* b9 x3 V( B8 b! Z" A

device firmware

firmware installation
The Broadcom wireless chip needs software, called "firmware", that runs on the wireless chip itself during operation. This firmware is copyrighted by Broadcom and it must be extracted from Broadcom's proprietary drivers. To get such firmware on your system, you must download the driver from a legal distribution point, as noted below. Then you must extract the firmware from that Broadcom driver by using b43-fwcutter (or bcm43xx-fwcutter) and install it in the special directory for firmware - usually /lib/firmware. Please note that the firmware from the binary drivers is Copyrighted by Broadcom Corporation and must not be redistributed.
7 j3 I0 g4 \6 j
! w& a6 U$ r. b1 JSome distributions have special methods for installing the firmware. In general these consist of a special command entered at a terminal. Because the proprietary driver containing the firmware cannot be included in the distribution, you will need a working connection to the Internet. Please post details for distros that are missed at bcm43xx-dev@lists.berlios.de .

/ h  y/ d1 b+ u7 `Fedora 10 and 11 use the following commands:
! ]! m! J% T  j; |( ]: P. B' Osu -

yum install b43-fwcutter wget

7 |' X! V( C2 A8 S+ wwhen you are asked "Is this ok [y/N]:" answer "Y" (and press "Enter)
& I6 V0 n1 {- Z: [% w% v1 tNow you have installed b43-fwcutter tool for extracting firmware from windows driver and download tool called wget. Now you need to download windows driver.
wget http://downloads.openwrt.org/sou ... l-4.80.53.0.tar.bz2
) O2 ^6 i  n; S# }0 }7 O
Now decompress, extract and copy firmware to /lib/firmware directory.
tar xjf broadcom-wl-4.80.53.0.tar.bz2
; ^/ D: d5 w9 q& e9 H2 D
cd broadcom-wl-4.80.53.0/kmod"
3 u/ `1 N% Y2 `  q7 V: v; I
5 m1 i) z! ~* b# M8 qb43-fwcutter -w /lib/firmware/ wl_apsta.o

openSUSE 11.0 and 11.1 use the following command:
sudo /usr/sbin/install_bcm43xx_firmware

* n% a1 t5 ~: p5 Gin latest versions of Ubuntu (all flavors) and Debian just need to install the b43-fwcutter package:
$ P5 J/ s+ u. M1 p+ x: M2 C2 g2 Ksudo apt-get install b43-fwcutter

when you are asked "Fetch and install firmware?" answer "Yes" (just press "Enter)
Gentoo systems supply a pre-compiled binary for b43-fwcutter. You need to "emerge b43-fwcutter", and then follow the instructions below to download the Broadcom driver. The line that invokes b43-fwcutter will need to be changed to execute the program emerged above.
/ ^4 Z" k% H) J/ v+ d2 j# hMandriva's graphical network card configuration tool, drakconnect, will extract the firmware from the Broadcom driver, which must be downloaded before configuring the card. For versions through 2008 Spring, you will need the V3 driver described below. Beginning with 2009, you will need either the V3 or V4 driver depending on whether your device uses b43legacy or b43. Either the wget command below, or a browser download will get the appropriate file.
Note: If you cannot use your distribution's packages, you need to have a compiler and headers for libc installed. The reason for this requirement is that you will have to build fwcutter.
) _# C. X7 p0 l9 |7 G  }1 \8 l
- f, c( w* R" `( X! p& bThere are different versions of firmware and tools you may need:
  I4 [4 e7 v, s7 A/ l/ Z+ c
Driver
Kernel
4 @/ o" s" n, F: l; t4 P5 W Firmware
Firmware extractor
' R5 S- X$ J! d/ t6 Z3 V# x Instructions

b43
) q& t1 h0 U" O0 l Linux-2.6.24, including 2.6.24-rcX and 2.6.24.Y
4.80.53.0
# h8 I" ~/ J4 m: H7 d b43-fwcutter v. 12
Go
" k. o' a6 r# Z5 h# `
. V% V1 M& R& V) tb43
' f: x; D: {7 k4 y Linux-2.6.25 and newer, compat-wireless-2.6 package, current GIT trees
' U0 z0 \" s( I+ j) N. Y) W, v 4.150.10.5
/ M5 g& M9 u: I5 T# N/ J b43-fwcutter v. 12
# A: A  K+ |, Y; j, Q Go
$ K% C5 }# C% `8 o5 A" p  A1 M, ]
b43legacy
- {) u- S. T7 {% D+ p Any
( }1 {7 X) }" I( ~% v 3.130.20.0
b43-fwcutter v. 12
6 [8 w. b0 C5 l8 v9 g Go
3 K$ u0 n! U- h4 O2 y+ @7 Y1 K
6 c, ]  ]) }$ h% E6 rbcm43xx (deprecated)
4 u  f& _9 A9 s& m$ g$ U Any
% Z  Z/ s9 L) q/ _7 z- p 3.130.20.0
% R; H* f1 y5 W! O" m; x5 m bcm43xx-fwcutter v. 6
Go
; w! c5 U# \3 a' P
% j4 j/ {% @; B- U( Y  U3 M
* I7 t1 ]  x# S$ ETo accomplish this task, do the following:

% I2 A/ ~8 c  V" V1 h/ K0 n! z
1 q: @5 x7 F* o
* j, H, y9 A$ t: P# [3 i- q7 ]You are using the b43 driver from linux-2.6.24
If you are using the b43 driver from linux-2.6.24, follow these instructions.
4 j& k& N2 t# h" U5 c- }- c6 e
: m4 h0 n) r) T5 ~- j/ C# C4 JUse version 012 of b43-fwcutter.
, y/ v3 p$ J! i1 f& vDownload, extract the b43-fwcutter tarball and build it:
- u0 l5 X1 q9 l5 e& ~
  u, x2 ?+ C' O" \: Y( S' b
0 o2 y  w' k( i( S9 C" qwget http://bu3sch.de/b43/fwcutter/b43-fwcutter-012.tar.bz2
0 T# _# H* A6 C  r9 c" Star xjf b43-fwcutter-012.tar.bz2
3 l2 B2 X# P+ }" ]4 Ucd b43-fwcutter-012
$ }  [1 G" b! k' L6 y" S( t! q7 lmake
cd ..Use version 4.80.53.0 of Broadcom's proprietary driver.
Download and extract the firmware from this driver tarball:
8 f9 ~8 n* t$ M7 ]- A8 {3 y

export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sou ... l-4.80.53.0.tar.bz2
, d4 w2 q  Q* mtar xjf broadcom-wl-4.80.53.0.tar.bz2
cd broadcom-wl-4.80.53.0/kmod
8 }; m' f# E+ ]4 C% n8 m, lsudo ../../b43-fwcutter-012/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta.oNote that you must adjust the FIRMWARE_INSTALL_DIR path to your distribution. The standard place where firmware is installed to is /lib/firmware. However some distributions put firmware in a different place.

  \0 T8 p% _3 w) z: e2 I% P  j

6 S7 ?- [* U# k7 n3 \# `. v8 LYou are using the b43 driver from linux-2.6.25 or newer
Follow these instructions if you are using the b43 driver from linux-2.6.25 and newer or compat-wireless-2.6, or from any current GIT tree.

Use version 011 of b43-fwcutter.
+ y5 K" B5 O/ D$ m/ N0 _+ ~: J7 vDownload, extract the b43-fwcutter tarball and build it:


- G. `& X" Z; y% E9 c6 s$ o5 ]wget http://bu3sch.de/b43/fwcutter/b43-fwcutter-012.tar.bz2
* [: F- Y- \: Q, J) e* ^tar xjf b43-fwcutter-012.tar.bz2
cd b43-fwcutter-012
8 g0 A$ y( g4 y# mmake
cd ..Use version 4.150.10.5 of Broadcom's proprietary driver.
Download and extract the firmware from this driver tarball:
" p  w8 Z0 o+ ~4 }+ ^/ e9 C& G8 l

export FIRMWARE_INSTALL_DIR="/lib/firmware"
. c2 M, c3 e, _# G% x" W/ T! ^wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2
tar xjf broadcom-wl-4.150.10.5.tar.bz2
1 q; C  r/ E, }cd broadcom-wl-4.150.10.5/driver
; x! L5 @2 g1 c$ Q2 H4 h. Jsudo ../../b43-fwcutter-012/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta_mimo.oNote that you must adjust the FIRMWARE_INSTALL_DIR path to your distribution. The standard place where firmware is installed to is /lib/firmware. However some distributions put firmware in a different place.

, B0 e9 j. a# s! e! ~; _( s
# c0 \* m3 F3 ^2 f) Y+ R, ~) u) o6 N2 }
You are using the b43-legacy driver
If you are using the b43legacy driver, follow these instructions.
" }$ A7 ~8 ?; {
; h  \1 ~  ?8 Z; FUse version 011 of b43-fwcutter.
# C- Z  O' D' R( n- T4 MDownload, extract the b43-fwcutter tarball and build it:


  Y; q6 n# d6 {2 Dwget http://bu3sch.de/b43/fwcutter/b43-fwcutter-012.tar.bz2
4 u4 _: O: D4 d2 ~" Gtar xjf b43-fwcutter-012.tar.bz2
cd b43-fwcutter-012
make
" {5 H- D) T& Q& Ccd ..Use version 3.130.20.0 of Broadcom's proprietary driver.
Download and extract the firmware from this driver:
4 e2 L+ L* d1 |: t# D, I# y* @
2 G  I+ f6 t; Z$ Y1 h& \
export FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
sudo ./b43-fwcutter-012/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta-3.130.20.0.oNote that you must adjust the FIRMWARE_INSTALL_DIR path to your distribution. The standard place where firmware is installed to is /lib/firmware. However some distributions put firmware in a different place.
$ M. p4 t% V# X) B1 x  D4 L3 R* Z1 G

: g' a$ U  s6 N
% u/ s1 F. Y, m7 Y/ `9 U0 E4 m8 ?You are using the deprecated bcm43xx driver
If you are using the old deprecated bcm43xx driver, follow these instructions.

- a7 O9 }# M3 k! EUse version 006 of bcm43xx-fwcutter.
Download, extract the bcm43xx-fwcutter tarball and build it:
8 ?: f3 G! A+ z( L( I
6 N+ @2 W$ d: u
wget http://bu3sch.de/b43/fwcutter/bcm43xx-fwcutter-006.tar.bz2
- ?& x+ z6 Z7 x; otar xjf bcm43xx-fwcutter-006.tar.bz2
9 m2 v4 @! k4 {0 f- `cd bcm43xx-fwcutter-006
make
4 `5 ^9 ?9 P1 J. pcd ..Use version 3.130.20.0 of Broadcom's proprietary driver.
Download and extract the firmware from this driver:

$ F3 d3 x9 o5 r/ G3 R- k
# I# {* ^) e% K( |, |+ }& Fexport FIRMWARE_INSTALL_DIR="/lib/firmware"
wget http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
  Z+ \4 U  D8 R; Ksudo ./bcm43xx-fwcutter-006/bcm43xx-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta-3.130.20.0.oNote that you must adjust the FIRMWARE_INSTALL_DIR path to your distribution. The standard place where firmware is installed to is /lib/firmware. However some distributions put firmware in a different place.
/ {( J& n: p6 D( z2 W) o4 J1 n6 [
" h+ {1 [& v0 y7 s. y
bug reporting
! {3 G1 t8 o. o7 \& T& WYou should send a message to the b43/b43legacy mailing list at bcm43xx-dev@berlios.de containing ALL of the following:
+ k( B, J1 W, _# }8 M; ?
A description of the problem at hand
When it happens
+ c# ]. s$ J* s6 k2 g9 JHow to reproduce
% _/ p6 L  K" b8 `. z" P0 TThe output of the following commands:
! k) _: ]3 L: _, D9 k% L
uname -a
2 t0 \. ]; x7 P0 l
% _' {' I" ^, c; c' a/ [8 tlspci -vvn|grep 43 -A7

: h1 n8 Y) R# o% bdmesgwlan configuration, authentication/encryption type
2 e* i# w$ W: T2 ?+ ?3 [In addition the following may be of interest to developers:
/ t0 |7 s+ A* f) r
If you have built the kernel from git, tell which tree, and the output of "git describe"
! {8 _, m0 Q2 AIf the driver worked with earlier kernels, but has since stopped working, a bisection is of great value.
" F8 ?0 d  j' R9 f# [" U, v
# w: b# J7 J- K6 Y+ [7 ]  Ybcm43xx, b43legacy, b43, softmac,... the full story
1 s/ k! h$ B: ~  U% q0 _) c7 d2 k# hThe bcm43xx is the old deprecated driver. It is using the ieee80211 + softmac libraries of code shared with other drivers. This stack is deprecated and being replaced by the new mac80211 stack. A new stack implies brand new, re-written driver(s): here come b43 and b43legacy.
) p/ `) I. |/ e2 `  [
9 N7 A, N; N- x# a0 A
$ ?2 E# N  W% ^0 M% jWhat's the difference between b43legacy and b43?
- D9 V, @' |* Hb43 offers a newer codebase and hardware crypto support. Broadcom did not release any version 4 firmware files for some older boards, possibly due to memory constraints on the cards themselves. Stuck with firmware version 3, these cards must use b43legacy which doesn't have hardware crypto support because that has not been reverse engineered completly for version 3 firmware.
5 i4 ?5 u5 l! Q5 E! `  }4 v  a: K
& W% g( q# u2 ^6 R4 ?6 w# R
1 Y4 Q6 |7 h3 T3 C. f5 X bcm43xx
" k$ o& }7 M. J- c+ {, s, [! V b43legacy
b43
' p1 g& ?6 e& f5 R# G4 c
+ c3 A3 G5 J$ z. z, s9 D  Eneeds firmware
# ]! P- w* K( W version 3
version 4

0 {* o# V5 X3 ^8 Z9 vextracted by
bcm43xx-fwcutter
2 I+ N: U& E" j' w b43-fwcutter
& m# N9 g$ M5 \2 D$ `8 a" [
1 G! N( W  g8 b& x7 i7 Z1 p5 vdepends on
- a% N$ e  K# U! o# f! ` softmac
mac80211

8 x( R* u6 f2 [$ Y4 q
b43legacy should be used on all 4301 and 4303 cards. 4306 and 4309 cards with a MAC core revision of 4 or less should also use b43legacy. b43 should be used on all other cards. You can safely have both versions built on the same system. The full MAC core version is printed in the kernel logs when "SSB debugging" is enabled in KConfig and the driver finds a board. Type "dmesg" to see it. If you are unsure and don't know what we are talking about here, always build both b43 and b43legacy (and get firmware for both too). The kernel autoloader will automatically do the right thing and load the correct driver for your device.
, x1 o! I' k# }
) M3 `: F  s2 ]" a8 n
; ]2 h$ e5 U: O! T3 x: brelated tools
ssb-sprom
A tool for the modification of the Broadcom Sonics Silicon Backplane SPROM (e.g. you can permanently change the MAC address or the PCI IDs of your wireless card – useful on some (e.g. Compaq/HP) laptops where the BIOS checks these at boot. It's now part of b43-tools:
git clone http://git.bu3sch.de/git/b43-tools.gitTo use the sprom tool, it is necessary to get a disk copy of your sprom from the /sys file system. The file path for the sprom contents depends on the bus layout of the specific computer being used and will be something like
" t. x6 c, R7 T$ l: o/sys/devices/pci0000:00/0000:00:0d.0/0000:04:00.0/ssb_spromIt is not recommended that you try to type the name. Instead, you should use the following commands to get the working copy:
SSB_SPROM=$(find /sys/devices -name ssb_sprom)
echo $SSB_SPROMIf the echo command only results in a single instance of "/sys/...", you may proceed. For systems with more than one SSB-based interface, there will be such a string for each, and the command that sets the SSB_SPROM symbol will have to be changed. In the name above, the sequence states that this device is attached to the 0'th PCI bus via bridge 0d.0 and is device 04:00.0 on that bridge. To find which of your SSB devices to select, use the 'lspci -v' command. On my system, the first line of such output for my interface is "04:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 02)". For this device, one would use
$ Z7 w1 w/ ]  BSSB_SPROM=$(find /sys/devices -name ssb_sprom | grep 04:00.0)
echo $SSB_SPROMOf course, the "04:00.0" needs to match your system, and check the output value to determine that there is now a single instance of "/sys..." and that the path matches the device whose SPROM is to be changed. If not, adjust the string after 'grep' accordingly.
Once the SSB_SPROM variable matches the path to ssb_sprom for your device, get a working copy of the sprom contents with
sudo cat $SSB_SPROM > ssb_sprom_copyYou may now look at the contents of your sprom with the command
ssb-sprom -i ssb_sprom_copy -PAs an example, let us suppose that you have purchased a Dell mini-pci card to use in an HP laptop. The HP BIOS refuses to use the card when the pcivendor is Dell (code 0x1028), not HP (code 0x103C). From the information provided by an "ssb-prom –help" command, we learn that the switch needed to change this vendor code is "–subv". To change that code, we use the command
ssb-sprom -i ssb_sprom_copy -o new_ssb_sprom_copy --subv 0x103Cto write the HP vendor ID to our working copy. I use different input and output files so as not to destroy the original. If further changes are needed, for example the PCI product ID, the command
3 p$ I+ Q5 R3 u2 N" b+ Qssb-sprom -i new_ssb_sprom_copy -o new_ssb_sprom_copy --subp 0x137Cwould be used. Note that the input and output files may be the same.
Once you think you have updated correctly, use the following to check the contents:
) _) O3 w2 N5 e9 Sssb-sprom -i ssb_sprom_copy -POnce the sprom contents are the way you want them, and presumably correct, you are ready to rewrite the file. First, use
% U" r# F& T! }  j* Kecho $SSB_SPROMto ensure that this symbol still contains the SPROM path. If not, then it will have to be reloaded as discussed above.
0 v4 @$ V: F6 M" l4 t& GYou are then ready to rewrite the sprom with
% i! K$ W# k: S9 n: Msudo cp new_ssb_sprom_copy $SSB_SPROMOnce again, you are urged to be absolutely certain of the contents of the working copy BEFORE taking this step. If your interface becomes unusable as a result of writing incorrect data into the sprom, the responsibility is YOURS. Once again, you have been warned.
: ?* E: p9 P& p& s6 G  e  hA firmware assembler/disassembler can be found in the git repository at
git clone http://git.bu3sch.de/git/b43-tools.gitThere are more development and debugging tools available in the b43-tools git repository. Just clone it and read the shipped documentation files.
1 D- O1 ]! `4 Cgit clone http://git.bu3sch.de/git/b43-tools.gitwpa_supplicant
; ~: |& ^5 r/ o( I# q; @! a5 a& DA tool for enabling WPA and full IEEE 802.11i/RSN/WPA2 WPA-PSK and WPA2-PSK (pre-shared key) ("WPA-Personal") WPA with EAP.
4 R$ d% w4 ~6 x- xwpa_supplicant may have a 'broadcom' driver that is used with the proprietary Broadcom driver. The bcm43xx, b43 and b43legacy drivers use the linux wireless extensions properly and so need the wext driver. This is set using the -D option like this:
wpa_supplicant -iwlan0 -Dwext -c/etc/wpa_supplement.confOf course, you don't need this if you're using NetworkManager.

+ u1 {4 z" Y# `  \/ `( K
0 N. S! G( @9 Xexternal links
Broadcom Wireless-LAN section
打印视图登录About this site

tedlsng

no money la

benf

我晕，又买了一次

fanzhi21

seeeeeeeeeeeee

xysm86

没钱付啊怎么办

xysm86

我的用minibt3  里面的无线管理工具能搜索到信号  为什么用spoonwep2 就不能搜索到信号 ？

ztzzm

这个是什么？airodump驱动？？

sd4510067

我的是Atheros AR5007EG，用啥驱动，打ifconfig -a或iwconfig等都看不到，若是不支持，但是怎么有那么多用这款的能用的呢

dkf666888

试试楼主说的方法