Finally got Linux booting successfully to shell.
I'm now using Geert's kernel, but I think the main issue was just
getting a working kernel configuration. There was something causing
oopses in the old one.
I also never got ramfs booting working correctly, but booting with
IDE rootfs i.e. what was working on real device, works now. [1]
Attached are working config, and bootlog from where you can see
Hatari options.
IDE content was just busybox in bin/, made into a FAT file system
with atari-hd-image script coming with Hatari, so it wasn't very
useful. :-)
After I've tested few extra things and updated/cleaned the docs a bit,
I'll push the updated patches in, if there are no further comments /
objections about them.
[1] Trying to boot with that same FAT rootfs that works through IDE,
from a floppy, never finished. I just got warnings from m68k kernel
soft-watchdog every few minutes that things were (still) stuck
somewhere. -> I think kernel itself is buggy in some configs.
- Eero
On 3/21/19 1:35 AM, Eero Tamminen wrote:
I got Linux starting enough that it showed logs also in Atari screen,
not just debug console, and it tried running init, at which point it
got NULL pointer Oops. Log attached.
I got this by building few days old Linux Git from upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Using the attached kernel config.
(Maybe the Debian 3.6 & 4.9 binary kernels I tried earlier enabled
some extra HW which probing disagrees with Hatari.)
This new kernel build some weird extra objects for which there were
no config options (e.g. some ARM omap stuff), but I didn't check
whether linker discarded those from final binary or not.
I'll probably try Geert's (m68k arch maintainer) kernel next:
https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git/log/?h=m68k-v5.0
And try to get newer m68k initrd content.