Hi Finn,
On Thu, Sep 8, 2022 at 2:49 AM Finn Thain <fth...@linux-m68k.org> wrote:
> On Thu, 8 Sep 2022, Stephen Walsh wrote:
> > >> amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
> > >> root=/dev/sda2 fb=false debug=mem
> > >
> > > Are you sure that is what you really used?
> > >
> >
> > Yes, that is what I've been using and works with 5.15
>
> I think that what Geert was getting at was the discrepancy between the
> two test runs seen here:
> https://lists.debian.org/debian-68k/2022/09/msg00015.html
>
> The first has this:
>
> [ 0.000000] Kernel command line: root=/dev/sda2 fb=false debug=mem
> BOOT_IMAGE=vmlinux-5.15.0-2-m68k
> [ 0.000000] Unknown kernel command line parameters "fb=false
> BOOT_IMAGE=vmlinux-5.15.0-2-m68k", will be passed to user space.
>
> Whereas the second has this:
>
> [ 0.000000] Kernel command line: ignore_loglevel -r
> initrd.img-5.15.0-2-m68k root=/dev/sda2 fb=false debug=mem
> BOOT_IMAGE=vmlinux-5.18.0-4-m68k
> [ 0.000000] Unknown kernel command line parameters "-r fb=false
> BOOT_IMAGE=vmlinux-5.18.0-4-m68k", will be passed to user space.
>
> The presence of "-r filename" in the second log indicates that amiboot did
> not act upon those arguments but passed them to the kernel instead.
>
> When you run the tests I proposed, please use the first method again i.e.
> omit "ignore_loglevel".
oh right, the "ignore_loglevel" is in the wrong location: it should be
located after the initrd.
In the screenshot you showed, "ignore_loglevel" was the last parameter,
which is fine.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
