GRUB is responsible for loading the initrd into memory, so it is possible that this is a GRUB regression. Also, this message is new to me:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
So maybe this is related to a new GRUB initrd loading method?
To test that, I grabbed focal's grubnetaa64.efi[*] and retested. This actually worked, and contains no "LINUX_EFI_INITRD_MEDIA_GUID" messages in the stub:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...
[ 0.000000] Booting Linux on physical CPU 0x0000120000 [0x413fd0c1]
GRUB is responsible for loading the initrd into memory, so it is possible that this is a GRUB regression. Also, this message is new to me: INITRD_ MEDIA_GUID device path
EFI stub: Loaded initrd from LINUX_EFI_
So maybe this is related to a new GRUB initrd loading method?
To test that, I grabbed focal's grubnetaa64.efi[*] and retested. This actually worked, and contains no "LINUX_ EFI_INITRD_ MEDIA_GUID" messages in the stub:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services...
[ 0.000000] Booting Linux on physical CPU 0x0000120000 [0x413fd0c1]
So, adding a grub task.
[*] http:// ports.ubuntu. com/ubuntu- ports/dists/ focal/main/ uefi/grub2- arm64/2. 04-1ubuntu26/ grubnetaa64. efi.signed