Re: Booting Kernel on Amiga 3000

Re: Booting Kernel on Amiga 3000

[John Paul Adrian Glaubitz]

Hi Stephen!

Might be a wise idea to cross-post this to the Linux/m68k kernel mailing list.

Also, kernel 5.19.6 is currently being built and should be available soonish.

Adrian

On 9/3/22 02:24, Stephen Walsh wrote:
> I have "Debian GNU/Linux bookworm/sid" installed on both Qemu-user and
> real hardware.
> 
> Amiga 3000
> Warpengine 68040@40Mhz
> 128Mb ram on warpengine
> 8Mb Fast ram on MB
> 2Mb Chip ram
> X-surf Network card (Original)
> Kickstart 3.2
> 
> Qemu is working with no issues.
> 
> Real hardware issue:
> 
> Booting kernel/inintrid 5.15.0-2 works and the machine boots all the
> way.
> 
> Trying to boot with kernel/initrid 5.18.0-1 through to 5.18.0-4 results
> in a grey screen and the machine doing nothing after amiboot loads in
> the kernel. I have  left it for 20 minutes with no change. Booting
> 5.15.0-2 starts showing the boot process after a couple of minutes.
> 
> 
> amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
> root=/dev/sda2 fb=false
> 
> When trying the newer kernel's, all I'm doing is replacing the
> kernel/initrid with the newer versions.
> 
> 
> 
> 

-- 
  .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Re: Booting Kernel on Amiga 3000

[Geert Uytterhoeven]

Hi Ingo,

On Tue, Sep 6, 2022 at 7:46 AM Ingo Jürgensmann <ij@2022.bluespice.org> wrote:
> Am 06.09.2022 um 03:46 schrieb Stephen Walsh <vk3heg@vk3heg.net>:
> >> So, here is the error and a possible solution: using a memfile might
> >> help.
> > I've not done a memfile before so will need a pointer or two.
>
> Quick pointer was to look it up in my blog about the BigRamPlus:
>
> https://blog.windfluechter.net/2013/12/18/1677-debian-donation-m68k-arrived/
>
> There you can find a memfile. Basically it is quite simple. First line should be ChipMem and in that example there are my 64 MB FastMem on the Warpengine. And next parameter to the starting address is the size in bytes.
>
> > The memory layout is like this. Seams to be all the time, booting into
> > 3.1/ATK/SYSINFO
> >
> > $08000000 - $0FFFFFFF     128Mb (WarpEngine)
> > $07800000 - $07FFFFFF     8Mb (Fast Ram)
> > $00004000 - $001FFFFF     2Mb (Chip Ram)
> >
> >
> > Z3 Warpengine $40000000 (16Mb)
> > Z2 X-Surf     $00E90000 (64Kb)
> > Z2 Buddha IDE $00EA0000 (64Kb)
>
> You’ll only need to include those address space that is actually RAM, not address space for firmware or IO stuff.

As there are only two regions of Fast RAM, and the second one should
not be used as it is slow motherboard RAM, I think a memfile won't
make a difference.

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

Re: Booting Kernel on Amiga 3000

[Geert Uytterhoeven]

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