Ok. Installing grub-efi-amd64-signed was expected to fix the SecureBoot
bootability, so this was the problem. The logs provide no explanation
of why this package was missing from your system, however, so there's
nothing more we can do from this side to track that down. If you can
find some expla
$ dpkg -l 'shim*' 'grub*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture
I enabled Secure Boot and it's working now, thanks for help. But still,
I'm absolutely sure that I got this secure boot failure on 02/07 and I
had to disable it in order to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
term.log.2.gz also doesn't show any changes during June that would
explain the setup being trashed by the time July arrived.
If you really never had grub-efi-amd64-signed installed, then this
should never have worked under SecureBoot.
Please do the following:
- attach the output of 'dpkg -l 'sh
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489987
Title:
Secure Boot failed on Ubuntu 14.04 on Dell E7440
To manage notifications about this bug go to:
https://b
ok, so the term.log.3.gz shows the upgrade from May 18, and it appears
that at that time you *did* have grub-efi-amd64-signed installed and
probably also shim-signed.
The timestamp on the grubx64.efi is from July 2, which is when you say
the problem started. But your apt log for this time period
Ok, thanks for the clarification. I overlooked that this problem
started affecting you two months ago, I didn't expect a bug report would
be based on a boot problem from so long ago.
A few things:
- your file timestamps date back to May. Can you attach the apt term log for
*this* period? (whic
Steve, please do tell me if my present term.log (which does not cover
the time when Secure Boot failed) might be of relevance here. If so,
I'll attach it as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Yes, it was term.log, but since this all happened two months ago, the
relevant log was already archived. I'm now attaching it with the correct
name. Also I pasted the other outputs in the original post, but I'll
repaste them here as well for clarity:
/boot/efi/EFI/ubuntu$ ls -l
total 2592
-rwxr-xr
Is the attached file /var/log/apt/term.log? The filename (and the
contents) suggests this was /var/log/apt/term.log.1 instead.
Also need the information about the current state of your efi boot
partition and firmware settings (/boot/efi/EFI/ubuntu, efibootmgr -v).
--
You received this bug notif
@vorlon correct, this was an existing system and it worked fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489987
Title:
Secure Boot failed on Ubuntu 14.04 on Dell E7440
To manage notification
As per @vorlon's request.
** Attachment added: "term.log.1.gz"
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1489987/+attachment/4453943/+files/term.log.1.gz
** Description changed:
(I'm following instructions from https://help.ubuntu.com/community/UEFI
to report this here)
On
So just to be sure, you're saying that this was an existing system which
was installed with 14.04 and was working fine, then after upgrade, it
stopped working?
Please attach to this bug:
- a copy of /var/log/apt/term.log
- a directory listing of /boot/efi/EFI/ubuntu/
- the output of 'efibootmg
13 matches
Mail list logo
