From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] trouble with bcm43xx
Date: Wed, 26 Jul 2006 08:36:16 +0100 [thread overview]
Message-ID: <20060726083616.6e9da112@hactar.digimed.co.uk> (raw)
In-Reply-To: <yu9wta1yvkk.fsf@nyu.edu>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Tue, 25 Jul 2006 22:00:11 -0400, Allan Gottlieb wrote:
> The guide recommended wl_apsta.o for firmware, but that failed the
> bcm43xx-fwcutter command so I then tried wl.o, which bcm43xx was happy
> with.
It seems that some cards can be fussy about firmware, so try some
different ones. I have the following installed and my card works OK,
although it sometimes takes a couple of attempts to get a good
connection.
bcm43xx_initval01.fw bcm43xx_initval07.fw bcm43xx_microcode4.fw
bcm43xx_initval02.fw bcm43xx_initval08.fw bcm43xx_microcode5.fw
bcm43xx_initval03.fw bcm43xx_initval09.fw bcm43xx_pcm4.fw
bcm43xx_initval04.fw bcm43xx_initval10.fw bcm43xx_pcm5.fw
bcm43xx_initval05.fw bcm43xx_microcode11.fw
bcm43xx_initval06.fw bcm43xx_microcode2.fw
You don't say which card you are using, some are more problematic than
others, the gentoo-sources Changleog shows that support for some versions
is still being added. "lspci | grep BCM" will show you the exact model.
--
Neil Bothwick
Advanced: (adj.) doesn't work yet, but it's pretty close. See: bug,
glitch.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-26 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 2:00 [gentoo-user] trouble with bcm43xx Allan Gottlieb
2006-07-26 7:36 ` Neil Bothwick [this message]
2006-07-26 14:44 ` Allan Gottlieb
2006-07-26 22:49 ` Neil Bothwick
2006-07-26 23:47 ` Allan Gottlieb
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060726083616.6e9da112@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox