Hi Jason,
Thanks, I tried all three both previously and again on receipt of your response (Incase i made a simple error somewhere) and the outcome is the same, it goes to kernel panic. I tried variations of the /dev/mmcblk1p1 foot INITRD = xxx which was working on the early kernels and this made no difference either. The initrd.img for these is there and created on install and I have tried regeneating it, also I explicitdly named the vmlinux-x.x.x and initrd.img-x.x.x for the failing kernels and it does not boot like before. Is there any major config change between 6.12 and 6.18 that could be behind this? Regards Ryan On Tue, 2026-05-26 at 05:06 -0700, Jason Self wrote: > Please check these three things: > > 1. Is the initramfs missing? Check /boot to see if initrd.img- > [version] > actually exists for the failing kernels. If not, boot into 6.12 and > regenerate it: > sudo update-initramfs -c -k [failing_kernel_version] > > 2. Is the bootloader loading it? Check your U-Boot config. Make sure > the boot entry for the failing kernels has an INITRD line pointing to > the correct initramfs image. > > 3. Did the drive name change? Newer kernels sometimes rename the SD > card reader. In your boot config, try changing the root= parameter to > use the UUID instead (e.g., root=UUID=your-drive-uuid). _______________________________________________ linux-libre mailing list [email protected] http://www.fsfla.org/cgi-bin/mailman/listinfo/linux-libre
