The image for the StarFive VisionFive and the Nezha boards will be available in 22.04.1: in order to be able to boot using UEFI, we need flash-kernel to install the DTBs to the right location for GRUB to load, so we need to add those boards to the flash-kernel database.
[Test Plan]
I tested the version that built here [1] on the VisionFive board, and flash-kernel worked correctly:
ubuntu@ubuntu:~$ sudo dpkg -i flash-kernel_3.104ubuntu10~22.04.1ubuntu1~ppa0_riscv64.deb
Selecting previously unselected package flash-kernel.
(Reading database ... 94352 files and directories currently installed.)
Preparing to unpack flash-kernel_3.104ubuntu10~22.04.1ubuntu1~ppa0_riscv64.deb ...
Unpacking flash-kernel (3.104ubuntu10~22.04.1ubuntu1~ppa0) ...
Setting up flash-kernel (3.104ubuntu10~22.04.1ubuntu1~ppa0) ...
Installing new version of config file /etc/flash-kernel/bootscript/bootscr.uboot-generic ...
Using DTB: starfive/jh7100-starfive-visionfive-v1.dtb
Installing /lib/firmware/5.17.0-1001-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.17.0-1001-starfive/starfive/jh7100-starfive-visionfive-v1.dtb
Taking backup of jh7100-starfive-visionfive-v1.dtb.
Installing new jh7100-starfive-visionfive-v1.dtb.
flash-kernel: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.140ubuntu13) ...
update-initramfs: Generating /boot/initrd.img-5.17.0-1001-starfive
Using DTB: starfive/jh7100-starfive-visionfive-v1.dtb
Installing /lib/firmware/5.17.0-1001-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.17.0-1001-starfive/starfive/jh7100-starfive-visionfive-v1.dtb
Taking backup of jh7100-starfive-visionfive-v1.dtb.
Installing new jh7100-starfive-visionfive-v1.dtb.
Installing /lib/firmware/5.17.0-1001-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.17.0-1001-starfive/starfive/jh7100-starfive-visionfive-v1.dtb
Taking backup of jh7100-starfive-visionfive-v1.dtb.
Installing new jh7100-starfive-visionfive-v1.dtb.
System running in EFI mode, skipping.
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for flash-kernel (3.104ubuntu10~22.04.1ubuntu1~ppa0) ...
Using DTB: starfive/jh7100-starfive-visionfive-v1.dtb
Installing /lib/firmware/5.17.0-1001-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.17.0-1001-starfive/starfive/jh7100-starfive-visionfive-v1.dtb
Taking backup of jh7100-starfive-visionfive-v1.dtb.
Installing new jh7100-starfive-visionfive-v1.dtb.
System running in EFI mode, skipping.
The changes are board-specific so it should not alter the behaviour on other boards and unfortunately, I tried flash-kernel on a non-working kernel as the kernel team is still working on it, but the changes are straightforward enough.
[Other Info]
I added support for the LicheeRV board although not officially supported, but as it works well with our current kernel, we'd better have it available.
Note that I think we can drop the ~22.04.1 suffix and move to 3.104ubuntu11 as @waveform has just uploaded 3.106ubuntu1 into kinetic.
[Impact]
The image for the StarFive VisionFive and the Nezha boards will be available in 22.04.1: in order to be able to boot using UEFI, we need flash-kernel to install the DTBs to the right location for GRUB to load, so we need to add those boards to the flash-kernel database.
[Test Plan]
I tested the version that built here [1] on the VisionFive board, and flash-kernel worked correctly:
ubuntu@ubuntu:~$ sudo dpkg -i flash-kernel_ 3.104ubuntu10~ 22.04.1ubuntu1~ ppa0_riscv64. deb 3.104ubuntu10~ 22.04.1ubuntu1~ ppa0_riscv64. deb ... 22.04.1ubuntu1~ ppa0) ... 22.04.1ubuntu1~ ppa0) ... kernel/ bootscript/ bootscr. uboot-generic ... jh7100- starfive- visionfive- v1.dtb 5.17.0- 1001-starfive/ device- tree/starfive/ jh7100- starfive- visionfive- v1.dtb into /boot/dtbs/ 5.17.0- 1001-starfive/ starfive/ jh7100- starfive- visionfive- v1.dtb starfive- visionfive- v1.dtb. starfive- visionfive- v1.dtb. img-5.17. 0-1001- starfive jh7100- starfive- visionfive- v1.dtb 5.17.0- 1001-starfive/ device- tree/starfive/ jh7100- starfive- visionfive- v1.dtb into /boot/dtbs/ 5.17.0- 1001-starfive/ starfive/ jh7100- starfive- visionfive- v1.dtb starfive- visionfive- v1.dtb. starfive- visionfive- v1.dtb. 5.17.0- 1001-starfive/ device- tree/starfive/ jh7100- starfive- visionfive- v1.dtb into /boot/dtbs/ 5.17.0- 1001-starfive/ starfive/ jh7100- starfive- visionfive- v1.dtb starfive- visionfive- v1.dtb. starfive- visionfive- v1.dtb. 22.04.1ubuntu1~ ppa0) ... jh7100- starfive- visionfive- v1.dtb 5.17.0- 1001-starfive/ device- tree/starfive/ jh7100- starfive- visionfive- v1.dtb into /boot/dtbs/ 5.17.0- 1001-starfive/ starfive/ jh7100- starfive- visionfive- v1.dtb starfive- visionfive- v1.dtb. starfive- visionfive- v1.dtb.
Selecting previously unselected package flash-kernel.
(Reading database ... 94352 files and directories currently installed.)
Preparing to unpack flash-kernel_
Unpacking flash-kernel (3.104ubuntu10~
Setting up flash-kernel (3.104ubuntu10~
Installing new version of config file /etc/flash-
Using DTB: starfive/
Installing /lib/firmware/
Taking backup of jh7100-
Installing new jh7100-
flash-kernel: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.140ubuntu13) ...
update-initramfs: Generating /boot/initrd.
Using DTB: starfive/
Installing /lib/firmware/
Taking backup of jh7100-
Installing new jh7100-
Installing /lib/firmware/
Taking backup of jh7100-
Installing new jh7100-
System running in EFI mode, skipping.
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for flash-kernel (3.104ubuntu10~
Using DTB: starfive/
Installing /lib/firmware/
Taking backup of jh7100-
Installing new jh7100-
System running in EFI mode, skipping.
[1] https:/ /launchpad. net/~alexghiti/ +archive/ ubuntu/ distro/ +sourcepub/ 13687767/ +listing- archive- extra
[Where problems could occur]
The changes are board-specific so it should not alter the behaviour on other boards and unfortunately, I tried flash-kernel on a non-working kernel as the kernel team is still working on it, but the changes are straightforward enough.
[Other Info]
I added support for the LicheeRV board although not officially supported, but as it works well with our current kernel, we'd better have it available.
Note that I think we can drop the ~22.04.1 suffix and move to 3.104ubuntu11 as @waveform has just uploaded 3.106ubuntu1 into kinetic.