* A small error in b43
@ 2011-04-07 20:09 Gregory Bellier
2011-04-07 20:18 ` Rafał Miłecki
2011-04-07 20:20 ` Larry Finger
0 siblings, 2 replies; 7+ messages in thread
From: Gregory Bellier @ 2011-04-07 20:09 UTC (permalink / raw)
To: b43-dev
Dear list,
I would like to test the b43 driver for a BCM4322. I tried with 2.6.38.2
and 2.6.39-rc2 but I'm stuck with a firmware error in dmesg :
[ 75.922582] b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found
[ 75.922587] b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw"
not found
[ 75.922590] 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.
I have b43-fwcutter v13.
# b43-fwcutter -w /lib/firmware/ broadcom-wl-4.178.10.4/linux/wl_apsta.o
This file is recognised as:
ID : FW15
filename : wl_apsta.o
version : 478.104
MD5 : bb8537e3204a1ea5903fe3e66b5e2763
Extracting b43/ucode5.fw
Extracting b43/pcm5.fw
Extracting b43/b0g0bsinitvals5.fw
Extracting b43/a0g0bsinitvals5.fw
Extracting b43/b0g0initvals5.fw
Extracting b43/a0g1initvals5.fw
Extracting b43/a0g0initvals5.fw
Extracting b43/a0g1bsinitvals5.fw
Extracting b43/ucode9.fw
Extracting b43/a0g1initvals9.fw
Extracting b43/a0g0bsinitvals9.fw
Extracting b43/b0g0bsinitvals9.fw
Extracting b43/b0g0initvals9.fw
Extracting b43/a0g1bsinitvals9.fw
Extracting b43/a0g0initvals9.fw
Extracting b43/ucode11.fw
Extracting b43/n0bsinitvals11.fw
Extracting b43/n0absinitvals11.fw
Extracting b43/n0initvals11.fw
Extracting b43/ucode13.fw
Extracting b43/b0g0initvals13.fw
Extracting b43/a0g1bsinitvals13.fw
Extracting b43/a0g1initvals13.fw
Extracting b43/lp0bsinitvals13.fw
Extracting b43/b0g0bsinitvals13.fw
Extracting b43/lp0initvals13.fw
Extracting b43/ucode14.fw
Extracting b43/lp0initvals14.fw
Extracting b43/lp0bsinitvals14.fw
Extracting b43/ucode15.fw
Extracting b43/lp0bsinitvals15.fw
Extracting b43/lp0initvals15.fw
Extracting b43/ucode16.fw
Extracting b43/n0bsinitvals16.fw
Extracting b43/sslpn0initvals16.fw
Extracting b43/n0initvals16.fw
Extracting b43/lp0initvals16.fw
Extracting b43/sslpn0bsinitvals16.fw
Extracting b43/lp0bsinitvals16.fw
Did I miss something ? I promise I read carefully.
Sorry, I wrote this email in several times. I finally did a symlink in
/lib/firmware/b43 : # sudo ln -s ucode16.fw ucode16_mimo.fw
And it worked like this.
Regards,
Gregory Bellier.
^ permalink raw reply [flat|nested] 7+ messages in thread
* A small error in b43
2011-04-07 20:09 A small error in b43 Gregory Bellier
@ 2011-04-07 20:18 ` Rafał Miłecki
2011-04-07 20:20 ` Larry Finger
1 sibling, 0 replies; 7+ messages in thread
From: Rafał Miłecki @ 2011-04-07 20:18 UTC (permalink / raw)
To: b43-dev
2011/4/7 Gregory Bellier <gregory.bellier@gmail.com>:
> Dear list,
>
> I would like to test the b43 driver for a BCM4322. I tried with 2.6.38.2 and
> 2.6.39-rc2 but I'm stuck with a firmware error in dmesg :
> [ ? 75.922582] b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found
> [ ? 75.922587] b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw" not
> found
> [ ? 75.922590] 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.
>
> I have b43-fwcutter v13.
>
> # b43-fwcutter -w /lib/firmware/ broadcom-wl-4.178.10.4/linux/wl_apsta.o
> This file is recognised as:
> ?ID ? ? ? ? : ?FW15
> ?filename ? : ?wl_apsta.o
> ?version ? ?: ?478.104
> ?MD5 ? ? ? ?: ?bb8537e3204a1ea5903fe3e66b5e2763
> Extracting b43/ucode5.fw
> Extracting b43/pcm5.fw
> Extracting b43/b0g0bsinitvals5.fw
> Extracting b43/a0g0bsinitvals5.fw
> Extracting b43/b0g0initvals5.fw
> Extracting b43/a0g1initvals5.fw
> Extracting b43/a0g0initvals5.fw
> Extracting b43/a0g1bsinitvals5.fw
> Extracting b43/ucode9.fw
> Extracting b43/a0g1initvals9.fw
> Extracting b43/a0g0bsinitvals9.fw
> Extracting b43/b0g0bsinitvals9.fw
> Extracting b43/b0g0initvals9.fw
> Extracting b43/a0g1bsinitvals9.fw
> Extracting b43/a0g0initvals9.fw
> Extracting b43/ucode11.fw
> Extracting b43/n0bsinitvals11.fw
> Extracting b43/n0absinitvals11.fw
> Extracting b43/n0initvals11.fw
> Extracting b43/ucode13.fw
> Extracting b43/b0g0initvals13.fw
> Extracting b43/a0g1bsinitvals13.fw
> Extracting b43/a0g1initvals13.fw
> Extracting b43/lp0bsinitvals13.fw
> Extracting b43/b0g0bsinitvals13.fw
> Extracting b43/lp0initvals13.fw
> Extracting b43/ucode14.fw
> Extracting b43/lp0initvals14.fw
> Extracting b43/lp0bsinitvals14.fw
> Extracting b43/ucode15.fw
> Extracting b43/lp0bsinitvals15.fw
> Extracting b43/lp0initvals15.fw
> Extracting b43/ucode16.fw
> Extracting b43/n0bsinitvals16.fw
> Extracting b43/sslpn0initvals16.fw
> Extracting b43/n0initvals16.fw
> Extracting b43/lp0initvals16.fw
> Extracting b43/sslpn0bsinitvals16.fw
> Extracting b43/lp0bsinitvals16.fw
>
> Did I miss something ? I promise I read carefully.
>
> Sorry, I wrote this email in several times. I finally did a symlink in
> /lib/firmware/b43 : # sudo ln -s ucode16.fw ucode16_mimo.fw
> And it worked like this.
Symlink should work for now. The real solution is not use:
http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.3_mipsel.tar.bz2
and the newest fwcutter (which is needed to support this 5.10.56.27.3).
I still hope to get easy access to newer broadcom-wl, so I'm waiting
with updating howto on wiki page. I just mailed OpenWRT team day or
two ago.
--
Rafa?
^ permalink raw reply [flat|nested] 7+ messages in thread
* A small error in b43
2011-04-07 20:09 A small error in b43 Gregory Bellier
2011-04-07 20:18 ` Rafał Miłecki
@ 2011-04-07 20:20 ` Larry Finger
2011-04-07 20:36 ` Gregory Bellier
1 sibling, 1 reply; 7+ messages in thread
From: Larry Finger @ 2011-04-07 20:20 UTC (permalink / raw)
To: b43-dev
On 04/07/2011 03:09 PM, Gregory Bellier wrote:
> Dear list,
>
> I would like to test the b43 driver for a BCM4322. I tried with 2.6.38.2 and
> 2.6.39-rc2 but I'm stuck with a firmware error in dmesg :
> [ 75.922582] b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found
> [ 75.922587] b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw" not found
> [ 75.922590] 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.
>
> I have b43-fwcutter v13.
>
> # b43-fwcutter -w /lib/firmware/ broadcom-wl-4.178.10.4/linux/wl_apsta.o
> This file is recognised as:
> ID : FW15
> filename : wl_apsta.o
> version : 478.104
> MD5 : bb8537e3204a1ea5903fe3e66b5e2763
> Extracting b43/ucode5.fw
> Extracting b43/pcm5.fw
> Extracting b43/b0g0bsinitvals5.fw
> Extracting b43/a0g0bsinitvals5.fw
> Extracting b43/b0g0initvals5.fw
> Extracting b43/a0g1initvals5.fw
> Extracting b43/a0g0initvals5.fw
> Extracting b43/a0g1bsinitvals5.fw
> Extracting b43/ucode9.fw
> Extracting b43/a0g1initvals9.fw
> Extracting b43/a0g0bsinitvals9.fw
> Extracting b43/b0g0bsinitvals9.fw
> Extracting b43/b0g0initvals9.fw
> Extracting b43/a0g1bsinitvals9.fw
> Extracting b43/a0g0initvals9.fw
> Extracting b43/ucode11.fw
> Extracting b43/n0bsinitvals11.fw
> Extracting b43/n0absinitvals11.fw
> Extracting b43/n0initvals11.fw
> Extracting b43/ucode13.fw
> Extracting b43/b0g0initvals13.fw
> Extracting b43/a0g1bsinitvals13.fw
> Extracting b43/a0g1initvals13.fw
> Extracting b43/lp0bsinitvals13.fw
> Extracting b43/b0g0bsinitvals13.fw
> Extracting b43/lp0initvals13.fw
> Extracting b43/ucode14.fw
> Extracting b43/lp0initvals14.fw
> Extracting b43/lp0bsinitvals14.fw
> Extracting b43/ucode15.fw
> Extracting b43/lp0bsinitvals15.fw
> Extracting b43/lp0initvals15.fw
> Extracting b43/ucode16.fw
> Extracting b43/n0bsinitvals16.fw
> Extracting b43/sslpn0initvals16.fw
> Extracting b43/n0initvals16.fw
> Extracting b43/lp0initvals16.fw
> Extracting b43/sslpn0bsinitvals16.fw
> Extracting b43/lp0bsinitvals16.fw
>
> Did I miss something ? I promise I read carefully.
>
> Sorry, I wrote this email in several times. I finally did a symlink in
> /lib/firmware/b43 : # sudo ln -s ucode16.fw ucode16_mimo.fw
> And it worked like this.
I'm not sure if those two firmware files are equivalent or not.
There is a new version of b43-fwcutter in the git repository at
git://git.bu3sch.de/b43-tools.git that knows how to extract the firmware from
URL http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.3_mipsel.tar.bz2.
After untarring, the object file is
broadcom-wl-5.10.56.27.3/driver/wl_apsta/wl_prebuilt.o
Larry
^ permalink raw reply [flat|nested] 7+ messages in thread
* A small error in b43
2011-04-07 20:20 ` Larry Finger
@ 2011-04-07 20:36 ` Gregory Bellier
0 siblings, 0 replies; 7+ messages in thread
From: Gregory Bellier @ 2011-04-07 20:36 UTC (permalink / raw)
To: b43-dev
2011/4/7 Larry Finger <Larry.Finger@lwfinger.net>
> On 04/07/2011 03:09 PM, Gregory Bellier wrote:
>
>> Dear list,
>>
>> I would like to test the b43 driver for a BCM4322. I tried with 2.6.38.2
>> and
>> 2.6.39-rc2 but I'm stuck with a firmware error in dmesg :
>> [ 75.922582] b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found
>> [ 75.922587] b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw" not
>> found
>> [ 75.922590] 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.
>>
>> I have b43-fwcutter v13.
>>
>> # b43-fwcutter -w /lib/firmware/ broadcom-wl-4.178.10.4/linux/wl_apsta.o
>> This file is recognised as:
>> ID : FW15
>> filename : wl_apsta.o
>> version : 478.104
>> MD5 : bb8537e3204a1ea5903fe3e66b5e2763
>> Extracting b43/ucode5.fw
>> Extracting b43/pcm5.fw
>> Extracting b43/b0g0bsinitvals5.fw
>> Extracting b43/a0g0bsinitvals5.fw
>> Extracting b43/b0g0initvals5.fw
>> Extracting b43/a0g1initvals5.fw
>> Extracting b43/a0g0initvals5.fw
>> Extracting b43/a0g1bsinitvals5.fw
>> Extracting b43/ucode9.fw
>> Extracting b43/a0g1initvals9.fw
>> Extracting b43/a0g0bsinitvals9.fw
>> Extracting b43/b0g0bsinitvals9.fw
>> Extracting b43/b0g0initvals9.fw
>> Extracting b43/a0g1bsinitvals9.fw
>> Extracting b43/a0g0initvals9.fw
>> Extracting b43/ucode11.fw
>> Extracting b43/n0bsinitvals11.fw
>> Extracting b43/n0absinitvals11.fw
>> Extracting b43/n0initvals11.fw
>> Extracting b43/ucode13.fw
>> Extracting b43/b0g0initvals13.fw
>> Extracting b43/a0g1bsinitvals13.fw
>> Extracting b43/a0g1initvals13.fw
>> Extracting b43/lp0bsinitvals13.fw
>> Extracting b43/b0g0bsinitvals13.fw
>> Extracting b43/lp0initvals13.fw
>> Extracting b43/ucode14.fw
>> Extracting b43/lp0initvals14.fw
>> Extracting b43/lp0bsinitvals14.fw
>> Extracting b43/ucode15.fw
>> Extracting b43/lp0bsinitvals15.fw
>> Extracting b43/lp0initvals15.fw
>> Extracting b43/ucode16.fw
>> Extracting b43/n0bsinitvals16.fw
>> Extracting b43/sslpn0initvals16.fw
>> Extracting b43/n0initvals16.fw
>> Extracting b43/lp0initvals16.fw
>> Extracting b43/sslpn0bsinitvals16.fw
>> Extracting b43/lp0bsinitvals16.fw
>>
>> Did I miss something ? I promise I read carefully.
>>
>> Sorry, I wrote this email in several times. I finally did a symlink in
>> /lib/firmware/b43 : # sudo ln -s ucode16.fw ucode16_mimo.fw
>> And it worked like this.
>>
>
> I'm not sure if those two firmware files are equivalent or not.
>
> There is a new version of b43-fwcutter in the git repository at git://
> git.bu3sch.de/b43-tools.git that knows how to extract the firmware from
> URL
> http://mirror2.openwrt.org/sources/broadcom-wl-5.10.56.27.3_mipsel.tar.bz2.
> After untarring, the object file is
> broadcom-wl-5.10.56.27.3/driver/wl_apsta/wl_prebuilt.o
>
Yes, it works properly with this one !
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20110407/e9a5eb4f/attachment-0001.html>
^ permalink raw reply [flat|nested] 7+ messages in thread
* A small error in b43
[not found] <alpine.DEB.2.01.1104162313180.18728@trent.utfs.org>
@ 2011-04-17 7:06 ` Rafał Miłecki
[not found] ` <alpine.DEB.2.01.1104170131420.18728@trent.utfs.org>
0 siblings, 1 reply; 7+ messages in thread
From: Rafał Miłecki @ 2011-04-17 7:06 UTC (permalink / raw)
To: b43-dev
2011/4/17 Christian Kujau <lists@nerdbynature.de>:
> I just stumbled over the "A small error in b43" thread and wanted to say
> thanks!
>
> With b43-fwcutter (git) and broadcom-wl-5.10.56.27.3/driver/wl_apsta/wl_prebuilt.o,
> my BCM4322 chip finally works!
>
> 2.6.38.2-9.fc15.x86_64 / MacBookPro5,5
>
> 03:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
> ? ? ? ?Subsystem: Apple Computer Inc. Device 008d
> ? ? ? ?Flags: bus master, fast devsel, latency 0, IRQ 23
> ? ? ? ?Memory at d3200000 (64-bit, non-prefetchable) [size=16K]
> ? ? ? ?Capabilities: [40] Power Management version 3
> ? ? ? ?Capabilities: [58] Vendor Specific Information: Len=78 <?>
> ? ? ? ?Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
> ? ? ? ?Capabilities: [d0] Express Endpoint, MSI 00
> ? ? ? ?Capabilities: [100] Advanced Error Reporting
> ? ? ? ?Capabilities: [13c] Virtual Channel
> ? ? ? ?Capabilities: [160] Device Serial Number d5-53-bb-ff-ff-00-00-26
> ? ? ? ?Capabilities: [16c] Power Budgeting <?>
> ? ? ? ?Kernel driver in use: b43-pci-bridge
> ? ? ? ?Kernel modules: ssb
>
> It's pretty slow (max ~500KBps vs. ~3MBps in MacOS) and even SSH
> connections are a bit sluggish, but it's better than nothing :-)
>
> Thanks again!
> Christian.
>
>
> [ 4215.197290] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
> [ 4215.273450] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 4238.260117] b43-phy1: Broadcom 4322 WLAN found (core revision 16)
> [ 4238.283448] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
> [ 4238.283765] Registered led device: b43-phy1::tx
> [ 4238.283801] Registered led device: b43-phy1::rx
> [ 4238.283840] Registered led device: b43-phy1::radio
> [ 4238.283864] Broadcom 43xx driver loaded [ Features: PMNLS, Firmware-ID: FW13 ]
> [ 4238.486290] b43-phy1: Loading firmware version 508.1084 (2009-01-14 01:32:01)
Thanks for your report! :) Support in 2.6.38 is known to be speed
limited. Actually, if you check
http://wireless.kernel.org/en/users/Drivers/b43 , we report BCM4322 as
supported in 2.6.39+. With this newer kernel you should get 54M TX.
--
Rafa?
^ permalink raw reply [flat|nested] 7+ messages in thread
* A small error in b43
[not found] ` <alpine.DEB.2.01.1104170131420.18728@trent.utfs.org>
@ 2011-04-17 10:27 ` Rafał Miłecki
[not found] ` <alpine.DEB.2.01.1104171138421.18728@trent.utfs.org>
0 siblings, 1 reply; 7+ messages in thread
From: Rafał Miłecki @ 2011-04-17 10:27 UTC (permalink / raw)
To: b43-dev
W dniu 17 kwietnia 2011 10:35 u?ytkownik Christian Kujau
<lists@nerdbynature.de> napisa?:
> On Sun, 17 Apr 2011 at 09:06, Rafa? Mi?ecki wrote:
>> http://wireless.kernel.org/en/users/Drivers/b43 , we report BCM4322 as
>> supported in 2.6.39+. With this newer kernel you should get 54M TX.
>
> FWIW, I booted 2.6.39-0.rc3.git2.0.fc16.x86_64 and now it's at 1.2MBps,
> which is not great but a huge impovement. Oh, and for the record: the
> PCI-ID for this BCM4322 chip is 14e4:432b.
How did you test this speed? Was this iperf or something else? 1.2MBps
is 9.6 Mbps. I was able to achieve 15.2 Mbps (1.9 MBps) with the same
card.
What were the conditions? Were you far away from AP?
You can see my comparison for PHY rev4, which means for example
14e4:432b: http://zajec.net/blog/view/2011-b43-n-phy-rev3plus-performance
--
Rafa?
^ permalink raw reply [flat|nested] 7+ messages in thread
* A small error in b43
[not found] ` <alpine.DEB.2.01.1104171138421.18728@trent.utfs.org>
@ 2011-04-17 21:34 ` Rafał Miłecki
0 siblings, 0 replies; 7+ messages in thread
From: Rafał Miłecki @ 2011-04-17 21:34 UTC (permalink / raw)
To: b43-dev
W dniu 17 kwietnia 2011 20:52 u?ytkownik Christian Kujau
<lists@nerdbynature.de> napisa?:
> On Sun, 17 Apr 2011 at 12:27, Rafa? Mi?ecki wrote:
>> How did you test this speed? Was this iperf or something else? 1.2MBps
>> is 9.6 Mbps. I was able to achieve 15.2 Mbps (1.9 MBps) with the same
>> card.
>
> No, I did not involve any fancy tools, just netcat on both sides and "pv"
> inbetween:
>
> server$ nc -l 1234 | pv | dd of=/dev/null
> client$ dd if=/dev/zero | nc server 1234
>
> ..and "pv" prints out the data rate during the test (and "dd" does it too
> at the end.
>
>> What were the conditions? Were you far away from AP?
>
> The AP is a Linksys WRT54GL router (802.11abg) and I'm 3m away from it -
> the same distance as when it's booted in MacOS.
>
> I've just retested with MacOS again and with the "test" above I'm only
> getting 2.5MBps too, not quite the 3MBps I was talking about. The AP is
> quite old, so maybe I cannot get any higher than this anyway.
>
>> You can see my comparison for PHY rev4, which means for example
>> 14e4:432b: http://zajec.net/blog/view/2011-b43-n-phy-rev3plus-performance
>
> I'm going to give iperf a try and report back.
Thanks, I'll try nc && dd.
Did you connect your server by cable to the AP?
--
Rafa?
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2011-04-17 21:34 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-04-07 20:09 A small error in b43 Gregory Bellier
2011-04-07 20:18 ` Rafał Miłecki
2011-04-07 20:20 ` Larry Finger
2011-04-07 20:36 ` Gregory Bellier
[not found] <alpine.DEB.2.01.1104162313180.18728@trent.utfs.org>
2011-04-17 7:06 ` Rafał Miłecki
[not found] ` <alpine.DEB.2.01.1104170131420.18728@trent.utfs.org>
2011-04-17 10:27 ` Rafał Miłecki
[not found] ` <alpine.DEB.2.01.1104171138421.18728@trent.utfs.org>
2011-04-17 21:34 ` Rafał Miłecki
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).