Here's the output
BootCurrent: 0015
Timeout: 0 seconds
BootOrder:
0000,0001,0016,0013,0014,0015,0012,0010,0011,0019,001A,001B,0017,0018
Boot0000* fedora
HD(1,800,fa000,a37591b8-de99-44c3-9eb8-e7de6f28d62d)File(\EFI\fedora\grubx64.efi)
Boot0001* Windows Boot Manager
HD(1,800,fa000,a37591b8-de99-44c3-9eb8-e7de6f28d62d)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...5................
Boot0010 Setup
Boot0011 Boot Menu
Boot0012* Removable Drive
030a2400d23878bc820f604d8316c068ee79d25b20699b27e1a34f488e97534d40523c1d
Boot0013* Hard Drive
030a2400d23878bc820f604d8316c068ee79d25bf5b01cc8ce8e9841b3a8fb94b6dfefee
Boot0014* USB Storage Device
030a2400d23878bc820f604d8316c068ee79d25b6895f49a99882e4bb0da03ec784d2828
Boot0015* CD/DVD/CD-RW Drive
030a2400d23878bc820f604d8316c068ee79d25b3750dce1249e1748876bee5d3f25ebfb
Boot0016* Network
030a2400d23878bc820f604d8316c068ee79d25b6567de8ee595634d842b325e6a43510b
Boot0017* Onboard NIC
030a2400d23878bc820f604d8316c068ee79d25b1b7f7356e3475744a9a6ed8e91832083
Boot0018* Onboard NIC
030a2400d23878bc820f604d8316c068ee79d25bb4a054dda1fa7043abf832c5a88367a6
Boot0019 Diagnostics
Boot001A Peripheral Device setting (OPROM setting)
Boot001B Change boot mode setting
On Mon, Mar 17, 2014 at 12:11 PM, Chris Murphy <li...@colorremedies.com>wrote:
>
> On Mar 17, 2014, at 10:47 AM, pgaltieri . <pgalti...@gmail.com> wrote:
>
> > This didn't work. I still get the access denied error. The
> /boot/efi/EFI/fedora directory contains a file
> >
> > gcdx64.efi
> >
> > and
> >
> > grubx64.efi
> >
> > They are both the same size. The first is dated July 2 2013 the other
> is dated today. I tried renaming grubx64.efi to gcdx64.efi but it also
> failed.
>
> I think I understand what's going on. The grub2-install command added a
> new NVRAM entry pointing to grubx64.efi. While you now have the correctly
> signed grubx64.efi file, the NVRAM entry pointing to it is incorrect,
> because grubx64.efi is signed with the Fedora key which isn't present in
> your firmware (normal). The NVRAM entry should either be deleted, or
> replaced to point to shim.efi which is signed with a Microsoft key, which
> is in your firmware. Either way then shim.efi will properly execute
> grubx64.efi.
>
>
> From the rescue environment (not chrooted), what do you get for
>
> efibootmgr -v
>
> cat /mnt/sysimage/var/log/anaconda/anaconda.program.log | grep efibootmgr
>
>
> Chris Murphy
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
