Just wanted to check in, these instructions worked today on a Late 2013 MacBook Pro 15" with a Broadcom BCM4360, Pop!_OS 22.04 LTS fully patched. Wifi didn't work on the bare install, but I shared my phone's internet via USB to patch, install inxi, and work through your advice. Thanks!Dam it, being Loosely based on Ubuntu I hoped it would work, you were connected by wire to the router/internet I hope!
If so, let's make one last try this afternoon..
make sure you are connected to the internet, then try
sudo apt update and enter then when that's done
sudo apt install bcmwl-kernel-source and enter then when that has done
sudo modprobe wl and enter now when that's finished
edit, note the get has gone from the instructions as I dont think its needed with Pop
Hello @linnnnil,Since this thread has helped me get a WIFI connectivity on my (recently purchased) old 2015 MacBook Air, I just wanted to pay tribute with my first post and add some (CRUCIAL in my case) information:
I could only install the drivers for the built-in Broadcom WLAN device via USB tether from my (unloved and rarely used) Android mobile phone. At first I tried to share WLAN from my iPhone, not knowing that iPhones would NOT allow network access to a Linux machine via sharing a personal hotspot.
I still don't understand why these drivers are NOT part of the Pop!_OS ISO installation file.... This is really an unfathomable mystery to me.
So, maybe this note will help some other newbies. Would have saved me a few hours for sure....
Well, finally, my very frist Linux test can begin! I've been a Mac fan for over 30 years, but I'm increasingly annoyed by Apple's data sucking policy, gender GUIs, mobile optimised (= vertical OMG!) preference panes in OS 13 etc.
Hi Mike,Sorry for contributing to the necro-posting, guys...
Answer me this.....if you can. This business of "installing" the Broadcom drivers, it's a bit different to how we handle this stuff under Puppy. Does the "mainstream" method simultaneously install the firmware along with the drivers?
I only ask, because we frequently find that certain kernel/firmware combos usually contain either the one OR the other.....but not both. One of our veteran members (by the name of gyrog) has for years been collecting/compiling/building a huge firmware database on behalf of the community, from which he periodically releases 'snapshots' in the form of 'load-on-the-fly' SFS packages.
Puppies tend to use the following format for their 'base' packages:-
- A 'puppy-xxxxx.xx.sfs' file - the 'main' Puppy file
- A 'zdrv-xxxxx.xx.sfs' file - contains the kernel modules. This, along with vmlinuz, is what enables quick kernel swaps in Puppyland; one is created for every kernel by the kernel-master-kit script in Woof-CE at Github
- An 'frdv-xxxxx.xx.sfs' file - this is optional, but will be one of gyrog's periodic firmware update releases, often containing frequently hard-to-find, or 'awkward' firmware
- An 'adrv-xxxxx.xx.sfs' file - often present, but again optional. Used by individual developers to add certain software packages of their choice. Can be easily rebuilt to alter contents
I only wondered how the mainstream distros handle this, 'cos I have very little to do with them....
GNU/Linux Ubuntu 22.04 Broadcom Driver Setup Guide Hi! The Tutorial shows you Step-by-Step How to Install Broadcom WiFi/Bluetooth Drivers in GNU/Linux Ubuntu 22.04 Jammy LTS GNU/Linux. Especially relevant: here below you find the Broadcom Wireless Driver Ubuntu Jammy Setup Guides for most...tutorialforlinux.com
Hi MikeAnswer me this.....if you can. This business of "installing" the Broadcom drivers, it's a bit different to how we handle this stuff under Puppy. Does the "mainstream" method simultaneously install the firmware along with the drivers?