Quote:

Well, just goes to show that you shouldn't trust everything you read on the internet :P

The design of this whole Amiga OS 4-U-Boot boot system is indeed a giant mess, but that's a rant for another time.

MorphOS' U-Boot bootloader supports chain-loading the Amiga OS 4 bootloader from a file on the installed system, although this has only ever been tested on the X5000, as I don't have a copy of Amiga OS 4 for the Sam460. The path to the file should be :l/slb_v2. MorphOS' U-Boot bootloader supports FFS and SFS, so it has to be one of those two filesystems. Also due to limitations in Amiga OS 4, Amiga OS 4 has to have the highest boot priority, and thus be the default, for this to work.

Alternatively you can load just the MorphOS bootloader off an SD card, but then use the boot device selector to choose to boot off a partition with MorphOS installed on it.

This sound great. I will test and report back.

>> Since the bootloaders don't mutually support AmigaOS and MorphOS, there
>> is a blog showing this "convenient" way to boot both OS on the SAM460.

> just goes to show that you shouldn't trust everything you read on the internet :P

Apart from that blog, he may have come across that thread where the thread opener failed to run both MorphOS and OS4 from the same drive. It wasn't resolved back then, and the thread opener then resorted to not even using different drives on the same X5000, but to using each OS on its own X5000 ;-)

So, simply copying the AmigaOS bootloader to :L doesn't trigger the hyperbootloader to chain-load it.
Is there a way to configure the MorphOS bootloader? I looked in the HDConfig tool (the edit bootloader option sounds promising) but found nothing helpful.

[ Edited by Skygecko 03.08.2023 - 14:16 ]

Quote:

Hyperbootloader automatically lists all found RDB partitions that are marked as bootable and don't have the do not mount flag set, and which use a supported filesystem (ie, FFS (DOS3 and DOS7) or SFS (SFS\0)) as options to boot from. No configuration is necessary.

If Hyperbootloader doesn't list the partition containing :l/slb_v2. as a boot option, then it is either on a partition using an unsupported filesystem, the partition is not marked as bootable, the partition is marked as do not mount or for one reason or another, the disk can't be read by U-Boot at all, with the latter option being unlikely.

When Hyperbootloader lists your boot options, press the key on your keyboard corresponding to the partition you want to boot from. Here's the output of Hyperbootloader on my system here:

Code:

By default it will boot from DH0:, but if I want it to boot from DH1: instead, I have to press the 2 key on the keyboard when presented with this prompt.

It finally works :) Now I have DH0 for MorphOS, DH1 as a shared data partition and DH2 for AmigaOS on my HDD.
Thank you very much for all your help and explanations!

Glad to hear you got it working and confirming that it also works on the Sam460!

I just playing with my Sam460LE and three operating systems. I have question about bootloaders:

Are Hyperbootloader ( installed by MOS ) and slb_v2 ( installed by AOS ) installed on the same disk block(s)? I.e. are they mutually exclusive?
And can I simply overwrite slb_v2 with hyperbootloader and vice versa?

It SHOULD be this way, but I want to be sure, so excuse my a little stupid question


[ Edited by sailor 06.11.2024 - 09:28 ]

Don't simply overwrite slb_v2 with hyperbootloader since only slb_v2 can boot AOS4.
AOS should be installed on a SFS\00 partition/disk and the SAM460 needs to boot the MorphOS partition/disk first.
Hyperbootloader then simply lists all RDB partitions with compatible file systems (AOS on SFS\02 will not be found) so it can chainload slb_v2 on a SFS\00 partition to boot AOS4.

Quote:

Thanks, I know, I have it this way:
-SDcard: Hyperbootloader + SFS0 partition with L:slb_v2 + Kickstart/*
-SATA: slb_v2 ( not needed in this scenario), SFS0 MorphOS partitions, SFS02 AmigaOS partitipns
everything is worked as expected:
boot from SD invoke Hyperbootloder menu, I can continue to MOS or AmigaOS-slb

But I want to testing some configurations and also install linux, and want to install Hyperbootloader to SSD. And question is, if I overwrite Hyper again with slb, if there remains something somewhere, or is it OK. I.e. if slb and hyper occupy exactly the same place on disk...

They should, but I want to be sure.