Is it failing to execute /init (in the initramfs), or /sbin/init (in the root partition)? Are they missing, or is there an error code?kernel panic because it claims it can't find any form of init
It is not particularly magical. Unless you have your own logic in config.txt, the firmware just picks the kernel with the suffix that best supports the CPU architecture of the model of Pi that is booting. And the corresponding initramfs, if auto_initramfs=1.At this point it looks really like somehow the timestamps on the files in /boot/firmware being from the future was making the bootstrap's somewhat "magical" kernel/initrd-hunting process reject the images it should otherwise be happy with.
It is not rejecting anything; it is loading the kernel and you do not appear to claim it is loading the wrong one.
I do not believe the firmware knows the current date, by the way. If you boot a non-Pi5, without Ethernet connected, there is no way it could.
No matter how reproducible you think something is, unless there is a coherent explanation of how it causes an issue, it is just a coincidence.
Statistics: Posted by jojopi — Fri Mar 07, 2025 5:36 am