On Fri, Apr 19, 2013 at 10:26:36PM -0000, Dan Winkler wrote: > Boot000D* ubuntu > HD(1,800,5d21800,1bbce1c1-4706-4196-a31f-ff245bddffed)File(\EFI\ubuntu\shimx64.efi) > lucille@lucille-Inspiron-7720:~$ echo $? > 0 > lucille@lucille-Inspiron-7720:~$
Ok. The efibootmgr command succeeded, and the efivars usage looks reasonable, so this doesn't seem to be a problem with the nvram being filled up.
So when you checked, you found the shim-signed package installed? I.e., the output looked like this?
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 Description +++-==============-============-============-================================= ii shim-signed 1.2+0~201209 amd64 Secure Boot chain-loading bootloa
Can you confirm that /boot/efi/EFI/ubuntu/shimx64.efi is present on your system?
If it is, you should now be able to boot Ubuntu under Secure Boot.
If it's not, you still need to install the shim-signed package after all.
On Fri, Apr 19, 2013 at 10:26:36PM -0000, Dan Winkler wrote: 5d21800, 1bbce1c1- 4706-4196- a31f-ff245bddff ed)File( \EFI\ubuntu\ shimx64. efi) lucille- Inspiron- 7720:~$ echo $? lucille- Inspiron- 7720:~$
> Boot000D* ubuntu
> HD(1,800,
> lucille@
> 0
> lucille@
Ok. The efibootmgr command succeeded, and the efivars usage looks
reasonable, so this doesn't seem to be a problem with the nvram being filled
up.
So when you checked, you found the shim-signed package installed? I.e., the
output looked like this?
Desired= Unknown/ Install/ Remove/ Purge/Hold Not/Inst/ Conf-files/ Unpacked/ halF-conf/ Half-inst/ trig-aWait/ Trig-pend /Reinst- required (Status,Err: uppercase=bad) ======= ====-== ======= ===-=== ======= ==-==== ======= ======= ======= ======= =
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii shim-signed 1.2+0~201209 amd64 Secure Boot chain-loading bootloa
Can you confirm that /boot/efi/ EFI/ubuntu/ shimx64. efi is present on your
system?
If it is, you should now be able to boot Ubuntu under Secure Boot.
If it's not, you still need to install the shim-signed package after all.