From: Mourad De Clerck <bugs-wireless@aquazul.com>
To: linux-wireless@vger.kernel.org
Cc: Larry Finger <Larry.Finger@lwfinger.net>
Subject: firmware loading fails for b43 using linux 3.4?
Date: Thu, 24 May 2012 01:49:06 +0200 [thread overview]
Message-ID: <4FBD7772.6070305@aquazul.com> (raw)
Hi,
I'm probably missing something obvious, but when going from 3.3 to 3.4
the b43 driver throws up an error, saying it can't find the firmware -
but it really _is_ there.
Here's the error:
b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found
b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw" not found
b43-phy0 ERROR: You must go to
http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and
download the correct firmware for this driver version. Please carefully
read all instructions on this website.
Here's the firmware it claims doesn't exist:
$ sha1sum /lib/firmware/b43/ucode16_mimo.fw
825a4bc63e3a96bb20fd8551add947435d47ad46 /lib/firmware/b43/ucode16_mimo.fw
This is from Debian's firmware-b43-installer package, version 1:015-14.
The network card in question:
02:00.0 Network controller [0280]: Broadcom Corporation BCM4322
802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
The only obvious change is 6b6fa5868eec26bdc6a83543cebb8cf832a2645a by
Larry Finger. I don't know if it matters, but b43 is statically compiled
in the kernel.
Am I missing something?
Thanks,
-- Mourad DC
next reply other threads:[~2012-05-23 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 23:49 Mourad De Clerck [this message]
2012-05-24 1:13 ` firmware loading fails for b43 using linux 3.4? Larry Finger
2012-05-24 2:44 ` Mourad De Clerck
2012-05-24 3:03 ` Larry Finger
2012-05-24 4:38 ` Mourad De Clerck
2012-05-24 13:25 ` Larry Finger
2012-05-24 16:41 ` Mourad De Clerck
2012-05-24 16:43 ` Arend van Spriel
2012-05-24 19:36 ` Larry Finger
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=4FBD7772.6070305@aquazul.com \
--to=bugs-wireless@aquazul.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).