Getting somewhere, I guess?
Gets slightly better when supplying an initrd *cough*
Still doesn't boot to anything usable though.
Don't you love it when a search for a phrase returns all of two results?
Apparently, it's a framebuffer problem.
ARAnyM LILO config currently is:
LoadToFastRam = Yes
Kernel = ~/Downloads/vmlinux-5.6.0-2-m68k
Args = root=/dev/ram load_ramdisk=1 ramdisk_size=25000 video=atafb:vga16 stram_swap=0 debug=par verbose console=tty0 debian-installer/framebuffer=false
Ramdisk = ~/Downloads/initrd.gz
Hrm. The current installer can't verify keys from the archive. Checking those can be disabled with a boot parameter (see https://www.debian.org/releases/buster/amd64/ch05s03.en.html#installer-args), but setting debian-installer/allow_unauthenticated=true just leads one step further, when it sais there are no matching kernel modules.
I think I'll have to somehow aproach this differently...
(Looking at the debian-68k archives, developers are now mostly using qemu-m68k...)
@galaxis well, yes... sadly.
I always tried to argue in favour of real hardware and such. At least Adrian has 2x Amiga 060 borrowed from me, but it's really a problem: when I started with m68k autobuilders in May 2000 there were like 2200 packages or so. Now there are about 40-50000 packages to be built. That's impossible to keep up with 68060/50s
Of course it would also help when Adrian would not be more or less the last m68k dev that does the porting stuff...
@ij Tbh I was just on a detour playing around with Debian-m68k since it seemed in kind of a usable state, but I probably missed the window by half a year. Would certainly have tried on the TT if I could have made it work in Aranym.
I originally only wanted to set up a VM where I could run MiNT while I don't have access to real hardware.
@galaxis just report the issue. Adrian is usually quite quick in fixing things...
@mmu_man @galaxis Hmmm, emulated hardware is always complicated... Real hardware usually has its own bugs, maybe different from revision to revision, while emulated CPUs have different or not such bugs. So, if you compile the toolchain on an emulated system, this might work - until some corner cases will bite you on real hardware.
If everything goes back, you'll need to recompile the whole toolchain on real hardware to fix the bug.
In general, the speedup on qemu is a real benefit, though...
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!