On Fri, Apr 19, 2013 at 12:55:13PM -0000, Dan Winkler wrote: > Boot000C* ubuntu > HD(1,800,5d21800,1bbce1c1-4706-4196-a31f-ff245bddffed)File(\EFI\ubuntu\grubx64.efi)
Oh, that's very strange. We've seen reports of similar behavior before when the firmware's nvram space has been filled up (see https://lists.ubuntu.com/archives/ubuntu-devel/2013-April/037029.html). But if this is a new install, I don't know why you would have that problem, and it still doesn't explain why the installer set this to grubx64.efi in the first place. First thing's first, can you check that you have the 'shim-signed' package installed? ('dpkg -l shim-signed') If not, please install it with 'sudo apt-get install shim-signed', then run 'sudo grub-install --uefi-secure-boot' again. If that still doesn't fix it to let you run under secure boot mode, please do the following. Show the output of this command: $ ls -l /sys/firmware/efi/efivars/ Please then also try running these commands from the commandline (one immediately after the other), and paste the output: $ sudo efibootmgr -v -c -d /dev/sda -p 1 -w -L ubuntu -l '\EFI\ubuntu\shimx64.efi' $ echo $? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170183 Title: can not boot up in uefi secure boot mode unbuntu 13.04, can run in a live from cd uefi secure mode. will boot non secure boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1170183/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
