There is a common problem with some cards managed with the b43 driver, it gets disconnected randomly, with an error in dmesg saying: Using broadcom-wl did the trick and things are working great.- Skarphace ( talk) 05:16, 21 July 2012 (UTC) The signal was so weak it wouldn't obtain an IP address from DHCP, even right next to the AP. I could not get this to work with the kernel drivers. I'm running a new dv7-7000 with a Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01). The experiment results from trying the 3 firmware versions on my LP-PHY rev 01 are on this google sheet. I don't know what's the difference, but I'm going to go try them all out. It's just a different version of the driver.
#Broadcom bcm4360 linux driver install
An install script at downloads broadcom-wl-5.100.138.It links to an installer on github that downloads broadcom-wl-4.178.10.4.It describes a manual download of broadcom-wl-4.178.10.4.ArchWiki "Loading the b43/b43legacy kernel module" has a couple leads:.All of them do approximately the same thing with b43-fwcutter. There are a bunch of different packages/instructions/etc for getting the firmware.
Dustmote ( talk)Ĭan it (the package b43-fwcutter) be used to replace the manual download explained below (on ArchWiki "Loading the b43/b43legacy kernel module")? How does it (the package b43-fwcutter) relate to the external scripts and/or the AUR packages listed?ī43-fwcutter is required by all of the options listed to extract the firmware from the driver. 7 Installation: broadcom-wl is in the official repos nowĭiscussion from ArchWiki "Loading the b43/b43legacy kernel module".6 BCM4331 works better with broadcom-wl-dkms than with b43-firmware.
0 kommentar(er)
