Comment 2 for bug 1913468

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

booted focal riscv64 image in qemu VM.

updated to proposed, and installed the new u-boot-menu 4.0.1ubuntu0.1

upgrades to u-boot-menu did not regenerate /boot/extlinux/extlinux.conf.

as there is no kernel to update, i triggered u-boot-menu update by calling

$ sudo u-boot-update

Checking the /boot/extlinux/extlinux.conf it was updated and now has Ubuntu branding, non-quiet boot by default, and earlycon options set. root= argument is also parsed without issues. however my fstab currently doesn't have any comments either.

rebooting.

U-Boot menu
1: Ubuntu 20.04.1 LTS 5.8.0-14-generic
2: Ubuntu 20.04.1 LTS 5.8.0-14-generic (rescue target)
Enter choice: 1: Ubuntu 20.04.1 LTS 5.8.0-14-generic
Retrieving file: /boot/initrd.img-5.8.0-14-generic
157868702 bytes read in 230 ms (654.6 MiB/s)
Retrieving file: /boot/vmlinuz-5.8.0-14-generic
20092252 bytes read in 21 ms (912.4 MiB/s)
append: root=LABEL=cloudimg-rootfs ro earlycon
## Flattened Device Tree blob at ff73fa40
   Booting using the fdt blob at 0xff73fa40
   Using Device Tree in place at 00000000ff73fa40, end 00000000ff743d9d

Starting kernel ...

[ 0.000000] OF: fdt: Ignoring memory range 0x80000000 - 0x80200000
[ 0.000000] Linux version 5.8.0-14-generic (buildd@riscv64-qemu-lcy01-088) (g
cc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34)
#16~20.04.1-Ubuntu SMP Wed Jan 20 18:22:58 UTC 2021 (Ubuntu 5.8.0-14.16~20.04.1-
generic 5.8.18)
[ 0.000000] earlycon: ns16550a0 at MMIO 0x0000000010000000 (options '')
[ 0.000000] printk: bootconsole [ns16550a0] enabled
[ 0.000000] Initial ramdisk at: 0x(____ptrval____) (157872128 bytes)
[ 0.000000] Zone ranges:

Reading the above you can see that U-boot menu is now branded, and the boot is not quiet.