Repository navigation
2016 MacBook Pro bizarre WiFi behavior #4692
Replies: 41 comments 1 reply
|
On second attempt at install, I got this same issue. Waiting and retrying multiple times worked again. |
|
When you scan shows my networks, does it list your networks? |
|
@adamavenir Do you happen to have a 802.11ac from broadcom? Check with If you have |
|
For those of us who are noobs in linux, how do you do this? (I have the following controller: Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02))
|
It depends on which bootloader you use, but if it's Limine, see https://github.com/limine-bootloader/limine/blob/v9.x/CONFIG.md it may also be helpful to look at https://wiki.archlinux.org/title/Limine Essentially you will just add For example, if using systemd-boot, you will likely have a conf file located in /boot/loader/entries/ with a line that says "options". you would add that string to the end of that line. It's also possible you will need to create a blacklist for modprobe (you can look that up for your specific wifi card) but if it's a broadcom bcm43602, this is what worked for me: Create a file /etc/modprobe.d/broadcom-wifi.conf (filename doesnt matter) and give it the following contents: It may go without saying but after either of these changes, you need to reboot. |
|
@bcorcoran thanks a million. @pettersj fyi working on testing a fix for this, if it works will submit a PR here. |
Let me know if you'd like to collaborate on the PR! I was going to work on one myself. |
|
@bcorcoran Absolutely by all means, go for it! You're the one who pointed in the right direction with the Broadcom fw. I wrote a presumptive fix in the branch linked in the issue thread, but I still haven't been able to demonstrate the fix yet. Omarchy ISO doesn't have a pre-load (afaict?), but just the one-liner added in Arch at boot after hitting "e" didnt work for me. I tried modifying the actual Omarchy ISO but hit some friction with not getting the EFI setup right. |
|
@adamavenir I'm going to try to gather up all my 2012 mbp fixes (this one amongst them) and try to make a PR for an initial macbook.sh PR. I'll tag you when I do. Likely within the next week! |
|
@bcorcoran Awesome. Thank you for doing that! I created draft PR #1143 in the event I can get this tested successfully when I have time next. |
|
I can also help test this fix on my 2012 MacBook Pro, if you want help :) I also raised this topic as an issue on the Omarchy iso GitHub |
|
@brink-lab What does |
|
@bcorcoran |
Yes, but it was installed via NetworkManager as a dependency. I do not have I have not configured |
This resolved the issue that I had on my MacBook Air (11-inch, Early 2015), where it wouldn't automatically reconnect to the WiFi after a reboot. Thanks. |
Out of curiosity, have you run sudo mkinitcpio -P after adding the modprobe options? From what I have read about limine, this update the device persistence hardware options. I'm also new to this too, so someone else here may be able to confirm or deny truth to this suggestion. |
Also read a little about this and turning off SIP on the device. This may help during your debugging as the hardware may not work correctly without it, at least that is what I've read in past posts online. For what it is worth, my device wifi is working without the broadcom-wl package. I have yet to see my Touchbar or audio driver work fully. I've gone through configuring options for hid_appletb_bl (touchbar), hid_appletb_kbd (touchbar), hid_apple (keyboard/touchpad), brcmfmac (wifi), and snd_hda_intel (audio). I can share the /etc/modprobe.d/*.conf files I have setup if anyone wants? Also for clarity, my MBP device designation is a 2016 model cat /sys/class/dmi/id/product_nameMacBookPro13,2 lspci -nnv | grep "43602"02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 02) |
Just to verify here, is a "sudo mkinitcpio -P" also required to persist these settings into pram/etc? |
|
@iamobservable |
|
I've been installing a dual boot recently with my 13,2 device that required using the archinstall instead of the omarchy.iso. I've been experiencing all the issues mentioned in this thread with my broadcom device. After having stumbled around with modprobe and setting the feature_disable=0x82000, I saw @adamavenir reference to the wireless-regdb issue that @eclecticc worked on. Fast forward and I installed iw and wireless-regdb to my device so iw is available in /usr/sbin/iw and the /etc/conf.d/wireless-regdom settings are created. I can confirm that setting "iw reg set US" fixes my broadcom device with no other changes. Has anyone else experienced this in your testing? I was pretty surprised how direct of a fix it was after seeing the reference. 👏 Thanks to everyone involved in finding a fix! |
|
Hi, I am helping someone who's using omarchy with BCM43602 rn. We did the kernel param and regen initramfs (this is confirmed to be set with We're going to try the wireless-regdb above (I assume register for the country residing in instead of US like said above as to not break carrier frequency law(?)). And if that doesn't work we'll try to get will report back if any of these works for our case just to give more information for others! |
|
Moved to discussion: https://github.com/basecamp/omarchy/discussions/4679 — this is a hardware/driver-specific issue not directly actionable by Omarchy. The original comments remain here for reference. |
|
@dhh that discussion is gone but I was replying to you there re: this:
I had the same exact experience when I opened #1022! But I actually just gave up on my old MBP when I realized it didn't have a physical escape key. |
|
Also had this problem on my MacBookPro 14,3. It only showed 2.4 GHz wifi, almost no signal, couldnt connect with password wrong error etc Found a fix for this on my machine by adding a broadcom NVRAM file I found and now everything works. Opened a PR for this here #7487 But its potentially problematic to vendor the NVRAM file because its Broadcom proprietary, thats why linux-firmware dont ship it. If it cant be merged because of that then you can simply add the file yourselves manually |
|
Adding a reproducible result from a MacBookPro13,3 with BCM43602 [14e4:43ba]. Environment:
The saved hotspot password is correct, but both the Omarchy network UI and a direct NetworkManager test fail. The direct test used the hotspot's currently scanned BSSID explicitly: The useful finding is that this does not reach a WPA four-way handshake and there is no Even more notably, the logs show the association attempt going to the BSSID of the currently available Costa access point, not the iPhone hotspot BSSID supplied to This machine already has the commonly suggested workaround loaded through modprobe configuration: So that setting is not sufficient here. The driver reports firmware This evidence suggests the password is never actually rejected: the BCM43602/brcmfmac path is selecting or reporting the wrong BSSID before the key exchange. The stock Arch and LTS kernels are already installed, so comparing one of those against |
|
I have evidence of a country-table failure on a MacBookPro11,4 with BCM43602/1, plus a second iMac17,1 session. Both use firmware 7.35.177.61 (FWID 01-ea662a8c). These results help distinguish channel-availability failures from password errors; they do not diagnose every case in this discussion. On the MacBook (board 0x0133), firmware RU/0 reported only 13 channel specifications, none on 5 GHz. A connection attempt to a visible 5 GHz AP switched to that table and failed before authentication. Channel 36, WPA2 AES and router compatibility changes did not resolve it. A board-specific driver change selecting RU/2 allowed connections on both 2.4 and 5 GHz; five gateway pings had no loss. The AP then selected US/0, so the 780 Mbit/s link rate does not establish 80 MHz support under RU/2. The iMac session (board 0x014a) independently recorded the same RU/0 limitation and a channel-36 connection with a board-specific RU/2 variant. Its operator later corrected the physical location to Kazakhstan. Native KZ/0 and KZ/1 excluded channel 100, despite the installed KZ rules reportedly covering it. Its final channel-100 connection needed a different local firmware mapping plus a pinned/targeted NetworkManager profile. It was not compared against the stock driver using that same final profile, so it is not evidence of a kernel-only fix. I am preparing a Linux wireless RFC for the narrow MacBook workaround and including the iMac evidence for review. The KZ patch remains discussion material: a fixed power assignment can override a lower user preference, and RF/DFS behavior and later AP-country transitions need review. No blanket country-code change or copied calibration file is recommended. The MacBook has now passed a reboot test: the DKMS module loaded and the 5 GHz connection activated automatically; a live check confirmed 5180 MHz. The iMac final configuration still lacks reboot validation, and neither machine has suspend/resume or long-run validation. The second session is reported evidence, not newly repeated testing on this MacBook. OpenAI Codex assisted with investigation, code, tests and these drafts; a human will review and submit them. |


Uh oh!
There was an error while loading. Please reload this page.
I attempted to install arch on an old MBP and ran into some interesting challenges.
This is relevant here now because I just attempted to install the iso and had similarly strange issues.
Arch
What I did:
station wlan0 scan-> found my networksstation wlan0 connect <SSID>-> entered correct password -> got “Operation failed”Found:
NetworkConfigurationEnabled=truein /etc/iwd/main.conf, error went away, but still got “Operation failed” and status shows “disconnected”Omarchy
Had similar results in Omarchy's WiFi UI:
But then...
I was about to reattempt it in order to document the error message for this issue, but after the couple minutes I spent writing the above, I came back to the installer (still open at network select screen) and attempted to connect and it worked (without asking my password) as it went to the next step and I'm now downloading packages!
All reactions