Package Details: b43-firmware

Git Clone URL: (read-only, click to copy)
Package Base: b43-firmware
Description: Firmware for Broadcom B43 wireless networking chips - latest release
Upstream URL:
Keywords: broadcom firmware wireless
Licenses: unknown
Conflicts: b43-firmware-classic
Submitter: Xavion
Maintainer: hayao
Last Packager: Xavion
Votes: 251
Popularity: 0.001537
First Submitted: 2008-11-22 01:47 (UTC)
Last Updated: 2015-12-31 21:30 (UTC)

Latest Comments

hayao commented on 2021-06-13 13:15 (UTC)

Now I am maintainer. What should I do? Should I remove the dependency?

JulianXhokaxhiu commented on 2021-06-13 12:55 (UTC)

I forgot I'm actually no more the maintainer, but somehow I still receive notification mails. You'd have to wait for the new one to take action, sorry :)

Scimmia commented on 2021-06-13 12:36 (UTC)

The dep should simply be removed.

JulianXhokaxhiu commented on 2021-06-13 08:51 (UTC)

I'd be totally open to that, if there's a way in the PKGBUILD to target all possible packages providing linux, in the depends section.

Is anyone aware how to achieve that?

df8oe commented on 2021-06-09 11:14 (UTC) (edited on 2021-06-09 11:16 (UTC) by df8oe)

If you run a linux-zen kernel without installed linux you cannot use package (but of course it works). I think dependency should be extended to linux-zen, too

Hi-Angel commented on 2016-11-19 18:42 (UTC)

vicp74 works here, Linux 4.8.7-1, WiFi card is BCM4312.

vicp74 commented on 2016-10-21 04:28 (UTC)

This firmware is not working for me with the kernel 4.8.2, the system doesn't boot and I think it's related to [1]. I tried the b43-firmware-classic but that one also fails. I'm doing some testing, is someone else experiencing this problem? [1]

Xavion commented on 2015-12-31 22:05 (UTC)

Okay, I've changed the license name and downgraded the warning to a post-installation message. I'm a bit surprised I didn't do the latter that way the first time to be honest. Anyway, this should bring about a peaceful end to our discussion. You might recall that the last one we had didn't conclude quite so smoothly. You ended up saying: "Don't bother emailing me again. You're now blocked." Am I still blocked, BTW? :-)

Scimmia commented on 2015-12-31 15:44 (UTC)

The license is what gets put on the end package. It is most definitely not GPL. Change it to custom, proprietary, unknown, whatever. Just not GPL. I read the discussion, you're the only one who mentioned a warning in the PKGBUILD. That's not where it belongs. Even if you want it there, making the user acknowledge it is the real problem.

Xavion commented on 2015-12-31 08:46 (UTC)

Thanks for letting me know about the 'conflicts' line; I've just put brackets around it. Fortunately, it was correct in all of my other PKGBUILDs. The license is listed as 'GPL' because that's the way it is for the "b43-fwcutter" package in [core]. Both packages point to the same upstream URL. The license for the tarball isn't listed on the download page, nor is it mentioned in the tarball itself. Regarding the warning message, I know it's not an ideal solution. There's a lengthy discussion about it in the comments below, starting on "2014-02-09" and ending on "2015-05-22" :-). After reading through all of it, let us know if you have a better solution.

Scimmia commented on 2015-12-31 04:32 (UTC) (edited on 2015-12-31 04:41 (UTC) by Scimmia)

With pacman from git HEAD: ==> ERROR: conflicts should be an array Edit: The prompt in the build function is a bad idea. You're not supposed to need input for a pkgbuild. The license is also wrong; if it was GPL, we could redistribute it.

Xavion commented on 2015-10-22 07:48 (UTC)

I'm certainly not doing it intentionally. The "b43-fwcutter" tool creates the 'b43' directory with 750 permissions. I'm guessing those guys did it for a reason, so my inclination is to leave it alone.

xuiqzy commented on 2015-10-22 00:44 (UTC)

Is it intenional and right that after the installation the b43 directory in /lib/firmware/ has 750 permissions as opposed to all the other directories there, that all have 755?

Xavion commented on 2015-05-22 22:18 (UTC)

Okay, I've gone ahead and split the packages as noted below. Each PKGBUILD contains a warning message to inform the user of the other's existence. If the v6.30 device array ever expands significantly, I will notify "b43-firmware-classic" users accordingly via a comment to that package's webpage.

the-k commented on 2015-05-22 16:17 (UTC)

There is available.

ewtoombs commented on 2015-05-12 21:36 (UTC)

I'm having problems with version 6 as well. Sometimes, the interface gets disconnected, requiring manual intervention to bring the interface back online. When this happens, no programs can access the network, but NetworkManager still says the link is still fine. When I force NetworkManager to disassociate and reassociate, the link is fixed until the next episode. I'm trying firmware v5 now to see if there's a difference. I'll keep you posted.

