OK, this is actually due to the changes between u-boot-menu 4.0.1ubuntu0.1 and 4.0.2ubuntu5~20.04.1. The relevant difference is that the menu entry now has `fdtdir /lib/firmware/5.8.0-29-generic/device-tree/` (or similar) when it previously didn't load a device tree at all.
I successfully worked around this by adding the following to `/etc/default/u-boot`:
# XXX cjwatson 2021-08-24: Revert to old (nonexistent) default, since using
# the device tree in /lib/firmware/ results in an image that fails to boot.
# See https://bugs.launchpad.net/bugs/1940984.
U_BOOT_FDT_DIR="/usr/lib/linux-image-"
OK, this is actually due to the changes between u-boot-menu 4.0.1ubuntu0.1 and 4.0.2ubuntu5~ 20.04.1. The relevant difference is that the menu entry now has `fdtdir /lib/firmware/ 5.8.0-29- generic/ device- tree/` (or similar) when it previously didn't load a device tree at all.
I successfully worked around this by adding the following to `/etc/default/ u-boot` :
# XXX cjwatson 2021-08-24: Revert to old (nonexistent) default, since using /bugs.launchpad .net/bugs/ 1940984. FDT_DIR= "/usr/lib/ linux-image- "
# the device tree in /lib/firmware/ results in an image that fails to boot.
# See https:/
U_BOOT_