I’ve managed to get Aranym to boot m68k Debian, although getting networking going is another matter. The initial problem was with my config having the incorrect disk geometry (thanks to arosfan for making me double check my settings).

I’ve also been looking at getting the m68k unmaintained compile going again on x86, but have not had much luck with this to be honest. I’m still trying to get my head around the weird AROS build process.

No doubt I shall have to pop over to #aros for a chat with some devs soon.


After chatting to a number of people on the AROS dev list and #aros, I’ve decided to change tact on the bounty and try a different approach.

The idea is to forget about the stuff in .unmaintained, and try to get AROS compiling for m68k-hosted. For work to begin, I’ll need to get debian m68k installed and running on Aranym (yes, an Atari ST virtual machine :-) ). This was also the direction that the previous bounty owners were going (and looking at the date on this blog post, you can see that the bounty is at pretty much the same point it was just over a year ago!)

Although I’d really rather use Debian-m68k under UAE, the Linux version of UAE doesn’t seem to have MMU support (if I’m wrong about this, somebody please correct me). There is an MMU patch for version 0.8.20 that doesn’t build on the Karmic version of Ubuntu I’m currenty running (you need GTK v1 installed for this to work, plus it doesn’t pick up on X at all during configure).

Trying to get Aranym installing Linux from an ISO or boot floppy was a right pain. More so because I know bugger all about the Atari ST, what with being an Amiga user!

Anyway, after a bit of Google-fu, I came across this page. Basically it looks like the nice people at Debian have done the majority of the work for you in getting Debian up and running on Aranym.

So, we follow the instructions, and after some time of reading docs, twidling settings etc. we get Aranym to a point where it almost boots Debian Sid, but not quite…

[42949375.250000] Uniform Multi-Platform E-IDE driver
[42949375.250000] ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
[42949375.260000] ide: Falcon IDE controller
[42949375.260000] Probing IDE interface ide0...
[42949375.570000] hda: Master, ATA DISK drive
[42949376.650000] ide0 at 0xfff00000 on irq 15
[42949376.650000] hda: max request size: 128KiB
[42949376.660000] hda: 2118816 sectors (1084 MB) w/256KiB Cache, CHS=2102/16/63
[42949376.660000] hda: unknown partition table

[42949378.530000] VFS: Cannot open root device "hda1" or unknown-block(3,1)
[42949378.530000] Please append a correct "root=" boot option; here are the available partitions:
[42949378.530000] fe80 10485720 nfhd8 (driver?)
[42949378.530000] fe81 8496093 nfhd8p1
[42949378.540000] fe82 1989626 nfhd8p2
[42949378.540000] 0200 3280 fd0 (driver?)
[42949378.540000] 0201 3280 fd1 (driver?)
[42949378.540000] 0300 1059408 hda driver: ide-disk
[42949378.540000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)

Ouch. I’ve highlighted the key lines here, which basically indicate that the disk image I’ve downloaded from the wiki is not valid.

Suffice to say after this I set off to the directory where the disk image was downloaded from in search of a disk image that was valid…

More updates to follow :-)


Last night I started to look at the Kickstart ROM replacement bounty phase 1. I’ve been wanting to help out with AROS for a while, but the bounty I really wanted to work on was taken. It’s now been released, and assigned to me, yey!

Anyway, the requirements of the bounty are basically to get the Amiga m68k build of AROS working again. You can read more about it here.

I’ve only just started looking at the problem, but basically there are a few of stages I need to complete to finish the bounty:

  1. Move amiga and m68k-native out of arch/.unmaintained
  2. Build binutils and gcc for m68k-amigaos
  3. Update the build configuration so that the generated symlinks in bin/amiga-m68k/tools point to the correct tools
  4. Configure and build, fix any build problems encountered
  5. Try and bootstrap the AROS binary on UAE

I’m currently not sure how to achieve number 3, as I’m still learning about the AROS build process, and poking around to see how it’s done.

Steps 4 and 5 are obviously the biggest part of the bounty, so these will take the longest and will probably be split up into smaller stages.

If anybody has any comments, ideas or suggestions, I’d welcome them.

That’s all for now. I’ll keep you all posted on my progress.


Welcome to my first blog post.

This blog is here primarily for me to collect my thoughts, and to keep all the AROS folks updated with my progress on the Kickstart ROM replacement bounty.