skydrome commented on 2015-04-15 15:45 (UTC)

i would ask for v5 to stay its own pkg also, for my aging Acer laptop v6 firmware kills all connectivity for some reason, reverting back to v5 fixes it. using the -classic tag sounds good for it.

Halcyon522 commented on 2015-04-14 14:07 (UTC)

I think that might best serve everyone's needs. The only potential issue I could see is if future firmware upgrades to v6 widen the device array to include those of us who need to remain on v5. We would be left with deprecated firmware. I don't know how likely that would be.

Xavion commented on 2015-04-13 23:04 (UTC)

I don't have a problem with doing it that way. Does anyone disagree with Jristz's suggestion?

commented on 2015-04-13 21:46 (UTC)

Also I want tnothe that v6 improve my wireless reception compared to v5.

commented on 2015-04-13 21:45 (UTC)

I thing v5 and v6 are differents, maybe is enought to split this in 2 packages (v5 and v6 containing only the new stuff) maybe b43-firmware and b43-firmware-classic?

ta33ers commented on 2015-04-06 23:13 (UTC)

I would also like add that I had to down grade this package, I have a BCM4311, if that is of any help. Download speed went from 11mbs to 0.1mbs, and upload speed never read. Thank you for maintaining this package.

Xavion commented on 2015-04-06 21:28 (UTC)

Okay, it's looking like v6.30 has a smaller device array than v5.100. The significantly smaller tarball size of the former gives support to this theory. When I return home to my Linux box in roughly a week, I'm thinking I should: switch the PKGBUILDs back the way they were; have the default one at least notify the user about v6.30.

Halcyon522 commented on 2015-04-06 15:42 (UTC)

I can confirm Wheelman's issue. Extremely low download speeds, constant dropping. Reverting to 5.100.138-2 solved it for me. Using Broadcom BCM4311.

cemsbr commented on 2015-04-05 05:04 (UTC)

I can finally use b43 now! Too many drops with version 5, but none with 6.30 so far. I'm using a MacBook Pro 8,1 (dual boot) with "03:00.0 Network controller: Broadcom Corporation BCM4331 802.11a/b/g/n (rev 02)".

Scimmia commented on 2015-04-04 05:23 (UTC)

Yes, Wheelman, we get it, you don't have to post 4 times

Wheelman commented on 2015-04-04 05:16 (UTC)

Upgrading to caused my wireless card to drop the wifi connection constantly. Download speed dropped to 100 kbits/s. Downgrading back to 5.100.138-2 fixed it. Broadcom Corporation BCM4306 (rev 03) [14e4:4320]

Xavion commented on 2015-04-03 05:28 (UTC)

I'm not convinced it'd be worth all the effort to be honest. If v6.30 turns out to be a winner, we can throw v5.100 away altogether. I've just found the commit for v6.30, and it looks fairly legitimate: As such, I've decided to make v6.30 the default from now on. Anyone who has problems with it can simply use "PKGBUILD.old" instead.

commented on 2015-04-03 04:04 (UTC)

I pointing that "why not use one pkgbuild for both in place of 2"?

Xavion commented on 2015-03-25 22:47 (UTC)

Sorry, I had difficulty understanding your message. The "" file points to v6.30 of the firmware.

commented on 2015-03-25 21:52 (UTC)

the pagke from the download listed and as far in this 2 years look like broadcom will not anounce releases even if they do, also look like this is the last one, so look for update ot let the user decide in the pkgbuild??

MoroS commented on 2014-09-14 05:56 (UTC)

It seems that either Broadcom or the kernel fixed something as I'm running the 5.100.138 with the 3.16.2 kernel with no problems (it's the "BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)" and no need to use the 6.x version for the time being). As for the linux-grsec I think someone should change the "provides" section from kernel26-grsec to kernel26 so that one could use it as a dependency (just like Java VM packages provide the "java-environent" virtual package, that Java-based utilities use in their PKGBUILD dependencies), but that's probably to be discussed with the linux-grsec package maintainer (there also might be some circumstances that prevent them from doing so).

czubek commented on 2014-08-06 11:40 (UTC)

Thank you Xavion. I use packer -Syyu for updates and AUR updates are difficult to miss and easy to control.

Xavion commented on 2014-08-06 02:06 (UTC)

According to the ArchWiki, there's no way to specify "either 'a' or 'b'" in the "depends=()" array. Therefore, you will need to modify the PKGBUILD to suit every time this package is updated.

czubek commented on 2014-08-06 00:06 (UTC)

I wanted to switch from plain linux to linux-grsec. b43-firmware works under linux-grsec with plain linux uninstalled, but b43-firmware reinstallation depends on plain linux. Should I just change the packagebuild to indicate linux-grsec and watch for b43-firmware updates thereafter or is there a way to revise b43-firmware to accept any linux>3.2?

