Package Details: b43-firmware 6.30.163.46-1

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 14 Next › Last »

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: https://github.com/mbuesch/b43-tools/commit/f9ea2d59b33b552994a9c7ad3ca8fa1ef9992b95 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.

<deleted-account> 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 "PKGBUILD.new" file points to v6.30 of the firmware.

<deleted-account> commented on 2015-03-25 21:52 (UTC)

the pagke from the download listed http://www.lwfinger.com/b43-firmware/broadcom-wl-6.30.163.46.tar.bz2 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?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 14 Next › Last »