http://bugzilla.opensuse.org/show_bug.cgi?id=1183884 http://bugzilla.opensuse.org/show_bug.cgi?id=1183884#c10 Michael Chang <mchang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(linuxkamarada@gma | |il.com) --- Comment #10 from Michael Chang <mchang@suse.com> --- (In reply to Projeto Linux Kamarada from comment #3)
Created attachment 847744 [details] Output of efibootmgr -v
The efi boot entry didn't look good to me...
Boot0002* Kamarada PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(1,GPT,7142e6bb-de6c-425b-9f70-ed70c6798843,0x800,0x32000)/File(\EFI\Linux_Kamarada\grubx64.efi)A01 .. Boot0003* Unknown Device: HD(1,GPT,7142e6bb-de6c-425b-9f70-ed70c6798843,0x800,0x32000)/File(\EFI\opensuse\grubx64.efi)RC Boot0004* Unknown Device: HD(1,GPT,7142e6bb-de6c-425b-9f70-ed70c6798843,0x800,0x32000)/File(\EFI\opensuse\grubx64.efi)RC Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot2003* EFI Network RC
Why the lable was written as "Unknown Device" whereas the grubx64.efi was installed into \EFI\opensuse\... ? The correct label should be "opensuse", so I wonder is that a change made by firmware ? Also why would the path contain trailing 'RC' or 'A01 ..' that would make the device path 'invalid' ? Which boot entry you were using to boot the opensuse? Have you tried the 'Unknown Device' ? Besides we may need the config files which would be used for efi label creation. /etc/default/grub /etc/os-release And the output of the command ls -lR /boot/efi The access time would be useful to tell which grubx64.efi was updated and when ... Thanks. -- You are receiving this mail because: You are on the CC list for the bug.