Bug 1343559

Created attachment 1165651 [details]
program.log

Created attachment 1165652 [details]
journal.log

Could you grab the output from 'efibootmgr -v'?

It's possible that we didn't setup the correct path to shim.efi, or your firmware may require manual intervention for whatever reason.

You could also try running:

efibootmgr -c -w -L FedoraTest -d /dev/mmcblk0 -p 1 -l \EFI\fedora\shim.efi

and also post the output of 'efibootmgr -v' afterwards.

efibootmgr -c -w -L FedoraTest -d /dev/mmcblk0 -p 1 -l \EFI\fedora\shim.efi
 
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0004,0001,2001,2002,2003
Boot0000* Unknown Device: 
Boot0001* Fedora
Boot0002* Unknown Device: 
Boot0003* Windows Boot Manager
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
Boot0004* FedoraTest

efibootmgr -v

BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0004,0001,2001,2002,2003
Boot0000* Unknown Device: 	HD(1,GPT,7808b833-e89a-4456-ae50-459c67e9dcc6,0x800,0x64000)/File(\EFI\fedora\shim.efi)RC
Boot0001* Fedora	PciRoot(0x0)/Pci(0x17,0x0)/Ctrl(0x0)/HD(1,GPT,7808b833-e89a-4456-ae50-459c67e9dcc6,0x800,0x64000)/File(\EFI\fedora\shim-fedora.efi)A01 ..
Boot0002* Unknown Device: 	HD(1,GPT,7808b833-e89a-4456-ae50-459c67e9dcc6,0x800,0x64000)/File(\EFI\fedora\shim.efi)RC
Boot0003* Windows Boot Manager	HD(2,GPT,5fd3b602-b757-4beb-b2af-b45f1ddedef1,0x12c800,0x96000)/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.}....................
Boot0004* FedoraTest	HD(1,GPT,7808b833-e89a-4456-ae50-459c67e9dcc6,0x800,0x64000)/File(EFIfedorashim.efi)
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

If you do:

cd /sys/firmware/efi/efivars/
cp PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443 ~/
cp BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c ~/
# if chattr fails, ignore the failure
chattr -i PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443
rm PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443
cat ~/BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c > PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443

and then reboot, do the right menus show up?

(In reply to Peter Jones from comment #5)
> If you do:
> 
> cd /sys/firmware/efi/efivars/
> cp PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443 ~/
> cp BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c ~/
> # if chattr fails, ignore the failure
> chattr -i PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443
> rm PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443
> cat ~/BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c >
> PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443
> 
> and then reboot, do the right menus show up?

Which menus?

Now I boot directly into Grub and after in Fedora, to do what you ask and check menus you mean first to remove the trusted efi file I selected?

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.