12584 2018-03-06 11:31:43 +0000 Generic EFI booting needs to support random UUIDs 2026-01-16 13:43:32 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-oe-core 0.0.0 x86 Multiple NEW Medium normal 6.99 1 california.l.sullivan unassigned ccasciato randy.macleod richard.purdie stephano --- --- Don't know oldest_to_newest 79723 0 california.l.sullivan 2018-03-06 11:31:43 +0000 Currently, the generic EFI boot method using the following assume root=/dev/sda2 or similar: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/lib/wic/canned-wks/efi-bootdisk.wks.in https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-core/systemd/systemd-bootconf_1.00.bb https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-bsp/grub/grub-bootconf_1.00.bb Using /dev/sda and such is not a reliable way to boot, as it depends on the install media enumerating to a certain value. Instead random UUIDs should be used. This will require both the -bootconf recipes and wic to know the same random value. This value also needs to be saved in sstate, else issues will arise when rebuilding and doing package upgrades. The current path to explore to accomplish this is as follows: 1) modify wic to take a file containing a UUID as input for its UUID creation 2) merge the -bootconf recipes into one recipe with multiple packages. This package would also deploy the UUID file for consumption. 3) modify efi-bootdisk.wks.in to use the new wic functionality and UUID file. This would allow all bootloaders and wic to know the same UUID, and since it uses deploy should work with sstate. The new bootconf recipe would need to be extensible to support any arbitrary bootloader as well. 91889 1 richard.purdie 2021-11-04 15:12:59 +0000 systemd-bootconf file still contains root=/dev/sda2 so no EFI uuid support despite general wic uuid support 96890 2 randy.macleod 2023-10-24 14:24:38 +0000 Bulk move from 4.99 or 0.00 to 5.99