Bug 1733817 - shim fails on aarch64 when booting from a U-Boot firmware
Summary: shim fails on aarch64 when booting from a U-Boot firmware
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: shim
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Garrett
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker IoT
TreeView+ depends on / blocked
 
Reported: 2019-07-28 22:30 UTC by Peter Robinson
Modified: 2019-08-19 12:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Peter Robinson 2019-07-28 22:30:47 UTC
For us to support EBBR on Fedora we need to be able to boot the standard UEFI boot process with EFI/BOOT/BOOTAA64.EFI but when do that, as opposed to hardcoding the grub path we get the following failure when shim tries to boot.

shim-aa64-15-8.aarch64


U-Boot> boot
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found EFI removable media binary efi/boot/bootaa64.efi
Found DTB mmc 0:2 /dtb/broadcom/bcm2837-rpi-3-b.dtb
14118 bytes read in 5 ms (2.7 MiB/s)
Scanning disk mmc@7e202000.blk...
Card did not respond to voltage select!
Scanning disk mmcnr@7e300000.blk...
Disk mmcnr@7e300000.blk not ready
Found 4 disks
FDT memrsv map 0: Failed to add to map
BootOrder not defined
EFI boot manager: Cannot load any image
858216 bytes read in 39 ms (21 MiB/s)
FDT memrsv map 0: Failed to add to map
System BootOrder not found.  Initializing defaults.
Could not read \EFI\: Invalid Parameter
Error: could not find boot options: Invalid Parameter
start_image() returned Invalid Parameter
## Application terminated, r = 2
FDT memrsv map 0: Failed to add to map
BootOrder not defined
EFI boot manager: Cannot load any image
858216 bytes read in 39 ms (21 MiB/s)
FDT memrsv map 0: Failed to add to map
System BootOrder not found.  Initializing defaults.
Could not read \EFI\: Invalid Parameter
Error: could not find boot options: Invalid Parameter
start_image() returned Invalid Parameter
## Application terminated, r = 2
EFI LOAD FAILED: continuing...
Card did not respond to voltage select!

Device 0: unknown device
Waiting for Ethernet connection... unable to connect.

Comment 1 Ben Cotton 2019-08-13 17:00:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 2 Ben Cotton 2019-08-13 18:53:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.


Note You need to log in before you can comment on or make changes to this bug.