On 2022-12-28, Vagrant Cascadian wrote: > The odroid-c2 fails to boot syslinux/extlinux style menus (e.g. those > produced by u-boot-menu) or boot.scr as of upstream 2022.07-rc1. The > commit triggering the issue has been identified as: > > a9bf024b2933bba0e23038892970a18b72dfaeb4 > efi_loader: disk: a helper function to create efi_disk objects from > udevice > > Workarounds I've heard are to disable EFI support for that board, or to > boot using EFI rather than boot scripts or syslinux/extlinux style > menus. > > I will also want to get confirmation if other amlogic boards are > affected...
The currently supported amlogic platforms are: # Neil Armstrong <narmstr...@baylibre.com> u-boot-amlogic_platforms += khadas-vim # Neil Armstrong <narmstr...@baylibre.com> u-boot-amlogic_platforms += khadas-vim2 # Frederic Danis <frederic.da...@collabora.com> u-boot-amlogic_platforms += libretech-cc # Neil Armstrong <narmstr...@baylibre.com> u-boot-amlogic_platforms += nanopi-k2 # Vagrant Cascadian <vagr...@debian.org> u-boot-amlogic_platforms += odroid-c2 # Reco <b...@enotuniq.net> u-boot-amlogic_platforms += odroid-n2 Please test if the current versions from Debian unstable (2022.10*) and experimental (2023.01-rc*) are affected by this issue... and if there are other issues for Debian bookworm/testing (2022.04*). This is part of what has been blocking u-boot from migrating to testing. I do not see (m)any records of tests for most of these platforms at: https://wiki.debian.org/U-boot/Status live well, vagrant
signature.asc
Description: PGP signature
