** Description changed:
+ [ Impact ]
+
+ With no wifi drivers in the initrd, the wait-online unit (which runs in
+ the initrd under dracut) will no function, breaking cloud-init usage
+ with wifi setups on the Pi (bearing in mind on some Pis this is the only
+ network interface).
+
+ [ Test plan ]
+
+ * Flash Ubuntu resolute for Pi image to an SD card
+ * Configure network-config on boot partition for wifi service (but no
ethernet)
+ * Boot on a Pi with wifi
+ * Check status of systemd-networkd-wait-online service (if it's disabled, add
rd.neednet to cmdline.txt on the boot partition and try again)
+ * Observe failure of the service
+ * Enable proposed
+ * sudo apt install -t resolute-proposed ubuntu-raspi-settings
+ * Ensure initrd is rebuilt and written to boot partition
+ * sudo reboot
+ * Check status of systemd-networkd-wait-online service
+ * Observe success
+
+ [ Where things could go wrong ]
+
+ This change doesn't remove anything from the initrd, so there's little
+ risk to the production of the initrd itself. The danger comes from the
+ increase in the size of the resulting initrd (by about 10MB).
+
+ This may well cause issues on systems with smaller boot partitions
+ (installations that have been upgraded since jammy, for instance), where
+ a pre-existing issue in dracut causes the initrd to be written partially
+ (it doesn't notice the out-of-space error when copying, or ignores it).
+ On the plus side, this is unlikely to break people's boot (due to the
+ A/B system on resolute), but under those circumstances will cause a
+ fallback to older (known good) boot assets.
+
+ There are workarounds in such cases: users with no need of wifi in the
+ initrd can simply disable this change (delete
+ /etc/dracut.conf.d/12-raspi-brcmfmac.conf or otherwise comment out its
+ contents). Users with sufficient RAM can try higher compression ratios
+ (delete/disable /etc/dracut.conf.d/20-raspi-compress.conf -- although
+ this doesn't work on models with smaller RAM). Users confident in their
+ fs skills can re-partition and expand their boot partition (sadly
+ there's no automated, safe way of doing this). In short, this can be
+ worked around, but it'll be case by case.
+
+ [ Original description ]
+
By default, the linux-firmware-raspi wifi firmware blobs are not
appearing in the dracut initrd. While this does not prevent the wifi
interface from *eventually* initializing (once the rootfs is mounted and
the blobs are loaded) it does prevent early usage of the wifi, which
affects cloud-init.
It is debatable if this configuration should be placed in linux-
firmware-raspi or ubuntu-raspi-settings but I'm opting for the latter on
the basis that this is not part of the upstream firmware package.
** Also affects: ubuntu-raspi-settings (Ubuntu Resolute)
Importance: Undecided
Status: New
** Changed in: ubuntu-raspi-settings (Ubuntu Resolute)
Status: New => In Progress
** Changed in: ubuntu-raspi-settings (Ubuntu Resolute)
Importance: Undecided => High
** Changed in: ubuntu-raspi-settings (Ubuntu Resolute)
Milestone: None => ubuntu-26.04.1
** Changed in: ubuntu-raspi-settings (Ubuntu Resolute)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-raspi-settings (Ubuntu)
Milestone: ubuntu-26.04.1 => ubuntu-26.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2150053
Title:
[SRU] Ensure brcmfmac firmware present in dracut initrd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2150053/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
