04-21-2022, 08:32 AM
(04-21-2022, 06:00 AM)wibble Wrote: The multiboot image is built to use and take advantage of the features of megi's p-boot. It doesn't have the config file that tow-boot looks to for the kernel, initrd, boot args etc. so tow-boot doesn't find anything that it knows how to boot. Even if the partition layout is something tow-boot could read, and you translated the p-boot config for the boot options to the format tow-boot uses, I don't think you'd have a way to select which multi-boot option you wanted as tow-boot doesn't have a GUI on the pinephone. It's the wrong tool for the job - stick to p-boot for multiboot.
Thanks for that explanation! I was thinking “yeah, of course that makes sense and I’d completely forgotten that Megi’s p-boot was what enabled his multiboot menu...” so I shouldn’t expect it to work unless Megi were to make some changes to his multiboot image.
But then I thought: how come Tow-Boot correctly booted the multiboot menu from the microSD card install and let me select which distro/OS I wanted to launch?
If I’ve understood your explanation correctly, Tow-Boot shouldn’t have been able to “see” anything to boot from the microSD card? So my experience should have been the same as with the multiboot install on the eMMC?
