Hi there, so I personally do not have this problem because I have an Intel wireless card but I have helped a few of my friends who have Macbook Pros and after installing the Broadcom wireless driver from doflicky the system will not connect to a wireless network that is password protected (it just keeps spitting out the enter password prompt like the password is wrong when I know it is not) but the card has no problem when the network is open.
I have a macbook pro and I can confirm this issue, but I can also say it is with all distros like this. it has to be the broadcom driver or the combo between network manager and the broadcom driver
There are several issues actually with the broadcom driver, they all appear randomly:
- the wifi gets dropped and the card is not recognizing any networks anymore.
- it keeps asking to confirm the password
I have tried a plethora of solutions found on the internet, but none of them work, except putting the computer to sleep by closing the lid and keeping it like that for 10 seconds. Afterwards you can go on again for a while.
The timings of the problems can range from 15min to 5-6 hours, not related to a specific network and/or a specific location.
On my Broadcom card:
lspci | grep -i network 12:00.0 Network controller: Broadcom Limited BCM4313 802.11bgn Wireless Network Adapter (rev 01)
I have this problem every once in a while.
I'm not sure, but I believe it happens mainly after wake-from-suspend and/or after updating broadcom drivers (from software center updates, of course).
I solve this by running this command in terminal:
sudo systemctl start NetworkManager.service
After waking from suspend (sometimes), the wifi password dialog pops-up. If I try to connect, it spins for a while, doesn't connect, wifi password dialog again.
If at that moment I try:
sudo systemctl status -l NetworkManager.service
I'll get this output:
user@host ~ $ sudo systemctl status -l NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib64/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since lun 2017-08-28 14:26:21 -03; 2 days ago Docs: man:NetworkManager(8) Main PID: 667 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─667 /usr/sbin/NetworkManager --no-daemon ago 30 22:35:48 host NetworkManager: <info> [1504143348.5598] device (wlp18s0): supplicant interface state: associating -> disconnected ago 30 22:35:53 host NetworkManager: <info> [1504143353.5606] device (wlp18s0): supplicant interface state: disconnected -> scanning ago 30 22:35:57 host NetworkManager: <info> [1504143357.3943] device (wlp18s0): supplicant interface state: scanning -> disconnected ago 30 22:35:58 host NetworkManager: <info> [1504143358.8638] device (wlp18s0): supplicant interface state: disconnected -> scanning ago 30 22:35:59 host NetworkManager: <info> [1504143359.1678] device (wlp18s0): supplicant interface state: scanning -> associating ago 30 22:35:59 host NetworkManager: <info> [1504143359.1994] device (wlp18s0): supplicant interface state: associating -> 4-way handshake ago 30 22:36:06 host NetworkManager: <info> [1504143366.3933] device (wlp18s0): supplicant interface state: 4-way handshake -> disconnected ago 30 22:36:06 host NetworkManager: <info> [1504143366.3955] device (wlp18s0): Activation: (wifi) disconnected during association, asking for new key ago 30 22:36:06 host NetworkManager: <info> [1504143366.3957] device (wlp18s0): state change: config -> need-auth (reason 'supplicant-disconnect') [50 60 8] ago 30 22:36:06 host NetworkManager: <info> [1504143366.4932] device (wlp18s0): supplicant interface state: disconnected -> inactive
After a service restart, wifi connects almost immediately:
sudo systemctl restart NetworkManager.service
Not sure if I had this particular issue, or if these things are related, but I was NOT connecting to any of my Wi-fi access points using the Broadcom wireless driver, either. I have an AC1300 / Archer T6E Wireless Dual Band PCI Express Adapter (branded TP-Link). I had to install the wireless drivers using DoFlicky, update my computer fully, and then install the proprietary Nvidia binary blob for my GPU (a GeForce GTX 660). I tried restarting and re-installing the wireless driver first, as well - I'm pretty sure it was only after installing the Nvidia binary driver that the wireless driver properly connected to my wi-fi access points. After that, it finally was able to connect easily.
Anyway, it might be something to keep in mind?
Someone correct me if I am wrong but doflicky mainly deal with proprietary drivers, correct? Regardless this, and I say this non-critically, is a simple matter of oversight I think. Basically at one point many of the broadcom drivers were developed open source by the community with no support from broadcom. Eventually broadcom gave support thru broadcom-sta. Broadcom-sta does't support certain older wireless cards. BCM4313 uses brcmsmac instead. Other than broadcom-sta there I think are 5 other b43 related device drivers. If broadcom-sta is the only one available then a number of broadcom cards will not work with Solus. Perhaps the following driver packages can be integrated into doflicky https://wiki.debian.org/bcm43xx or those that aren't?
I have same issue as well. They way to fix it, is to "Forget" that netwrok, because the first time it took the wrong password. Once you press "Forget" then it will take the correct password. I don't know why passing a wrong password wont let the correct password to be passed.
Broadcom wireless is the reason I won't buy another Apple laptop.
One way distros handle this is to package b43-fwcutter and have actual driver packages (b43) that uses b43-fwcutter to install the driver. The other way is to use the 3rd party drivers manager, which I believe *buntu-like distros do.
In the meantime, following those instructions will get you up and running.
Also, not every feature is supported on every card with the reverse-engineered broadcom drivers. The card in a machine I was using wouldn't connect to 5ghz networks, for instance. It's possible that some issues are just the way it is.
TY so much spacecase for that reference.
As many older apple laptops cannot be updated even to sierra, their price is dropping and they become very attractive as a Linux box. My own MacBook Air 1,1 cannot even go past Lion. They can be had for $80. Build is gorgeous. I would dearly love to use it with Solus and am working on that now. The Budgie 3 ISO does not see it's Broadcom 4321. I'm using a USB adapter to try to get to the latest kernel and get it working, but at the moment I'm stuck at the grub with black screen after update--unrelated I'm working on that. I will report here on wifi after my current hurdle.
My point is: any distro which can handle apple intel laptop hardware, especially the older stuff, will gain credibility and users in the wider world. I have many clients who may be candidates right now. So the apple quirks, like 32 bit efi on some systems, these awful broadcom things, etc, are worth a little love because the efforts really will win some hearts.