Comment 15 for bug 1687729
Revision history for this message
| Jeff Lane (bladernr) wrote Re: [Bug 1687729] Re: Unable to deploy 16.04 w/ Xenial HWE to system with Secure Boot active | #15 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
On Thu, May 4, 2017 at 9:09 AM, Rod Smith <email address hidden> wrote:
> Jeff, the efibootmgr output indicates that Boot0008 is first in the boot
> order. That's a PXE-boot entry, as are the next three in the BootOrder
> list, so unless PXE-booting is failing for some reason, the Boot0010
> entry for Ubuntu's grubx64.efi should not come into play. You can test
> this by deleting the Boot0010 entry:
>
> sudo efibootmgr -b 0010 -B
>
> This should not affect booting if the system is PXE-booting, but if it's
> failing because of a direct boot of GRUB, this will cause the system to
> try the additional boot entries, which include additional PXE-boot
> entries, the USB drive, and the CD drive. If all of those fail it will
> probably launch the firmware setup utility, or maybe an EFI shell.
That is true and yes PXE works fine. The sequence is: Hardware OpROMs
load, node PXE boots, MAAS tells it to boot locally, then it tries
loading the shim and can't find it.
As noted above, when I disable SB and boot into the OS, the shim is
clearly present in /boot