linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "John H." <mistamaila@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	wireless <linux-wireless@vger.kernel.org>,
	Broadcom Linux <bcm43xx-dev@lists.berlios.de>
Subject: Re: Upgrade to f7 breaks bcm43xx module
Date: Fri, 1 Jun 2007 14:18:38 -0400	[thread overview]
Message-ID: <20070601181838.GB5663@tuxdriver.com> (raw)
In-Reply-To: <5b9417770706011111u20f32192s960961dc8693f00e@mail.gmail.com>

On Fri, Jun 01, 2007 at 01:11:51PM -0500, John H. wrote:
> bcm43xx mac80211:
> YOUR FIRMWARE IS TOO OLD. Firmware from binary drivers older than
> version 4.x is unsupported. You must upgrade your firmware files.
> 
> I get that now with f7 and 2.6.21 and didn't with fc6 2.6.20.
> 
> However, I read that the error is not what it sounds like.  What is
> the solution?

You might start by posting on a Fedora list, lest ye draw the ire of
any other distro users on this list... :-)

In the meantime, I suggest you extract firmware[1] from the wl_apsta.o
file in this archive:

	http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2

Hth!

John

[1] Using bcm43xx-fwcutter, of course.
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-06-01 18:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 18:11 Upgrade to f7 breaks bcm43xx module John H.
2007-06-01 18:18 ` John W. Linville [this message]
2007-06-01 18:18 ` Larry Finger
2007-06-01 18:23   ` John H.
2007-06-01 18:37     ` John H.
2007-06-01 18:55       ` John H.
2007-06-01 19:24         ` Larry Finger
2007-06-01 18:58     ` Larry Finger
2007-06-01 21:36 ` Michael Buesch

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=20070601181838.GB5663@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mistamaila@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).