isacdaavid commented on 2014-06-26 14:57 (UTC)

I have tried both firmware versions under Linux 3.15, using a 14e4:4311 (rev 02) chip, and none is working for it. Thanks perseus for the heads-up.

perseus commented on 2014-06-21 20:29 (UTC)

There is a problem with the BCM 4311 (maybe other cards too, I don't know), and kernel 3.15. In case anybody comes here looking for an answer, this thread refers to it:

Xavion commented on 2014-06-11 21:28 (UTC)

Thanks for letting me know about that. Is anyone else experiencing the same problem? If so, I'll make v6.30.163.46 the default.

MoroS commented on 2014-06-11 18:44 (UTC)

@crepererum: Download the tarball. It contains two PKGBUILD files: the standard one and the Just remove the ".new" the file name and build it. It's the PKGBUILD for version 6.x.

crepererum commented on 2014-06-11 17:45 (UTC)

It seems that the current (new) kernel requires version 6.xx With the old version it worked for a long time. After some updating (sorry, forgot to check the version, because I use WIFI only rarely), I got """ b43-phy0 ERROR: Microcode not responding b43-phy0 ERROR: You must go to and download the correct firmware for this driver version. Please carefully read all instructions on this website. """ After using the new package version (, everything works fine.

Xavion commented on 2014-04-30 22:12 (UTC)

If restarting your computer and reinstalling this package doesn't fix the problem, perhaps send a message to the "b43-dev" mailing list:

Schlummi commented on 2014-04-30 15:44 (UTC)

now with Kernel 3.14.1-1 my firmware wasn't found anymore. Both Firmware Versions 5.xx and 6.xx failed: Apr 30 15:50:47 laptop kernel: b43-phy0: Broadcom 4312 WLAN found (core revision 15) Apr 30 15:50:47 laptop kernel: b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 Apr 30 15:50:47 laptop kernel: b43-phy0 ERROR: Firmware file "b43/lp0initvals15.fw" not found Apr 30 15:50:47 laptop kernel: Broadcom 43xx driver loaded [ Features: PMNLS ] Apr 30 15:50:47 laptop kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found Apr 30 15:50:47 laptop kernel: b43-phy0 ERROR: You must go to and download the correct firmware for this driver version. Please carefully read all instructions on this website. Before updating my system, on Kernel 3.13.8-1 it works very well.

Xavion commented on 2014-02-10 20:03 (UTC)

In an attempt to keep everyone happy, I've added a PKGBUILD for v6.30.163.46 to the tarball. When that version becomes official, I'll overwrite the previous PKGBUILD with this new one.

MoroS commented on 2014-02-09 22:45 (UTC)

@Xavion: It didn't hit me until now. Upstream really doesn't mention anything about version 6.x. Still, they claim that b43 does not support BCM4322. Well, that's strange since I'm using it right now with the newest package. No hangs, no problems, no error logs. Hope the instruction set is not out of date. ;) I going to test the new version for a while. As of now it seems to work nicely when operating normally and on suspending and resuming the system. If anything unusual pops up, I'll let you know. :)

Xavion commented on 2014-02-09 20:35 (UTC)

Although v6.30.163.46 is available for download, there's no mention of it at the upstream URL yet. I think we should wait for the release to become official before updating the PKGBUILD.

MoroS commented on 2014-02-09 08:51 (UTC)

@Jristz: It just seems it hasn't been updated for a while now Last Updated: 2012-12-21 02:57 I've updated the PKGBUILD to use the new version and I'm testing it right now (works well on the BCM4322). I've also e-mailed Xavion, the package maintainer about this and sent him the source package. I hope it will be updated soon. :)

commented on 2014-02-09 05:35 (UTC)

I don't get it, you download broadcom-wl version 5.100.138, but first the webpage list broadcom-wl- as major version and you get this named b43-firmware and from an older version, please you can explain this to me?

Xavion commented on 2013-11-21 06:38 (UTC)

No, it's in the "base-devel" group. See the AUR wiki page for an explanation.

qubodup commented on 2013-11-20 06:57 (UTC)

binutils seem to be required, please add :)

Xavion commented on 2013-06-20 10:28 (UTC)

I think you meant to paste all of that to the comments section of the "broadcom-wl" package instead. Either way, I recommend that you use Pastebin from now on, so as to help keep the AUR looking nice.

commented on 2013-06-20 04:30 (UTC)

