[Bug 1998513] Re: SRU provide RISCV_EFI_BOOT_PROTOCOL in Focal

[Heinrich Schuchardt]

u-boot-qemu package tested successfully
with the following observations which are not a change from 2021.01+dfsg-3ubuntu0~20.04.5:

Booting https://cdimage.ubuntu.com/ubuntu-server/focal/daily-
preinstalled/current/focal-preinstalled-server-riscv64+unmatched.img.xz
(2022-10-31 07:04) on QEMU failed with

Retrieving file: /boot/initrd.img-5.15.0-1022-generic
118495394 bytes read in 15 ms (7.4 GiB/s)
Retrieving file: /boot/vmlinuz-5.15.0-1022-generic
29512704 bytes read in 4 ms (6.9 GiB/s)
append: root=LABEL=cloudimg-rootfs ro earlycon single
Retrieving file: /lib/firmware/5.15.0-1022-generic/device-tree/qemu-riscv.dtb
Failed to load '/lib/firmware/5.15.0-1022-generic/device-tree/qemu-riscv.dtb'
Skipping l0r for failure retrieving fdt
SCRIPT FAILED: continuing...
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk virtio-blk#8...

due to this entry in /boot/extlinux/extlinux.conf:

fdtdir /lib/firmware/5.15.0-1022-generic/device-tree/

Booting manually worked with the following commands:

=> virtio scan
=> load virtio 0:1 $kernel_addr_r /boot/vmlinuz-5.15.0-1022-generic    
29512704 bytes read in 3 ms (9.2 GiB/s)
=> load virtio 0:1 $ramdisk_addr_r /boot/initrd.img-5.15.0-1022-generic
118495394 bytes read in 14 ms (7.9 GiB/s)
=> setenv bootargs root=/dev/vda1
=> booti $kernel_addr_r $ramdisk_addr_r:$filesize $fdtcontroladdr

https://cdimage.ubuntu.com/releases/kinetic/release/ubuntu-22.10-preinstalled-
server-riscv64+unmatched.img.xz booted in the same way:

=> load virtio 0:1 $kernel_addr_r /boot/vmlinuz-5.19.0-1004-generic
31656960 bytes read in 3 ms (9.8 GiB/s)
=> load virtio 0:1 $ramdisk_addr_r /boot/initrd.img-5.19.0-1004-generic
111792546 bytes read in 13 ms (8 GiB/s)
=> setenv bootargs root=/dev/vda1
=> booti $kernel_addr_r $ramdisk_addr_r:$filesize $fdtcontroladdr
Bad Linux RISCV Image magic!

We should consider moving images for QEMU/Unmatched to using GRUB.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/1998513

Title:
  SRU provide RISCV_EFI_BOOT_PROTOCOL in Focal

Status in u-boot package in Ubuntu:
  In Progress
Status in u-boot source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Booting a current kernel (5.19) with U-Boot via UEFI fails in Focal
  because the RISCV_EFI_BOOT_PROTOCOL is not provided.

  The RISCV_EFI_BOOT_PROTOCOL is used to indicate the boot hart ID. In
  previous releases of the kernel the boot hart ID was read from the
  /chosen/boot-hartid property in the device-tree.

  Add the missing protocol.

  U-Boot in Focal cannot add the boot-hartid property if the the device-
  tree does not contain a chosen node. This might lead to failure to
  boot a 5.15 kernel. Add a patch fixing this.

  [ Test Plan ]

   * Try booting the SiFive HiFive Unmatched board and QEMU using the
  preinstalled server image for Focal.

   * Use the Kinetic server install image to install Ubuntu on the
  SiFive HiFive Unmatched board and on QEMU and try to boot with the
  SRUed U-Boot.

  [ Where problems could occur ]

   * The two applied patches affect only RISC-V (if there is no syntax
  error).

   * Booting the Focal Fossa 5.15 kernel would fail if the /chosen/boot-
  hartid were not provided.

  [ Other Info ]
   
  n/a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1998513/+subscriptions