** Description changed: + [ Impact ] + + Without the wlan0 adapter, some models of Pi (the 3A+ and Zero 2W + specifically), have no network access at all. On others, the only + network access is Ethernet, which may be insufficient for many users. + + While there is a workaround, it requires interaction + + [ Test plan ] + + For each affected $series, on each $model (Pi 3B, 3A+, 3B+, at least one + 4B, and one 5 model): + + * Flash image for $series server to an SD card + * Configure network-config on the boot partition with a valid netplan configuration including a valid wlan0 portion for your AP + * Boot SD card on $model + * On stonking, note that wlan0 is entirely missing even after boot + * On resolute, that wlan0 is not present for cloud-init, but present after boot completion (see /var/log/cloud-init-output.log and note that wlan0 is not connected when cloud-init runs) + * Ensure OS is fully updated (with Ethernet where available): sudo apt update; sudo apt full-upgrade (this is critical for the next portion) + * Enable proposed + * sudo apt install -t $series-proposed ubuntu-raspi-settings + * Ensure that during upgrade of ubuntu-raspi-settings, initramfs is implicitly rebuilt (this is why ubuntu-raspi-settings must be the only package in the upgrade set) + * sudo reboot + * Check that wlan0 is present and operational after boot (if Ethernet is enabled, disconnect cable and perform a test ping) + + [ Where things could go wrong ] + + The change adds yet another module to the initramfs, so there is always + the danger that we'll expand the size of the initramfs to the point that + two copies cannot be fitted on the boot partition of users who have + upgraded from much earlier series. + + On the plus side, the A/B boot mechanism should guard against breaking + boot in this eventuality, but in this case such users will either need + to expand their boot partition (risky and difficult), or apply another + workaround, like extra compression on the initrd (risky if the Pi model + has limited RAM), to enact this fix. + + Still, the bug's impact being that wifi is entirely unavailable (on + stonking), and non-operational for cloud-init (on resolute), is + sufficiently severe that the risk is considered acceptable. The test + plan ensures that both reboot and subsequent operation of wifi are + successful. + + Another possibility is that the initramfs is not triggered to rebuild + automatically during the upgrade (see LP: #2168417). The test plan + guards against this by ensuring that *only* ubuntu-raspi-settings is in + the upgrade set, and checking that initramfs rebuild is implicitly + triggered during apt. + + [ Original description ] + The wifi adapter does not appear under the stonking beta images, running linux-raspi 7.3.0-1002-raspi. I've checked the linux-firmware-raspi package is present, with the relevant firmware blobs, but wlan0 doesn't appear. The following brcmfmac messages are present in dmesg: $ sudo dmesg | grep brcmfmac [ 1.981931] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 1.983221] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 1.983979] usbcore: registered new interface driver brcmfmac [ 2.131189] brcmfmac: brcmf_fwvid_request_module: mod=cyw: failed 256 [ 2.144743] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed The messages above are from an RPi 5, but I've verified the adapter fails to appear on the 3B, 3B+, 4 (several memory models), and the 5 so it appears this isn't specific to the 43455 used on the later models, but also affects the 43430 used on the 3B (and Zero 2W, though I haven't tested that yet). + + [ Workaround ] + + Reload the brcmfmac driver after boot: + + sudo rmmod brcmfmac + sudo modprobe brcmfmac
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2169127 Title: [SRU][FFe] brcmfmac-cyw module missing from initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2169127/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
