This bug was fixed in the package u-boot-menu - 4.0.2ubuntu5~20.04.1
---------------
u-boot-menu (4.0.2ubuntu5~20.04.1) focal; urgency=medium
* SRU changes from hirsute to enable booting on the HiFive Unmatched
LP: #1925267 LP: #1923162
u-boot-menu (4.0.2ubuntu5) hirsute; urgency=medium
* Go back to generating fdtdir option in extlinux.conf, instead patch
u-boot qemu-riscv64_smode target to not process or load fdtdir
option. Currently the dtb for riscv64 unmatched board in kernel &
u-boot are _unmatched_ meaning u-boot must use its dtb, and kernel
must use its dtb. Hence fdtdir option in extlinux.conf is
required. LP: #1925267 LP: #1923162
u-boot-menu (4.0.2ubuntu4) hirsute; urgency=medium
* Revert "Add support for ubuntu kernels location of device trees." as
it breaks booting riscv64 images with qemu, as the qemu in-ram dtb
should be used not the one from disk. LP: #1923162
u-boot-menu (4.0.2ubuntu3) hirsute; urgency=medium
* Add support for ubuntu kernels location of device trees.
u-boot-menu (4.0.2ubuntu2) hirsute; urgency=medium
* Make default U_BOOT_PARAMETERS to be "ro earlycon". If one is using
embedded boards, most likely they want verbosity.
u-boot-menu (4.0.2ubuntu1) hirsute; urgency=medium
* u-boot-update: use PRETTY_NAME from os-release as menu label.
u-boot-menu (4.0.2) unstable; urgency=medium
[ Vagrant Cascadian ]
* install example script for syncing .dtb files
for systems with a split /boot partition
* fix comment handling in in /etc/fstab
[ Jonas Smedegaard ]
* declare compliance with Debian Policy 4.5.0
* use debhelper compatibility level 13 (not 10);
build-depend on debhelper-compat (not debhelper)
* copyright: extend coverage
-- William 'jawn-smith' Wilson <william.wil...@canonical.com> Thu, 24
Jun 2021 16:04:00 -0500
** Changed in: u-boot-menu (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in u-boot-menu package in Ubuntu:
Fix Released
Status in linux-riscv source package in Focal:
Invalid
Status in u-boot source package in Focal:
Fix Released
Status in u-boot-menu source package in Focal:
Fix Released
Status in linux-riscv source package in Hirsute:
Invalid
Status in u-boot source package in Hirsute:
Confirmed
Status in u-boot-menu source package in Hirsute:
Fix Released
Bug description:
[Impact]
* u-boot may crash when attempting to boot extlinux.conf which
specifies fdtdir; the given u-boot config doesn't specify a dtb
filename to load; autodetection tries to make one up using $soc &
$board variables; and if one or both of them are not set (as it is the
case for qemu) it would crash. Fix this crash by doing validation /
checking when quering for $soc & $board variables in autodetectionn.
[Test Plan]
* Use qemu & uboot produced by the build that fixes this bug report
properly and attempt to boot hirsute's riscv64+unmatched image.
* It should boot correctly without a crash / qemu backtrace.
[Where problems could occur]
* This patch is bein upstreamed. If one is using external uboot (i.e.
provided by some other vendor) it may still crash when trying to boot
Ubuntu's riscv64 rootfs or cloud image.
[Other Info]
* Patch is being reviewed upstream
https://lists.denx.de/pipermail/u-boot/2021-May/449176.html
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
