Bug 86 - kernel: b43-phy4 ERROR
Summary: kernel: b43-phy4 ERROR
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Ahmad Samir
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-17 18:19 CET by Gerardo Bueno
Modified: 2011-02-19 16:25 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Gerardo Bueno 2011-02-17 18:19:54 CET
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101230 Mandriva Linux/1.9.2.13-0.2mdv2010.2 (2010.2) Firefox/3.6.13
Build Identifier: 

Description of problem:
I get this errors into /var/log/messages:

Feb 17 18:13:52 localhost kernel: b43-phy4 ERROR: Firmware file "b43/ucode15.fw" not found
Feb 17 18:13:52 localhost kernel: b43-phy4 ERROR: Firmware file "b43-open/ucode15.fw" not found
Feb 17 18:13:52 localhost kernel: b43-phy4 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.



I've got a Broadcom Wifi Card and I have installed b43-fwcutter-013-1.mga1 rpm and wifi tools.

In Mandriva, I get this card works using ndiswrapper.


Thanks
Bye.


Reproducible: 

Steps to Reproduce:
Comment 1 Gerardo Bueno 2011-02-18 11:12:12 CET
I solve this error :D

Steps:

1.- Download this firmware:
http://downloads.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2

2.- Extract it.
3.- Go to mcc.
4.- Configure wireless card
5.- Choose 'wlan0: wlan0' option instead ndiswrapper
6.- Choose 'wl_apsta_mimo.o' file from tar.bz2 you extracted before
7.- That's all!!

I can surf the web again :D

Thanks.
Bye.
Comment 2 Gerardo Bueno 2011-02-19 16:25:12 CET
This bug can be closed.

It will be fixed using steps I write before.

Thanks.

Bye.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.