May 24, 2023 at 9:37 PM, "Cyril Brulebois" <k...@debian.org> wrote:
> > Fan Naibed <oregano+deb...@disroot.org> (2023-05-24): > > > > > May 23, 2023 at 3:17 AM, "Cyril Brulebois" <k...@debian.org> wrote: > > How would this work? firmware-b43-installer is just a downloader, > > so for it to do anything, you need to have a working connection in > > the first place. It's basically an empty shell, with its postinst > > doing the downloading. > > > > Installing onto slightly older Macbooks, using Wi-Fi, just worked(TM). > > So, their WiFi fw was included. > > > > Do you know which firmware files/packages were involved on those? The older macbook has 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43224 802.11a/b/g/n [14e4:4353] (rev 01) and uses firmware-brcm80211. The macbook pro has 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01) > > > > > The b43 installer/downloader would need to be changed to a firmware > > file that can be included with the installer. :) > > > > Presumably those are working this way because the license doesn't > allow for redistribution. Feel free to get that part resolved! Since I don't understand how automating the download and install is significantly different than including the firmware in the debian installer, from a license/legal standpoint, that is beyond me! > Also, see https://wiki.debian.org/bcm43xx Thanks