So, when the UUIDs were the same for (/boot and /) partitions on Micro SD and NVME, the boot loader defaults to the NVME even IF the EEPROM directive is not 0xF41? Versus 0xF416?
0xF41 = Boot Micro SD Card
0xF416 = Boot NVME
It is my understanding that 0xF41... should always boot from Micro SD card. Where as 0xF416 should always boot from NVME (providing PCIE support is enabled of course).
I found almost the similar behavior on an IndieDroid Nova, that uses U-Boot. In the case of the Nova, the boot loader defaults to EMMC memory then falls back to Micro SD card. The Nova boot loader is not smart enough to do more than look for the UUID and once found, matching, boots that partition. Even though U-Boot supports a menu system (a bit like grub), and even after setting up a menu under U-Boot, it is ignored. Not good.
Really wish SBC boot loaders would step up their logic/control, so we have something comparable to grub as we do for AMDx86 systems.
0xF41 = Boot Micro SD Card
0xF416 = Boot NVME
It is my understanding that 0xF41... should always boot from Micro SD card. Where as 0xF416 should always boot from NVME (providing PCIE support is enabled of course).
I found almost the similar behavior on an IndieDroid Nova, that uses U-Boot. In the case of the Nova, the boot loader defaults to EMMC memory then falls back to Micro SD card. The Nova boot loader is not smart enough to do more than look for the UUID and once found, matching, boots that partition. Even though U-Boot supports a menu system (a bit like grub), and even after setting up a menu under U-Boot, it is ignored. Not good.
Really wish SBC boot loaders would step up their logic/control, so we have something comparable to grub as we do for AMDx86 systems.
Statistics: Posted by Schorschi — Mon Feb 26, 2024 8:59 pm