| 1 |
On Tue, 25 Jul 2006 22:00:11 -0400, Allan Gottlieb wrote: |
| 2 |
|
| 3 |
> The guide recommended wl_apsta.o for firmware, but that failed the |
| 4 |
> bcm43xx-fwcutter command so I then tried wl.o, which bcm43xx was happy |
| 5 |
> with. |
| 6 |
|
| 7 |
It seems that some cards can be fussy about firmware, so try some |
| 8 |
different ones. I have the following installed and my card works OK, |
| 9 |
although it sometimes takes a couple of attempts to get a good |
| 10 |
connection. |
| 11 |
|
| 12 |
bcm43xx_initval01.fw bcm43xx_initval07.fw bcm43xx_microcode4.fw |
| 13 |
bcm43xx_initval02.fw bcm43xx_initval08.fw bcm43xx_microcode5.fw |
| 14 |
bcm43xx_initval03.fw bcm43xx_initval09.fw bcm43xx_pcm4.fw |
| 15 |
bcm43xx_initval04.fw bcm43xx_initval10.fw bcm43xx_pcm5.fw |
| 16 |
bcm43xx_initval05.fw bcm43xx_microcode11.fw |
| 17 |
bcm43xx_initval06.fw bcm43xx_microcode2.fw |
| 18 |
|
| 19 |
You don't say which card you are using, some are more problematic than |
| 20 |
others, the gentoo-sources Changleog shows that support for some versions |
| 21 |
is still being added. "lspci | grep BCM" will show you the exact model. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
Advanced: (adj.) doesn't work yet, but it's pretty close. See: bug, |
| 28 |
glitch. |
Archives