https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c14 --- Comment #14 from Stefan Seyfried <seife@novell.slipkontur.de> --- updated the second machine today to u-boot-rpiarm64-2023.01-2.1.aarch64 from tumbleweed-oss repo, last changelog * Fri Jan 27 2023 Guillaume GARDET <guillaume.gardet@opensuse.org> Patch queue updated from https://github.com/openSUSE/u-boot.git tumbleweed-2023.01 Prefer upstream solution to fix boo#1207562 * Patches dropped: 0017-rpi-fix-boot-from-USB-on-RPi4-boo-1.patch * Patches added: 0017-Backport-https-patchwork.ozlabs.org.patch And it still fails. I only could take a picture of the error message, so typing in here (if this continues, I definitely will have to set up a serial-to-syslog-device for my raspis ;-)) ------- Scanning usb 0:1 BootOrder not defined EFI boot manager: Cannot load any image Found EFI removable media binary efi/boot/bootaa64.efi ** Reading file would overwrite reserved memory ** Failed to load 'efi/boot/bootaa64.efi' No UEFI binary known at 0x00080000 EFI LOAD FILED: continuing... BOOTP broadcast 1 ------ I'd try to boot the machine simply via bootp/tftp, but these machines are in the guest network and thus I cannot easily provide them with tftp ;-) -- You are receiving this mail because: You are on the CC list for the bug.