I just went through the process of installing Arch by hand, and set up Gnome and NetworkManager. The wifi works perfectly fine on Arch, which helps narrow things down because we know it’s a specific issue with the way Antegros configures things, combined with the recent packageset.
Ruoh: I’m afraid I’m all up to date. Also, waiting for something to fix itself is a course of action but not a solution I’m afraid.
I’m having an issue with a Broadcom wifi chip (surprise surprise) that I can’t find anything online about, and I’ve exhausted all the methods that the wiki recommended, so here I am.
It’s a BCM432b wifi which is built into my 2009 unibody MacBook Pro. While the device is clearly visible to all programs, none of them are able to access it for scanning.
This holds true with all programs tested, whether graphical or not. The Gnome menu shows the wifi device as enabled but the network list stays empty; wifi-menu says “Scanning for networks… failed.” iw prints nothing at all. It also behaves the same way on every driver that I’ve tested, including but not limited to: b43, b43legacy, Broadcom-wl, and broadcom-wl-dkms. It’s not rfkilled either. I’m running all the commands as root.
But here’s the part that drives me crazy: on the latest Antergos Live CD, it works perfectly fine. I scan for, and connect to, networks without any problem. I can only assume there’s some recent package update that broke it. That’s why I included the live CD’s pacman -Q below. I’ve tried downgrading wpa-supplicant, and using the LTS kernel with Broadcom-wl-lts, but neither of those work. The driver on the cd was the latest one as well, so I’m not sure what else to try downgrading.
Also, this may be totally expected, but I’m noting it just because I’m unsure: when I install Antergos as “core” (meaning no GUI at all) it can’t see wifi or Ethernet at all. Is that just a lack of automatic module loading, or is it a sign that something that comes with gnome is handling it and might be responsible? (I’m sure it’s the former.)
Thanks so much!