On 19/07/2024 at 20:54, Diederik de Haas wrote:
There may be a bug here, in that the /boot partition was too small.
That has been fixed in the installer, but unfortunately we don't have
a general way to grow the partition on installed systems.
And there have been other reports that the kernel is getting too big.
It is mostly the initramfs which is getting too big.
Plymouth is installed by default and that includes the GPU modules and
the firmware for it.
Plymouth is installed by default (recommended) by desktop environment meta-packages. It adds GPU-related kernel modules and firmware files to
the initramfs.
And the firmware files have been getting bigger
too, especially for nvidia where they just added firmware files which
are respectively 23MB and 38MB in size ... (sigh)
The initramfs built by initramfs-tools < 0.143 can be as big as 240 MB
when firmware-nvidia-graphics is installed.
For ``/boot`` size it should minimally follow d-i's default,
D-i partman does not really define a default size for /boot. Guided partitioning with LVM currently sets a fixed size of 512 MB regardless
of the disk size. Guided partitioning without LVM does not create a
/boot partition. Manual partitioning does not have default size.
but I
actually think both should be updated to 1G in size, which should
(generally) not be a problem with current TBs NVMe drives.
Or changed to a variable size depending on the disk size.
Maybe it should also be noted that if systemd-boot is installed, the EFI
system partition (ESP) or the extended boot loader partition (XBOOTLDR)
must be big enough to contain the kernel images and initramfs.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)