[Bug 1978923] Re: SRU flash-kernel to add support for RISC-V boards

[Alexandre Ghiti]

Installed on the VisionFive board and rebooted successfully:

ubuntu at ubuntu:~$ sudo dpkg -i flash-kernel_3.104ubuntu11_riscv64.deb 
(Reading database ... 71987 files and directories currently installed.)
Preparing to unpack flash-kernel_3.104ubuntu11_riscv64.deb ...
Unpacking flash-kernel (3.104ubuntu11) over (3.104ubuntu11) ...
Setting up flash-kernel (3.104ubuntu11) ...
Using DTB: starfive/jh7100-starfive-visionfive-v1.dtb
Installing /lib/firmware/5.17.0-1003-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.b
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-1003-starfive
Using DTB: starfive/jh7100-starfive-visionfive-v1.dtb
Installing /lib/firmware/5.17.0-1003-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.b
Taking backup of jh7100-starfive-visionfive-v1.dtb.
Installing new jh7100-starfive-visionfive-v1.dtb.
Installing /lib/firmware/5.17.0-1003-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.b
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.104ubuntu11) ...
Using DTB: starfive/jh7100-starfive-visionfive-v1.dtb
Installing /lib/firmware/5.17.0-1003-starfive/device-tree/starfive/jh7100-starfive-visionfive-v1.dtb into /boot/dtbs/5.b
Taking backup of jh7100-starfive-visionfive-v1.dtb.
Installing new jh7100-starfive-visionfive-v1.dtb.
System running in EFI mode, skipping.

And on the Nezha board with an image that was built with this version,
the image booted fine.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

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

Title:
  SRU flash-kernel to add support for RISC-V boards

Status in flash-kernel package in Ubuntu:
  New
Status in flash-kernel source package in Jammy:
  Fix Committed

Bug description:
  [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 at ubuntu:~$ sudo dpkg -i flash-kernel_3.104ubuntu11~ppa0_riscv64.deb        
  Selecting previously unselected package flash-kernel.                            
  (Reading database ... 94352 files and directories currently installed.)          
  Preparing to unpack flash-kernel_3.104ubuntu11~ppa0_riscv64.deb ...              
  Unpacking flash-kernel (3.104ubuntu11~ppa0) ...                                  
  Setting up flash-kernel (3.104ubuntu11~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.104ubuntu11~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.

  [1]
  https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13689678/+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 dropped the ~22.04.1 suffix and moved to 3.104ubuntu11 as @waveform has just uploaded 3.106ubuntu1 into kinetic (which already contains the support for those boards).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1978923/+subscriptions