Package Details: broadcom-wl-lts 6.30.223.271-2

Git Clone URL: https://aur.archlinux.org/broadcom-wl-lts.git (read-only, click to copy)
Package Base: broadcom-wl-lts
Description: Broadcom 802.11abgn hybrid Linux networking device driver for LTS kernal
Upstream URL: https://www.broadcom.com/support/802.11
Licenses: custom
Submitter: Reficul
Maintainer: Reficul
Last Packager: Reficul
Votes: 1
Popularity: 0.000000
First Submitted: 2016-02-25 04:18 (UTC)
Last Updated: 2016-12-16 08:04 (UTC)

Latest Comments

jdubs commented on 2017-12-19 15:24 (UTC)

Is this package abandoned?

uwolfer commented on 2017-08-17 17:16 (UTC)

I cannot build this package anymore. Log: https://pastebin.com/PJW4Xh66 Any ideas?

Reficul commented on 2016-12-16 08:23 (UTC)

@Raimar Thank you for reminding.

Raimar commented on 2016-12-05 21:14 (UTC)

Download URLs have been changed: https://docs.broadcom.com/docs-and-downloads/docs/linux_sta/hybrid-v35-nodebug-pcoem-6_30_223_271.tar.gz https://docs.broadcom.com/docs-and-downloads/docs/linux_sta/hybrid-v35_64-nodebug-pcoem-6_30_223_271.tar.gz See, e.g. https://slackbuilds.org/repository/14.2/network/broadcom-sta/

severoraz commented on 2016-05-01 19:41 (UTC)

Has anybody tested this with BCM4352?

amatriain commented on 2016-03-14 16:44 (UTC)

It seems to work now, thanks.

Reficul commented on 2016-03-12 16:12 (UTC)

@amatriain: This package is modified from broadcom-wl. This issuse may be caused by some parameters I missed. I'm sorry for my mistake and I will try to fix it soon.

amatriain commented on 2016-03-12 09:05 (UTC)

Tring to update this package gives an error: error: failed to commit transaction (conflicting files) broadcom-wl-lts: /usr/lib/modprobe.d/broadcom-wl.conf exists in filesystem Errors occurred, no packages were upgraded. That file is owned by the broadcom-wl package: $ pacman -Qo /usr/lib/modprobe.d/broadcom-wl.conf /usr/lib/modprobe.d/broadcom-wl.conf is owned by broadcom-wl 6.30.223.271-2 It seems the latest version of broadcom-wl-lts cannot be installed in the same computer as the broadcom-wl package. Older versions did not have this limitation. Perhaps the filename in this package could be changed to broadcom-wl-lts.conf to avoid the collision? It makes sense having both broadcom-wl and broadcom-wl-lts installed at the same time. I usually keep both linux and linux-lts installed, I usually boot with linux but I can revert to linux-lts if an update breaks my system (it happened in the past). With this setup I need both broadcom-wl and broadcom-wl-lts installed so I have wifi with any kernel I choose to boot.