Package Details: b43-firmware-classic 5.100.138-1

Git Clone URL: https://aur.archlinux.org/b43-firmware-classic.git (read-only, click to copy)
Package Base: b43-firmware-classic
Description: Firmware for Broadcom B43 wireless networking chips - trusted release
Upstream URL: https://wireless.wiki.kernel.org/en/users/Drivers/b43
Licenses: unknown
Conflicts: b43-firmware
Submitter: Xavion
Maintainer: skmtrn
Last Packager: Xavion
Votes: 16
Popularity: 0.000000
First Submitted: 2015-05-22 22:04 (UTC)
Last Updated: 2015-12-31 21:30 (UTC)

Latest Comments

1 2 Next › Last »

visious commented on 2022-08-30 10:55 (UTC)

@skmtrn Hi, I have already tested with an other kernel and it's working only you can change the line 11 in PKGBUILD. In line 25 leave it as default option: From: depends=("linux>=3.2") To: depends=("linux-lts>=3.2")

And then you have to remove manually: sudo pacman -R linux, for some reasons makedepends, but it doesn't worth to switch kernel at all.

Btw you should add in PKGBUILD: /etc/modprobe.d/b43-firmware.conf

blacklist b43legacy

Activate experimental support for some hardware revisions

options b43 allhwsupport=1

For better functionality of Broadcom driver.

To both b43-firmware-classic and b43-firmware. I have tested both firmwares, I didn't see much difference at all.

visious commented on 2022-08-20 19:11 (UTC)

@skmtrn Thank you for your advice. I'll post you again when I decided to switch kernel anyway.

skmtrn commented on 2022-08-20 18:53 (UTC)

@visious5d: there is no need, b43-fwcutter is extracting the drivers from the upstream provided by the hardware producer, it is pointing to extract them from 'linux' folder where they simply stored linux drivers, changing it would actually break this PKGBUILD's functionality

visious commented on 2022-08-20 15:55 (UTC)

Hi, if switch kernel to linux-lts. Do I have to change the line 25 in PKGBUILD? I know for sure to change the line 11.

From: depends=("linux>=3.2") To: depends=("linux-lts>=3.2")

From: b43-fwcutter -w "${pkgdir}"/usr/lib/firmware/ linux/wl_apsta.o To: b43-fwcutter -w "${pkgdir}"/usr/lib/firmware/ linux-lts/wl_apsta.o

mahdi commented on 2022-01-15 19:00 (UTC) (edited on 2022-01-15 19:31 (UTC) by mahdi)

After installation still you have to run # modprobe b43 on every boot. When you uninstall broadcom-wl-dkms that problem solves

Fixed commented on 2020-03-02 14:44 (UTC)

My BCM4318 works, but with high asymmetry -- download is just 0.5 Mbit/sec, uopload about 12 Mbit/sec. USB WiFi dongle gives 7 Mbit/sec. Tests by speedtest.com

USB Wi-Fi dongle gets 20 Mbit/sec

Xavion commented on 2016-11-06 19:27 (UTC)

You won't be able to build/install any AUR packages via 'pacman': it only works with prebuilt (i.e. repository) packages. To access the AUR, you will need to use something like 'yaourt' instead.

soap commented on 2016-11-06 10:17 (UTC)

From the Newbie Corner Had problems installing this package via pacman: #pacman -S b43-firmware-classic So here is what I did to install it: cloned it with git (make sure you have installed git via pacman): git clone https://aur.archlinux.org/b43-firmware-classic.git cd b43-firmware-classic/ created a packge with makepkg (make sure you have installed the base-devel package via pacman): makepkg -s after creating the package I installed the b43-*.xz package via pacman: #pacman -U b43-*.xz after the installation is complete reboot You should see the your br wl interface ip link

Xavion commented on 2015-11-10 00:13 (UTC)

People have been telling me to do that my whole life. They never seem to consider that I might be bipolar-1.

1 2 Next › Last »