Comment # 35 on bug 1174412 from
(In reply to Andr�s Barrantes Silman from comment #33)
> BootCurrent: 0002
> Timeout: 0 seconds
> BootOrder: 0003,0002,0001
> 
> Boot0000* Windows Boot Manager 
> HD(1,GPT,006a637d-39b9-4d5d-be5a-e770db71c27f,0x800,0x32000)/
> File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.
> =.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.
> }...t................
> 
> Boot0001* Windows      
> PciRoot(0x0)/Pci(0x17,0x0)/Sata(1,65535,0)/HD(1,GPT,006a637d-39b9-4d5d-be5a-
> e770db71c27f,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)
> 
> Boot0002* OpenSUSE     
> PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-1B-44-8B-46-D1-0C-40)/
> HD(1,GPT,4aaad53c-5ec2-4c59-a48d-981c60d11db4,0x800,0xfa000)/
> File(\EFI\opensuse\shim.efi)
> 
> Boot0003* opensuse-secureboot  
> HD(1,GPT,4aaad53c-5ec2-4c59-a48d-981c60d11db4,0x800,0xfa000)/
> File(\EFI\opensuse\shim.efi)
> 
> 
> I did not install the custom software you posted above, should I do it and
> then update the logs?
> 
There is no need to install efibootmgr I've posted. Just want to check the
content of the boot entry.

> Now that I look closer, as you suggest, it is indeed sending an incomplete
> boot entry, since appending
> "PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-1B-44-8B-46-D1-0C-40)/"
> seems to make Boot0003 match Boot0002. 

The short device path is convenient in some cases. For example, moving hdd from
SATA1 to SATA2 won't break the boot entry since the UUID doesn't change. A boot
entry with a full device path is restricted to the specific bus.

It seems the firmware doesn't like the short device path :-(

> What looks so weird to me is the fact that Windows boot entry, despite being
> on the hard drive, has "PciRoot(0x0)/Pci(0x17,0x0)/Sata(1,65535,0)/"
> appended.  It does say sata instead of nvme, but it still seems odd to see
> PCI thrown in there.
> 
It just means SATA1 is wired to PCI bus and is common in x86 systems.

> By the way, I erased the SSD's GPT when reinstalling.


You are receiving this mail because: