[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: arm-efi: Problems with new boot method in 2.04 on Beaglebone Black
From: |
Kristian Amlie |
Subject: |
Re: arm-efi: Problems with new boot method in 2.04 on Beaglebone Black |
Date: |
Mon, 17 Feb 2020 14:58:09 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
On 05/02/2020 09:58, Kristian Amlie wrote:
> I'm having trouble using the GRUB arm-efi bootloader to boot Beaglebone
> Black. It used to work on 2.02, but no longer works on 2.04. Bisecting
> led me to commit d0c070179d4d, which switched the arm-efi bootloader to
> boot the kernel via the EFI stub instead of jumping into the image.
>
> I'm using U-Boot as the UEFI provider.
>
> Has anyone else tried this with Beaglebone Black? Any reason why this
> boot mode would produce different results?
Answering to myself, so maybe others can benefit: I found that this was
due to a bug in U-Boot, the UEFI provider. It was broken in this U-Boot
commit [1] and restored in this U-Boot commit [2]. The range of U-Boot
versions that don't work is v2018.09 - v2019.07. I only tested with GRUB
2.04, but it is working just fine outside that range of U-Boot UEFI
providers.
[1]
https://gitlab.denx.de/u-boot/u-boot/commit/a39f39cdd8be5cd3e7a8b696a463b621e3d827e0
[2]
https://gitlab.denx.de/u-boot/u-boot/commit/24a238f7633cbebcc00b810d0ac1608233a81fbf
--
Kristian
signature.asc
Description: OpenPGP digital signature