[ not including debian-release for this ] On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote: > On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote: > > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote: > > > When upgrading the firmware: > > > > > > [...] > > > Setting up firmware-intel-graphics (20240610-1) ... > > > Setting up firmware-iwlwifi (20240610-1) ... > > > Setting up firmware-misc-nonfree (20240610-1) ... > > > Setting up firmware-nvidia-graphics (20240610-1) ... > > > Setting up firmware-intel-misc (20240610-1) ... > > > Setting up firmware-mediatek (20240610-1) ... > > > Processing triggers for initramfs-tools (0.142) ... > > > update-initramfs: Generating /boot/initrd.img-6.9.9-amd64 > > > zstd: error 70 : Write error : cannot write block : No space left on > > > device > > > > If you do not need all that firmware, try removing the ones you > > don't need. Especially if you don't need nvidia-graphics firmware, > > remove that because that is BIG (and the reason it got split out > > from misc-nonfree). It's a RECOMMENDS, so you can remove it (if you > > don't need it). > > The graphics card is a Nvidia one, so I probably need this firmware.
Agreed, you should have that firmware package installed. I learned something new today: Are you using plymouth? Because plymouth does include GPU kernel modules and the firmware for it. > In any case, the upgrade should work for any user, including when > all these packages are needed. The real problem seems to be the size of /boot/ ... > > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote: > > > This is wrong. There's plenty of space: > > > > > > Filesystem Size Used Avail Use% Mounted on > > > ... > > > > > > 456M 243M 189M 57% /boot > > > > While generating the initramfs it needs a LOT more space then what's > > needed > > when the generation completes successfully. It's all the uncompressed > > files + the size of the compressed archived/initramfs. > > When done, it can remove all the uncompressed files. > > But it would be silly to use the /boot partition (which is typically > small) for storing the temporary uncompressed files. Smaller then the root partition, but it's problematic when /boot partition is actually 'small' ... > Note that https://www.debian.org/releases/stable/amd64/apcs01.en.html > does not recommend anything for the /boot partition. > > https://www.debian.org/releases/stable/amd64/apcs05.en.html says > "25–50MB should suffice" (though this is probably not sufficient > for most uses). > > https://linuxhint.com/boot-partition-size-debian/ says > 256 MB / 512 MB for Debian 11. > > Mine has 512 MB (more that 10 times the recommended 25–50MB). You may have guessed by my previous reply (which did include debian-release) that those recommendations are ABSURD. A 512 MB /boot/ partition *can* work nowadays, but it gets problematic when you use plymouth which then includes firmware for GPU modules ... and those have exploded in size ... mainly nvidia though. See f.e. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f4a3c72e5c413a601d1e21f9606f1c94a610d05d But IIUC, the default size for /boot/ partition by d-i is 512 MB and I think that's problematic, especially since enlarging the /boot partition is not easy to do for 'average' users. The kernels themselves have got bigger over time which was previously already reported as (being/becoming) problematic, especially if you have several kernels installed. But it seems the initrd file sizes increase now really causes problems. Especially if GPU firmware files get included in them. I don't use plymouth and (therefor) I don't have GPU modules nor GPU firmware files in them ... and my initrd is 37M in size (for 6.9.9). And when I installed my system, I made the /boot/ partition 2G in size...
signature.asc
Description: This is a digitally signed message part.