I have downloaded the old version from here, but it did not solve the compilation error. I guess my kernel is too new. $ uname -a Linux inge 3.9.6-1-ARCH #1 SMP PREEMPT Fri Jun 14 08:12:55 CEST 2013 x86_64 GNU/Linux $ makepkg ==> Making package: broadcom-wl (Thu Jun 20 07:32:26 CEST 2013) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found hybrid-portsrc_x86_64-v5_100_82_38.tar.gz -> Found modprobe.d -> Found license.patch -> Found semaphore.patch -> Found mutex-sema.patch ==> Validating source files with sha1sums... hybrid-portsrc_x86_64-v5_100_82_38.tar.gz ... Passed modprobe.d ... Passed license.patch ... Passed semaphore.patch ... Passed mutex-sema.patch ... Passed ==> Extracting sources... -> Extracting hybrid-portsrc_x86_64-v5_100_82_38.tar.gz with bsdtar ==> Starting build()... patching file src/wl/sys/wl_linux.c patching file src/wl/sys/wl_iw.h patching file src/wl/sys/wl_linux.c make: Entering directory `/usr/src/linux-3.9.6-1-ARCH' LD /home/ingeborg/Downloads/broadcom-wl/src/built-in.o CC [M] /home/ingeborg/Downloads/broadcom-wl/src/src/shared/linux_osl.o CC [M] /home/ingeborg/Downloads/broadcom-wl/src/src/wl/sys/wl_linux.o /home/ingeborg/Downloads/broadcom-wl/src/src/wl/sys/wl_linux.c:43:24: fatal error: asm/system.h: No such file or directory #include <asm/system.h> ^ compilation terminated. make[1]: *** [/home/ingeborg/Downloads/broadcom-wl/src/src/wl/sys/wl_linux.o] Error 1 make: *** [_module_/home/ingeborg/Downloads/broadcom-wl/src] Error 2 make: Leaving directory `/usr/src/linux-3.9.6-1-ARCH' ==> ERROR: A failure occurred in build(). Aborting...

commented on 2013-06-19 19:32 (UTC)

Broadcom has updated their driver to version 5_100_82_112. I have tried to adjust the PKGBUILD, as follows, but I get the following error while compiling: ==> Starting build()... patching file src/wl/sys/wl_linux.c Hunk #1 succeeded at 245 (offset 5 lines). patching file src/wl/sys/wl_iw.h patching file src/wl/sys/wl_linux.c Reversed (or previously applied) patch detected! Assume -R? [n] y Hunk #1 succeeded at 555 (offset 72 lines). make: Entering directory `/usr/src/linux-3.9.6-1-ARCH' Wireless Extension is the only possible API for this kernel version Using Wireless Extension API LD /home/ingeborg/Downloads/broadcom-wl/src/built-in.o CC [M] /home/ingeborg/Downloads/broadcom-wl/src/src/shared/linux_osl.o CC [M] /home/ingeborg/Downloads/broadcom-wl/src/src/wl/sys/wl_linux.o /home/ingeborg/Downloads/broadcom-wl/src/src/wl/sys/wl_linux.c:43:24: fatal error: asm/system.h: No such file or directory #include <asm/system.h> ^ compilation terminated. make[1]: *** [/home/ingeborg/Downloads/broadcom-wl/src/src/wl/sys/wl_linux.o] Error 1 make: *** [_module_/home/ingeborg/Downloads/broadcom-wl/src] Error 2 make: Leaving directory `/usr/src/linux-3.9.6-1-ARCH' ==> ERROR: A failure occurred in build(). Aborting... My PKGBUILD: ingeborg@inge:~/Downloads/broadcom-wl$ cat PKGBUILD # Contributor: Austin ( doorknob60 [at] gmail [dot] com ) # Maintainer: Gaetan Bisson <> pkgname=broadcom-wl pkgver= pkgrel=3 pkgdesc='Broadcom 802.11abgn hybrid Linux networking device driver' url='' arch=('i686' 'x86_64') license=('custom') depends=('kernel26') makedepends=('kernel26-headers') [[ $CARCH = x86_64 ]] && ARCH=x86_64 || ARCH=x86_32 source=("${ARCH}-v${pkgver//./_}.tar.gz" 'modprobe.d' 'license.patch' 'semaphore.patch' 'mutex-sema.patch') sha1sums=('5bd78c20324e6a4aa9f3fafdc6f0155e884d5131' '4fc595e24a1f472d37384fc96aafdd2ad3688670' 'ea7b67982ddc0f56fd3becb9914fd4458fe7d373' '105f8e1d48ebe1f25d53859e5ab9326a27435c66' 'adf0138194ae204ad70ce44e98b2dc18ead4ae2a') [[ $CARCH = x86_64 ]] && sha1sums[0]='5bd78c20324e6a4aa9f3fafdc6f0155e884d5131' install=install build() { cd "${srcdir}" patch -p1 < license.patch patch -p1 < semaphore.patch patch -p1 < mutex-sema.patch make -C /lib/modules/`uname -r`/build M=`pwd` } package() { cd "${srcdir}" install -D -m 755 wl.ko "${pkgdir}/lib/modules/`uname -r`/kernel/drivers/net/wireless/wl.ko" install -D -m 644 lib/LICENSE.txt "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE" install -D -m 644 modprobe.d "${pkgdir}"/etc/modprobe.d/broadcom-wl.conf }

