On Wed, 7 Sep 2022, Finn Thain wrote: > On Wed, 7 Sep 2022, Stephen Walsh wrote: > > > On Wed, 7 Sep 2022 11:59:17 +1000 (AEST) > > Finn Thain <fth...@linux-m68k.org> wrote: > > > > > > Here are three debugs..... mixing the kernel/intrid's... > > > > > > What happens if you boot the 5.19 kernel/initrd pair with > > > "root=/dev/sda2" omitted from the kernel parameters? > > > > > > It looks like the oops from the 5.18 build disappeared in the 5.19 > > > build. > > > > > > That makes me think that the 5.18 build would no longer oops when > > > used with the 5.19 initrd (?) > > > > All boot attempts have ran with the following amiboot line (Changing > > the kernel/initrd of course) > > > > amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k > > root=/dev/sda2 fb=false debug=mem > > > > Right. What I was saying was that you'd probably get better results if you > omitted root=/dev/sda2. >
Please disregard that. I realize now that the kernel is not aware of any initrd at all, which is why it fails with "No filesystem could mount root". It still looks like a bootloader issue to me.
