After some new input from some other thread inside AmigaWorld (see here: [url]email@example.com[/url]) I made some additional attempts.
Now I've got AOS4 booting from SATA SSD after kickstart had been loaded from IDE partition (I copied my kickstart dir onto my BOOT partition where also of file resides).
There are only 2 (minor) drawbacks resulting from the fact that I also have an additional IDE partition where I installed a clean AOS4.1 system. Hence I've got at least one bootable IDE partition (clean AOS4.1 install) with lower boot prio (2) and one SATA partition (beta installation) with higher boot prio (4).
- When making BOOT: partition with kickstart dir non-bootable bootloader shows available kicklayouts like the following:
First entry (not selected as default): Kickstart residing on BOOT: partition (partition lies in front of partition hosting AOS4.1 clean installation)
Second entry (selected as default): Kickstart residing on partition with clean AOS4.1 installation.
- When making BOOT: partition with kickstart dir bootable using boot prio 3 (higher than AOS4.1 clean installation but lower than AOS4.1 beta installation on SATA SSD) then kickstart on BOOT: partition is chosen as the default one but after kickstart has been loaded system still tries to boot from BOOT: partition even though SATA SSD should be booted from according to boot priorities! So I tried to use BootDevice entry inside kickstart directory of BOOT: partition doing in shell echo > Kickstart/BootDevice "AOS4" and enabling MODULE Kickstart/BootDevice as last entry inside kicklayout of BOOT: partition (AOS4 is the device name of SATA SSD AOS4.1 beta partition). But then when bootloader tries to process this entry it's telling me: "Kickstart/BootDevice missing" or sth. like that). Does this mean it cannot find the file named BootDevice (which exists at exactly that place with exactly this name) or does this mean it cannot find the appropriate device (since SATA devices are not available during kickstart loading)?
Maybe somebody can give some info on the second point? Question is: Why does system boot from SATA SSD bootable partition when BOOT: partition is non-bootable but does not boot from SATA SSD bootable partition when BOOT: partition is bootable (if necessary I can post the setup of those partitions as list with BOOT prio, device names, units etc.)?
The less painful procedure is now: Leaving BOOT: partition non-bootable and select it manually as partition where kickstart should be loaded from each time a cold reboot is necessary.
Or is there still sth. I missed here?