[Bug 2060032] Re: Mitigate lack of space from new initramfs

[Dave Jones]

Hmm, I see that was released on 21st of March; I'm *fairly* sure the
excess size of the initramfs was still occurring after that but I'll
double check this evening.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/2060032

Title:
  Mitigate lack of space from new initramfs

Status in flash-kernel package in Ubuntu:
  New
Status in ubuntu-raspi-settings package in Ubuntu:
  Fix Released

Bug description:
  Discovered on an image upgraded from jammy to noble:

  jammy's boot partition is a mere 256MB. This was fine when the initrd
  was relatively minimal, as was the case with the split linux-modules-
  extra, which resulted in initrd's with a size around ~30MB. However,
  with noble, linux-modules-extra has been removed (with good
  justification; the split caused a raft of complaints about missing
  modules). The new initrd is >100MB and as a result, flash-kernel can
  fail mid-way through copying things to the boot partition, leading to
  an unbootable system (this is also something flash-kernel should guard
  against, so I'll target this bug to f-k too).

  This won't affect new noble installs where the boot partition is an
  expanded 512MB, but there's no easy way to resize the boot partition
  on upgraded systems.

  Investigating the content of the new initrd, at least 40MB of it is
  taken up with binary blobs for nvidia graphics cards which probably
  aren't that useful on a Pi (unless your name is Jeff Geerling).
  There's no mechanism for exclusion of modules, so we should add an
  initramfs-tools hook to ubuntu-raspi-settings to manually exclude
  these modules (possibly with a configuration switch just in case
  someone wants to include them again).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2060032/+subscriptions