commented on 2013-02-03 09:54 (UTC)

link seem to be dowm

Xavion commented on 2012-07-29 00:41 (UTC)

You might need to load the 'b43' module explicitly when using 'systemd'. If that doesn't work, perhaps you should file a 'systemd' bug report.

Xavion commented on 2012-07-14 03:05 (UTC)

The archive couldn't be extracted, which probably means it was corrupt. I just rebuilt the package here without needing to modify the PKGBUILD.

throbscottle commented on 2012-07-13 20:42 (UTC)

I get: ==> Making package: b43-firmware 5.100.138-2 (Fri 13 Jul 21:37:42 BST 2012) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving Sources... -> Found broadcom-wl-5.100.138.tar.bz2 ==> Validating source files with sha1sums... broadcom-wl-5.100.138.tar.bz2 ... Passed ==> Extracting Sources... -> Extracting broadcom-wl-5.100.138.tar.bz2 with bsdtar broadcom-wl-5.100.138/: Can't restore time broadcom-wl-5.100.138/linux/: Can't restore time broadcom-wl-5.100.138/linux/wl_apsta.o: Can't unlink already-existing object broadcom-wl-5.100.138/linux/wl_ap.o: Can't unlink already-existing object broadcom-wl-5.100.138/linux/wl_sta.o: Can't unlink already-existing object broadcom-wl-5.100.138/README: Can't unlink already-existing object broadcom-wl-5.100.138/config/: Can't restore time broadcom-wl-5.100.138/config/wlconfig_lx_shared: Can't unlink already-existing object broadcom-wl-5.100.138/config/ Can't unlink already-existing object broadcom-wl-5.100.138/config/wl_default: Can't unlink already-existing object broadcom-wl-5.100.138/config/wl_hnd: Can't unlink already-existing object broadcom-wl-5.100.138/config/wlconfig_nomimo: Can't unlink already-existing object bsdtar: Error exit delayed from previous errors. ==> ERROR: Failed to extract broadcom-wl-5.100.138.tar.bz2 Aborting... Eventually installed using slightly modified line from PKGBUILD: b43-fwcutter -w ""${pkgdir}"/usr/lib/firmware/" broadcom-wl-5.100.138/linux/wl_apsta.o as root. Works okay but package database is not accurate now.

Xavion commented on 2012-07-04 06:20 (UTC)

Thanks for the notification; I've modified the PKGBUILD.

commented on 2012-07-03 20:01 (UTC)

@Xavion: there should be no need to add "b43" to the MODULES array (at least not on recent kernels). I suggest removing the message.

Xavion commented on 2012-05-09 05:37 (UTC)

Thanks for the notification; I've modified the PKGBUILD.

techryda commented on 2012-05-08 16:19 (UTC)

Please change the install location from /lib/firmware to /usr/lib/firmware as Arch is in the process of moving /lib into /usr Thanks! See the following links for more background info: - - -

commented on 2012-02-26 22:34 (UTC)

Will do. thanks.

Xavion commented on 2012-02-26 22:31 (UTC)

That means you might have problems building future architecture-specific packages. In the event that this happens, you might need to reopen that 'pacman' bug report.

commented on 2012-02-26 22:23 (UTC)

thanks. But, mine were already enabled. ######################################################################### # ARCHITECTURE, COMPILE FLAGS ######################################################################### # CARCH="x86_64" CHOST="x86_64-unknown-linux-gnu" Happy to be back on wireless :-)

Xavion commented on 2012-02-26 22:19 (UTC)

Be sure to fix your "/etc/makepkg.conf" file as noted below. I've modified the 'arch' array in the PKGBUILD as requested.

commented on 2012-02-26 22:13 (UTC)

That worked! Updated my PKGBUILD file to arch=("any") and it built an any package and installed it. Wireless is working now. I didn't know I could change the architecture like that and it have any effect. thanks falconindy!

falconindy commented on 2012-02-26 21:40 (UTC)

This package has no architecture -- nothing is compiled. Please mark it as arch=('any')

commented on 2012-02-26 21:13 (UTC)

Reported bug. Thanks for the advice. If you upload a 64bit build of the package to github, I could grab it from there perhaps? Or wherever :-) Thanks for your help. It is much appreciated.

Xavion commented on 2012-02-26 21:04 (UTC)

Ensure that these two lines are enabled in your "/etc/makepkg.conf" file: CARCH="x86_64" CHOST="x86_64-unknown-linux-gnu" If that doesn't fix it, re-perform the steps outlined on the following webpage: Let me know if these suggestions - and the bug report advice - have no effect.

commented on 2012-02-26 20:32 (UTC)

