[Bug 1578837] Re: Secure Boot failure on Lenovo x3550 M5

2016-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shim (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578837 Title:

[Bug 1578837] Re: Secure Boot failure on Lenovo x3550 M5

2016-05-06 Thread Rod Smith
I've done some more experiments. After booting in the normal MAAS way with Secure Boot disabled, I created an entry with efibootmgr to boot directly from the local hard disk, bypassing MAAS and its PXE boot. The system booted fine with this configuration, even after enabling Secure Boot. Thus,

[Bug 1578837] Re: Secure Boot failure on Lenovo x3550 M5

2016-05-06 Thread Rod Smith
** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578837 Title: Secure Boot failure on Lenovo x3550 M5 To manage notifications about this bug go to:

[Bug 1578837] Re: Secure Boot failure on Lenovo x3550 M5

2016-05-06 Thread Rod Smith
I'm attaching the contents of the /var/lib/maas/boot- resources/snapshot-20160426-183112 directory on the MAAS server (minus the ubuntu and custom directories, which contain OS images and are therefore huge). This tarball includes the shim and GRUB images used in this process. I'm also including

[Bug 1578837] Re: Secure Boot failure on Lenovo x3550 M5

2016-05-06 Thread Rod Smith
** Attachment added: "Contents of MAAS clusterd.log file showing activity involved in failed boot." https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1578837/+attachment/4657252/+files/clusterd.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is