6722 2014-09-12 21:12:17 +0000 Boot entry for partition not exposed 2015-02-17 21:12:48 +0000 1 1 12 Hardware Platforms MinnowBoard MAX Firmware minnowboard-firmware 2C A1 MinnowBoard Max Multiple RESOLVED WORKSFORME Medium normal Production Release 1 marcel dvhart danders david.wei dvhart marcel matt shifeix.a.lu sjolley.yp.pm warthog9 yoctoproject --- --- No (bug/feature does not impact docs) oldest_to_newest 45597 0 marcel 2014-09-12 21:12:17 +0000 The boot options for the selected boot entry does not reveal any information about the partition. This is from bootctl utility: System: Machine ID: e175a86a8ac145f78a9bdc62b4d27f25 Boot ID: 1f39b9c0ed454a2cb9db0a1ebd0fda33 Firmware: UEFI 2.40 (EDK II 1.00) Secure Boot: disabled Setup Mode: setup Selected Firmware Entry: Title: EFI Hard Drive Partition: n/a Boot Loader: Product: gummiboot 45 Partition: /dev/disk/by-partuuid/fa592eba-3242-4575-99a2-e52d8a830142 File: └─/EFI/BOOT/BOOTX64.EFI Normally the Partition: n/a from Selected Firmware Entry should resolve to the same Partition information from Boot Loader. Checking with efibootmgr I see that the partition information is missing: BootCurrent: 0001 Timeout: 5 seconds BootOrder: 0001,0002,0000 Boot0000* EFI Internal Shell FvVol(a881d567-6cb0-4eee-8435-2e72d33e45b5) Boot0001* EFI Hard Drive ACPI(a0341d0,0)PCI(12,0)Controller(0) Boot0002* EFI Network ACPI(a0341d0,0)PCI(1c,2)PCI(0,0)MAC(MAC(001320fe319e,0) For boot entry 0001, it misses the HD() entry providing the UUID. 45598 1 sjolley.yp.pm 2014-09-12 21:19:46 +0000 Not HW this is Frimware 45818 2 tim.he 2014-09-25 07:48:22 +0000 Thanks Marcel, I will check the information about partition. 46630 3 shifeix.a.lu 2014-10-29 05:25:33 +0000 Hi Marcel, Our BIOS can reach device level with Device Path of EFI Hard Drive,not reach Partition level with Device Path of EFI Hard Drive. If you want to need Partition information from Boot Loader,maybe Yocto OS will involved in to investigate it. 46632 4 david.wei 2014-10-29 06:24:08 +0000 More detail from me and Shifei: Boot0001* EFI Hard Drive ACPI(a0341d0,0)PCI(12,0)Controller(0) Above boot option "Boot0001* EFI Hard Drive" is the path of hard drive, not the file path pointing to boot loader file (BOOTX64.EFI). When user selec to boot from this device, BIOS searchs for boot loader file (BOOTX64.EFI) within this HDD. This formate is not a bug. Typically there is another boot option whose path does contains the bootable partition's name and the boot loader file's name. But that boot option is not generated by BIOS, it is generated by OS boot loader itself. Take Microsoft Windows for example, Windows boot loader adds a "Windows Boot Manager" option into the boot menu at the first boot. So I re-assgin this bug to Marcel Holtmann to continue investigating from OS loader side. 46834 5 dvhart 2014-11-06 23:35:25 +0000 Matt, wondering if you can add some experience here. Does look like an OS or a firmware issue to you? 46858 6 matt 2014-11-07 14:59:57 +0000 Hard to say. Can someone use efibootmgr to create a new boot entry with a partition and loader option? Something like, efibootmgr -c -d /dev/sda -p 1 -l \\EFI\\BOOT\\BOOTX64.EFI -L "Test loader" should do the trick. Then update this report with the output of efibootmgr -v. 46888 7 david.wei 2014-11-10 01:59:08 +0000 The UEFI BIOS also has an integrated function which allow user to add "<Partition>\\EFI\\BOOT\\BOOTX64.EFI" as a new boot option. Please enter BIOS Setup, then go into "Boot Maintenance Manager -> Boot options -> Add Boot Option", which will list out the bootable BOOTX64.EFI for you to add. Basically, the path of directory where boot loader is stored, such as "\\EFI\\BOOT\\BOOTX64.EFI", should be OS specific. It is not defined by UEFI specification. As you know, our current BIOS could automatically boot from Yocto OS loader "\\EFI\\BOOT\\BOOTX64.EFI" even there is no such a boot option pointing to this file. That's because this path, which is treated as a "well known OS laoder" path by our BIOS, along with its partition path, are appened to the device path of SD controller "ACPI(a0341d0,0)PCI(12,0)Controller(0)" to form a full path. But I think this is only a enhancement from BIOS side. It cannot cover the job what OS/OS loader should do. 47013 8 warthog9 2014-11-13 23:37:42 +0000 Marcell can you double check what Matt and David were saying? 48677 9 warthog9 2015-02-10 00:37:34 +0000 Following Matt's suggestion, with 0.77 and a 3.19 kernel, test loader is added and seems to work. I'm going to close, if this is incorrect please re-open