I saw there was an update on trixie initramfs-tools (rpt1 suffix) yesterday on 64-bit, haven't looked what it is just blind install. I guess it is some yes/no multithread xz compress but you need to check yourself.Ah, ok, didn't notice the -v8 (yes, this is a 32-bit system). OK I purged linux-image-rpi-v8 (along with linux-image-6.12.20+rpt-rpi-v8 and linux-image-6.12.34+rpt-rpi-v8), but I still have the configuration error, only now it's with a -v7 image.I tried adding some debug flags to dpkg but it doesn't increase the debug from the actual post-installation script, so I'm not really sure what it's getting hung up on. In any case, it's still working pretty normally otherwise.Code:
squirtle:~ # sudo dpkg --configure -aSetting up initramfs-tools (0.148.3+rpt1) ...update-initramfs: deferring update (trigger activated)Processing triggers for initramfs-tools (0.148.3+rpt1) ...update-initramfs: Generating /boot/initrd.img-6.12.34+rpt-rpi-v7E: /usr/share/initramfs-tools/hooks/kmod failed with return 1.update-initramfs: failed for /boot/initrd.img-6.12.34+rpt-rpi-v7 with 1.dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1Errors were encountered while processing: initramfs-tools
I haven't upgraded any RPiOS32 yet, will do that soon with my 32-bit test KVM, then more checks are still needed for my Pi1 and Pi0(W). I also will upgrade other vanilla Debian armhf soon, that will be other hook scripts in etc/initramfs /etc/kernel, as I guess maybe something goes wrong there.
You can manually create initramfs, but note that you must be able to fix not-booting-RPi issues in case this goes wrong (or wipe all, fresh image)
Statistics: Posted by redvli — Wed Jul 09, 2025 8:56 am