Yeah, I agree. Something is not right. I did as you asked. PKGBUILD now reads: arch=("x86_64") I ran makepkg -s again Then I get this: ==> ERROR: b43-firmware is not available for the 'i686' architecture. Note that many packages may need a line added to their PKGBUILD such as arch=('i686'). You'd think that would read as x86_64, not i686 given the previous messages. I will file a bug report. I'll start looking over my config files more too. Maybe I missed something.

Xavion commented on 2012-02-23 21:43 (UTC)

I think the problem has to be caused by one of your configuration files. Perhaps just remove "i686" from the 'arch' array in the PKGBUILD and rebuild the package. Let me know if this doesn't work-around the problem and I'll upload a 64-bit package for you somewhere. In the meantime, I advise you to lodge a bug report for the maintainers of 'pacman'.

commented on 2012-02-23 02:19 (UTC)

Thanks. Actually, I show the same list with pacman -Qs gcc I updated my info here to avoid duplication. I'm beginning to consider buying a USB adapter for a few days.

Xavion commented on 2012-02-19 01:42 (UTC)

I just rebuilt this package on my 64-bit machine without any problems. FYI, I had the following 'gcc' packages installed at build-time: `--> packer-color -Qs gcc local/gcc-libs-multilib 4.6.2-7 Runtime libraries shipped by GCC for multilib local/gcc-multilib 4.6.2-7 (multilib-devel) The GNU Compiler Collection - C and C++ frontends for multilib local/lib32-gcc-libs 4.6.2-7 Runtime libraries shipped by GCC (32-bit)

commented on 2012-02-18 02:56 (UTC)

Is anyone getting an invalid architecture message when trying to install this package on 64bit? I even have multi-lib installed. I've been trying to get help in the forum. But maybe this is a better place to ask the question? Thanks if you can point me in the right direction. package b43-firmware-5.100.138-1-i686 does not have a valid architecture

commented on 2012-01-31 06:46 (UTC)

Thx for your work!

commented on 2012-01-31 06:46 (UTC)

Thx for your work!

Xavion commented on 2012-01-19 21:53 (UTC)

As Linux v3.2.x is now in 'core', this package needed to be upgraded. This is because Arch Linux aims to be a "bleeding edge" distribution. For anyone who has trouble with the new firmware, I've left a copy of the previous PKGBUILD in the tarball.

muunleit commented on 2012-01-19 18:13 (UTC)

@robvelor: The pkg requires it not really, you could just rebuild it. @Xavion: The current pkg works well here with linux 3.2.1 .

robvelor commented on 2012-01-19 17:30 (UTC)

New kernel update, b43-firmware: requires linux<3.2 upon update.

kabbalah commented on 2012-01-13 22:43 (UTC)

Ok, solved issue. Thank Xavion

Xavion commented on 2012-01-13 21:19 (UTC)

Based on this new information, I've removed the versioned dependency. You are now free to use this older firmware with the Linux v3.2 in 'testing'.

wonder commented on 2012-01-12 22:48 (UTC)

@kabbalah yes, the versioned dependency is wrong. OLD firmware works with linux 3.2, NEW firmware doesn't work with old linux. you can keep until linux 3.2 hits core and then you can update to 5.100.138

kabbalah commented on 2012-01-12 22:11 (UTC)

Ok, I use Testing since two years, and no problem updating my system, then now seem that every time that change the kernel, then b43-firmware will no allow that update my system, until the kernel has been moved from 'testing' to 'core'. How emerged this issue? Which is the solution for it? For all. Or, then I will need no use Testing?

kabbalah commented on 2012-01-12 22:07 (UTC)

Ok, I use Testing since two years, and no problem updating my system, then now seem that every time that change the kernel, then b43-firmware will no allow that update my system, until the kernel has been moved from 'testing' to 'core'. How emerged this issue? Which is the solution for it? For all. Or, then I will need no use Testing?

Xavion commented on 2012-01-12 21:23 (UTC)

Please note that the "b43-firmware-latest" PKGBUILD incorrectly lists Linux < v3.2 as a dependency. Until the maintainer of that package changes it to require Linux >= v3.2, anyone attempting to use it will need to do so themselves.

muunleit commented on 2012-01-12 06:42 (UTC)

@kabbalah The reason is easy to explain. If Xavion would update the pkg now, everyone not using 'testing' could not use this pkg. In the mean time you can try the b43-firmware-latest-pkg I guess.

kabbalah commented on 2012-01-12 04:40 (UTC)

I not understand, when I updated my archlinux, no problem, but now you is tell me that "After Linux v3.2 has been moved from 'testing' to 'core', I'll update this PKGBUILD accordingly". Then, meantine I can't use Testing for realize my update? Please, explain me the reason for it decision. Cordially kabbalah

Xavion commented on 2012-01-10 21:29 (UTC)

This package currently requires Linux < v3.2, where '<' means "earlier than". In other words, you should install the 'linux' package (v3.1.8) from the 'core' repository instead. After Linux v3.2 has been moved from 'testing' to 'core', I'll update this PKGBUILD accordingly.

kabbalah commented on 2012-01-10 16:55 (UTC)

There is error in my comment: It is correct one: 1. b43-firmware, is impossible install! When update with testing include, ultimately it tell me: b43-firmware: necesita linux<3.2 error: error al preparar la transacción (no se pudieron satisfacer las dependencias) 2. I erase b43-firmware, for I can install linux 3.2-2, since I can't update, it tell me "b43 necesita linux 3.2" 2. I installed linux 3.2-2 since pkgbuild, now when want install b43-firmware since Aur, it tell me that it need as dependence: b43-firmware: necesita linux<3.2 error: error al preparar la transacción (no se pudieron satisfacer las dependencias) 3. edited the pkgbuild of b43, to change linux 3.3 by linux 3.2-2 but nothing appear the same error. Then with Testing active I can't update archlinux.

kabbalah commented on 2012-01-10 16:49 (UTC)

!b43-firmware, is impossible install! When update with testing include, ultimately it tell me: b43-firmware: necesita linux<3.2 error: error al preparar la transacción (no se pudieron satisfacer las dependencias) I installed linux 3.2-2 since pkgbuild, now when want install b43-firmware since Aur, it tell me that it need as dependence: b43-firmware: necesita linux<3.2 error: error al preparar la transacción (no se pudieron satisfacer las dependencias) I edited the pkgbuild of b43, to change linux 3.3 by linux 3.2-2 but nothing appear the same error. Then with Testing active I c'not update archlinux. I

commented on 2012-01-08 22:35 (UTC)

@alperkanat: I was using the wl module just fine until today.

alperkanat commented on 2012-01-08 00:27 (UTC)

Anyone able to use this driver with BCM4321?

Xavion commented on 2012-01-07 21:40 (UTC)

As a result of the problems reported by users of BCM4312 devices, I've decided to revert this package to the previous version. The tarball still contains the PKGBUILD for the newer firmware as well, in case some users want to check if it works with their devices.

commented on 2012-01-07 14:25 (UTC)

I'm experiencing the same problems as pointed out in the post from muunleit on Tue, 03 Jan 2012 19:33:02 +0000 I'm using the same hardware (BCM4312) with kernel 3.1.6 and 3.1.7, identical error msgs. Downgrading to fixed it.

Xavion commented on 2012-01-06 06:10 (UTC)

I'm guessing you meant that v5.10.144.3 (for Linux < v3.2) works for you. Let me know if you were referring to v5.100.138 (for Linux >= v3.2) instead. Linux v3.2 is still in the 'testing' repository, so this package isn't yet out-of-date. I'll upgrade its version once Linux v3.2 is moved into 'core'.

mmm commented on 2012-01-05 17:20 (UTC)

linux 3.2 is out, works for me

Xavion commented on 2012-01-05 09:45 (UTC)

I do value your opinion - as an Arch developer - but there are a few things to consider first. I'll start by referring to the "List of firmware" table: All of the firmware intended for v015 of the "b43-fwcutter" package is hosted at the "" domain. It's probable that the Larry Finger - who responded to my initial mailing list posting - is the owner of this domain. These two pieces of information led me to believe that he might be the new guy in charge of 'b43'. In this case, it's quite possible that he simply hasn't bothered to update the version recommendations on the website yet. The advice he gave me in his response confirmed what I had suspected: that upgrading could be beneficial to some users of the newer 'b43' devices. It also seemed unlikely that Broadcom would release firmware that cripples older chips. The fact that only one user has reported a problem with the new firmware could be seen as a positive sign. I'm wanting to get negative feedback from at least one additional user before deciding to roll-back this upgrade.

wonder commented on 2012-01-05 08:04 (UTC)

in my opionion you should stick with versions advised on the b43 wiki. If you are using the b43 driver from 3.2 kernel or newer: 5.100.138 If you are using the b43 driver from older kernel:

Xavion commented on 2012-01-04 00:57 (UTC)

I'm sorry to read that you've run into problems with the new firmware. I've included the old PKGBUILD file in the tarball for users who need to revert. I've asked the 'b43' developers about this problem. You can follow the thread here:

muunleit commented on 2012-01-03 19:33 (UTC)

I have problems with todays upgrade. I have a BCM4312 (, which works the last version, but not with todays upgrade. Kernel-Log with => Kernel-Log with =>

Xavion commented on 2012-01-03 09:48 (UTC)

Based on Larry's response to my question, I decided to take the plunge and upgrade this package. My main reason for doing so was because it could positively impact some of the newer 'b43' devices. Let me know if any catastrophic problems surface as a result and we can look at a rollback.

Xavion commented on 2011-12-31 00:30 (UTC)

Without knowing the specifics, it looks like openSUSE has upgraded to v5.10.144.3. I've requested some clarification from the 'b43' developers about this matter. You can follow the thread here:

Moo-Crumpus commented on 2011-12-30 14:33 (UTC)

The package is not outdated. It is the package ' firmware', matching kernel versions < 3.2. There are different combinations of fwcutter/firmware for kernels < 3.2 and >= 3.2. This is matching linux kernel < 3.2, and is the latest firmware for this kernel version. I doubt there will ever be a newer one.

commented on 2011-12-30 10:54 (UTC)

stuvjordan: have you tried downgrading fwcutter? And also, have you tried using broadcom-wl-5.100.138 instead?

commented on 2011-12-30 02:16 (UTC)

So, I'm having some trouble with b43 and broadcom hardware (like everyone does) and I just noticed something that's potentially a problem. (although I'm not really sure where I should post this). The version of fwcutter that is in the package repository is 015-1. The version of the firmware here is But the linuxwireless webpage seems to say (if I'm reading it right) that fwcutter v. 14 supports firmware v., but that fwcutter v 15 does not. To see what I'm talking about go to and search down the page to the table right under the "list of firmware" heading. does this mean that if I'm getting my fwcutter from the package repo, I need to be using firmware v. 5.100?

commented on 2011-11-13 11:22 (UTC)

I tried, but it doesn't work. I think the problem is because of kernel (I had to install testing release). Thank you very much for help. Regards!

Xavion commented on 2011-11-12 23:33 (UTC)

Just follow the instructions given in the 'Debian' section of the above website. More specifically, go here:

commented on 2011-11-12 21:30 (UTC)

Hello everybody. I'm sorry, is there any way to install this firmware on debian? I am really tired trying to solve this out :/ I've just installed GNOME 3 which is only for testing release - Wheezy and I've lost my wireless connection. I am trying to follow this guide: so I need to install this firmware I think.

Xavion commented on 2011-10-14 04:57 (UTC)

Uh, I got that information from the website listed above :-/. Just search on it for "using the b43 driver from 3.2 kernel or newer".

hollunder commented on 2011-10-13 12:09 (UTC)

3.2? Where did you get this from? But yeah, current b43-firmware-latest doesn't work for me, scans return nothing, so I'm stuck with this version.

Xavion commented on 2011-09-26 01:17 (UTC)

The v5.100.138 release that you mentioned requires v3.2 of the Linux kernel. I'll wait until this is in 'core' before making the changes that you've requested.

Huulivoide commented on 2011-09-25 08:51 (UTC)

"""DIFF""":: -b43-fwcutter -w ""${pkgdir}"/lib/firmware/" driver/wl_apsta/wl_prebuilt.o +b43-fwcutter -w "${pkgdir}/lib/firmware/" linux/wl_apsta.o And remove the msg as the module is autoloaded ^^

Huulivoide commented on 2011-09-25 08:44 (UTC)

More up to date versions can be fround from:${pkgver}.tar.bz2 5.100.138 is the newest version and requires version 15 of the tools

Xavion commented on 2011-09-01 22:13 (UTC)

Thanks for pointing that out. I guess I was just being too cautious. I've removed the empty 'build()' function.

Huulivoide commented on 2011-09-01 18:50 (UTC)

whats the idea behind: build() { /bin/true } ? Build function isint needed at all O_o

rafaelff commented on 2011-08-02 17:48 (UTC)

I'm using the correct firmware then. Thanks a lot for the information.

Xavion commented on 2011-08-02 06:04 (UTC)

You can read all about the two drivers on the following webpages. Since you have a BCM4313 chip, you need to use the 'brcm80211' driver. * *

rafaelff commented on 2011-08-02 03:12 (UTC)

Please don't understand this as a critic, but as a doubt. What is the difference between this firmware and the 'brcmsmac' module availabe in newer linux kernel (2.6.37+, afaik)? I have a BCM4313, so I suppose this is interesting for me as well.

dapolinario commented on 2011-06-16 21:11 (UTC)

New version:

Xavion commented on 2011-04-12 06:21 (UTC)

Thanks for the suggestion; I've updated the PKGBUILD.

commented on 2011-04-11 12:57 (UTC)

please, s/b43-fwcutter=013/b43-fwcutter>=013 otherwise it will not work as of today because b43-fwcutter is at 014 now otherwise, thanks ;-)

commented on 2010-10-14 02:48 (UTC)

tks @Xavion, this works for me

Xavion commented on 2010-08-06 22:40 (UTC)

If you want to trial Broadcom's STA driver, just search on the AUR for "broadcom-wl".

commented on 2010-08-06 17:04 (UTC)

Hey, do you think that there might be an advantage in updating this firmware? If you look at here, you will see a quite new firmware for BCM4311, like I use, being offered by Broadcom Corporation. It is version, so it is much newer than Bests dazzy.