[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Booting Kernel on Amiga 3000



Hi Stephen,

On Tue, Sep 6, 2022 at 3:47 AM Stephen Walsh <vk3heg@vk3heg.net> wrote:
> Debug booting 5.15.0-2
>
> [    0.000000] Linux version 5.15.0-2-m68k (debian-kernel@lists.debian.org) (gcc-11 (Debian 11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 Debian 5.15.5-2 (2021-12-18)
> [    0.000000] printk: console [debug0] enabled
> [    0.000000] Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF AUDIO FLOPPY A3000_SCSI KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA DENISE_HR AGNUS_HR_PAL MAGIC_REKICK ZORRO3
> [    0.000000] Ignoring memory chunk at 0x7800000:0x800000 before the first chunk
> [    0.000000] Fix your bootloader or use a memfile to make use of this area!
> [    0.000000] Zone ranges:
> [    0.000000]   DMA      [mem 0x0000000008000000-0x000000ffffffffff]
> [    0.000000]   Normal   empty
> [    0.000000] Movable zone start for each node
> [    0.000000] Early memory node ranges
> [    0.000000]   node   0: [mem 0x0000000008000000-0x000000000fffffff]
> [    0.000000] Initmem setup node 0 [mem 0x0000000008000000-0x000000000fffffff]
> [    0.000000] initrd: 0783283d - 08000000

So the initrd is located in motherboard RAM.

> Booting with kenel 5.18.0-4, but initrid 5.15.0-2
>
>
> [    0.000000] Linux version 5.18.0-4-m68k (debian-kernel@lists.debian.org) (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 Debian 5.18.16-1 (2022-08-10)
> [    0.000000] printk: debug: ignoring loglevel setting.
> [    0.000000] printk: console [debug0] enabled
> [    0.000000] Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF AUDIO FLOPPY A3000_SCSI KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA DENISE_HR AGNUS_HR_PAL MAGIC_REKICK ZORRO3

Why is there no initrd line here?

Note that your initial bad boot report (kernel 5.18.0-4 with corresponding
initrd) had:

    initrd: 0f7f81c2 - 10000000

I.e. the initrd was located in the WarpEngine RAM.

What happens with the old kernel and the new initrd?

> [    0.000000] Ignoring memory chunk at 0x7800000:0x800000 before the first chunk
> [    0.000000] Fix your bootloader or use a memfile to make use of this area!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@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


Reply to: