So the issue around providing fdtdir was that qemu did not know what fdt
file to attempt loading, and hence was failing to boot.
Now that we dropped fdtdir in extlinux.conf, all riscv64 boards need to
use preboot to pick up fdt from the .itb. This was already the case on
unleashed and smode, but not on unmatched.
Add USE_PREBOOT config option to unmatched too, thus bringing it inline
with unleashed & qemu.
** Changed in: u-boot (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: u-boot (Ubuntu)
Importance: Low => Critical
** Changed in: u-boot (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv package in Ubuntu:
Invalid
Status in u-boot package in Ubuntu:
Confirmed
Status in u-boot-menu package in Ubuntu:
Fix Released
Bug description:
When booting v5.11 based riscv unmatched image in qemu with uboot, it
fails to boot.
When booting v5.11 based riscv unmatched kernel+initrd directly, it
boots fine.
Somehow, it seems that u-boot fails to correctly load & start v5.11
kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
