Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2024-07-31 Thread Diederik de Haas
On Wednesday, 31 July 2024 16:37:48 CEST Pascal Hambourg wrote: > On 31/07/2024 at 00:38, Thomas Hahn wrote: > > On Fri, 26 Jul 2024 14:00:51 +0200 Pascal Hambourg > > > > wrote: > > > firmware-nvidia-graphics was installed on systems which already had > > > firmware-misc-nonfree because firmware

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2024-07-31 Thread Pascal Hambourg
On 31/07/2024 at 00:38, Thomas Hahn wrote: On Fri, 26 Jul 2024 14:00:51 +0200 Pascal Hambourg wrote: > > firmware-nvidia-graphics was installed on systems which already had > firmware-misc-nonfree because firmware-misc-nonfree recommends > firmware-misc-nonfree so that systems which rely on

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2024-07-30 Thread Thomas Hahn
On Fri, 26 Jul 2024 14:00:51 +0200 Pascal Hambourg wrote: > On 26/07/2024 at 13:27, Thomas Hahn wrote: > > There was some changes with the firmware packages. > > Yes, Nvidia firmware grew bigger (but not as much as the observed > initramfs size increase) so they were moved from firmware-misc-non

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2024-07-26 Thread Pascal Hambourg
On 26/07/2024 at 13:27, Thomas Hahn wrote: There was some changes with the firmware packages. Yes, Nvidia firmware grew bigger (but not as much as the observed initramfs size increase) so they were moved from firmware-misc-nonfree to a new package firmware-nvidia-graphics, which is recommende

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2024-07-26 Thread Thomas Hahn
There was some changes with the firmware packages. firmware-nvidia-graphics was installed automatically on boxes which don't have a NVIDIA device in their system. This blows up the initrd images to almost 4 times the size. If I apt remove firmware-nvidia-graphics the image sizes remain at the

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2024-07-19 Thread thah...@t-online.de
Which setting has changed in initramfs-tools, so initrd images are now almost 4 times bigger than before? tom@ideapada:/var/log/apt$ cd /boot tom@ideapada:/boot$ ls -l initrd* -rw-r--r-- 1 root root 60084701 Jun 4 17:37 initrd.img-6.8.12-amd64 -rw-r--r-- 1 root root 60296117 Jul 11 22:21 in

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2024-07-17 Thread Simon John
John Mullee's patch still doesn't fix the issue, as although the cpio is created in /tmp, you still have /boot/initrd.img-6.9.9-amd64.dpkg-bak So my pc upgraded from bullseye to Sid with a 500mb /boot (default luks install - no uefi) now can only fit a single kernel 6.9.9, even with MODULES=de

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2021-10-18 Thread Nathan Lövsund
Hi, I had the very same issue last night: running a bookworm system installed more than a year ago with buster's installer using the default encrypted scheme. The /boot partition cannot hold 2 initrd images and finish the installation of the new one because of a lack of disk space. I had to te

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

2020-10-18 Thread Jean-Marc
Bug already reported 2 times: initramfs-tools: update-initramfs should not store temporary files on /boot https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929424 pigz: abort: write error on (No space left on device) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960181 The 2 bugs are all mar