Michael Schmitz <schmitzmic <at> googlemail.com> writes:
Can you try to have the kernel placed in ST-RAM?
No, the kernel is too big. I've only got 4MB ST-RAM. And getting more on
The guys at the Atari booth at OpenRheinRuhr had the same problem,
they also had a 4/4 MiB split.
You may have to pare the kernel down to the bare minimum (i.e.
modularize about everything you don't need to boot to initrd). Not
sure where the limit for this is these days.
Note that the Debian kernel does not use initrd to boot (to the
finally installed system), especially as those tools are built
with klibc, which is currently still broken on m68k, and thus
contains everything needed to get into an ext3fs / from disc,
and then some. I don’t think you should be using a distro kernel
made under such constraints (nor should the distro kernel be
stripped more down considering the problems; I think there may
even be flavours that don’t _support_ initrd, outside the image
that is) but compile a stripped-down one yourself.
You're right, this should be possible to test with ARAnyM - the
behavior is not new though. Loading the kernel in TT-RAM has been
problematic on the Falcon for a long time now.
I don’t know about that; ARanyM has a built-in LILO, so I never
saw any TOS (except when using AfrOS, but that’s a whole different
beast)…
bye,
//mirabilos
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
