Problem installing Broadcom drivers, unable to power on the network device.
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Problem installing Broadcom drivers, unable to power on the network device.
ust installed Mint on a Lenovo laptop, but I cannot get the wireless card to work. lspci shows BCM43142, pci-id 14e4:4365 From ehat I can tell, 4365 is supposed to be compatible with bcmwl-kernel-source, but I sure as h can't get it to work.
I've tried b43-firmwarecutter -w wl_apsta.o (obviously after I downloaded it) and firmware-b43-installer. Neither does bcmwl-kernel-source, or firmware-b43legacy-installer.
Theclosest I've gotten is with bcmwl-kernel-source, with this wireless actually shows up in the network manager, but it is powered off and it's not possible to turn it on. If I try to turn it on, the slider instantly goes back to the off position. iwconfig also says the device is in a "powered off" state. ifconfig up says "Operation not possible due to RF-kill". Various modprobe b43, w1 etc makes no difference either. Secure boot is disabled. Any ideas?
This laptop does not have a on/off switch for the network card. It's only windows 10's "airplane mode" ,which for the record I made sure was disabled beforehand.
I've installed and re-installed bcmwl-kernel-source 4 or 5 times and rebooted a two digit number of times, but it appears that the standard installation procedure just doesn't cut it this time.
I've deployed Linux on many computers before and -with the exception of a few cranky Intel graphics cards-, I've never really had any extensive driver issues like this time. Most of the time everything "just works" -at least with some kind of generic driver, even if the component in question performs below par, it does still work.
This computer is mainly used for surfing and document/office work and even if the network card does not work at full performance it does not really matter, as long as it's actually working. Besides, the router that's within range in this part of the building is ancient and only supports 11mb/s anyway hehe.
I've tried b43-firmwarecutter -w wl_apsta.o (obviously after I downloaded it) and firmware-b43-installer. Neither does bcmwl-kernel-source, or firmware-b43legacy-installer.
Use one or the other. one is blacklisted.
If used the open source one bcma and you installed the b43. then you need to blacklist it.
in the beginning the b43 came without firmware. Why because the program firmwarecutter
is under a different licence. None distributional. make you go download it.
So we kept a /etc/modprobe.d/blastlist.conf file.
choose your module.
I also had such issues. I think i changed something in the kernel also
Quote:
ASUS-G75VW .... # zgrep RFKILL /proc/config.gz
CONFIG_RFKILL=y
CONFIG_RFKILL_LEDS=y
CONFIG_RFKILL_INPUT=y
# CONFIG_RFKILL_GPIO is not set
CONFIG_ATH9K_RFKILL=y
# CONFIG_AMILO_RFKILL is not set
# CONFIG_TOSHIBA_BT_RFKILL is not set
You need the proper kernel setting, proper kernel module and proper hardware id. Sometimes you need to patch the kernel for the proper hardware id also. And you need to know how to setup wireless also.
edit: reading @ post #5. you also need the firmware for the wifi card
Sorry for the late answer guys, have been some busy weeks lately.
The computer does have UEFI and as jefro suggested, there might be some issues regarding this, not sure.
At the time it had a dual boot configuration with win10, and with the recent meltdown/spectre issues MS pushed an update that rendered the entire computer usesless. At least one BSOD every few minutes, and sometimes it crashed during boot as well.
I got so fed up with this, and to be able to actually use this thing (Especially my GF who uses this partucular computer the most) i disabled everything UEFI and enabled legacy BIOS only. Formatted the drive and installed a Win7 ultimate and permanently disabled windows update to avoid any meltdown-patches that might screw it up again. For some reason the pre-installed win 10 home license also worked on the 7 Ultimate... Weird.
Bottom line is that after getting rid of win10 the computer now works better than ever, and my GF has decided to just leave it like this for now.
Maybe I'll experiment further another time, who knows?
Anyway, thanks for all your suggestions, much apreciated!
did you copy the extracted (fwcutter) firmware to /lib/firmware/b43/ ??? AKA the location the module loads it from. Having something is not the same as "using" it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.