[Bug 2141432] Re: New machines: Xunlong Orange Pi RV, SpacemiT K3 Pico-ITX, ultrarisc, dp1000
Launchpad Bug Tracker
2141432 at bugs.launchpad.net
Mon Mar 23 06:45:46 UTC 2026
This bug was fixed in the package flash-kernel - 3.110ubuntu2
---------------
flash-kernel (3.110ubuntu2) resolute; urgency=medium
[ Dave Jones ]
* Split out piboot-try package (LP: #2138618)
- flash-kernel-piboot is now a transitional package pointing to piboot-try
- All the delta specific to the Raspberry Pi is stripped out
* Removed changes from prior merge:
- Add support for Raspberry Pi 2, 3, 3+, CM3, CM3+, and 4 using a unified
bootscript (replaces upstream's entries)
- Update pi bootscript to support all flash-kernel vars, including
calculated devtype and partition for future USB boot support
- Add entry for Raspberry Pi 3A+
- Add entry for Raspberry Pi CM4
- Add entry for Raspberry Pi 400
- Import UC20 updates to the rpi bootscript from the snappy-dev/image
PPA
- Add Kernel-Flavors check to Raspberry Pi entries
- Support "raspi" kernel flavor
- Drop the "systemd.gpt_auto=0 rd.systemd.unit=basic.target" values from
the snapd_standard_params, which have not been needed since pre-GA of
UC20 and were removed in pc gadget on 20th April 2020. (LP: 1933093)
- Add "pi" value for the "Method" field which copies all dtbs and overlays
to the boot partition and provides defaults for the boot paths of the
kernel, initrd, and u-boot script.
- This fixes upgrades to support the Pi 4 on Bionic
- Permit initrd to be missing in flash-kernel
- Make U-boot optional in the "pi" method. From Groovy onwards, U-Boot
will be an option in the boot chain but not activated by default. For
the time being, the U-Boot-Script-Name will remain in the Pi entries,
but this commit permits it to be blank in future.
- Copy the Pi's bootloader firmware. At present, the Pi's bootloader
firmware is being copied to the boot partition by the postinst of the
linux-firmware-raspi2 package. However, flash-kernel should be
responsible for copying *everything* necessary to boot the Linux
kernel, hence this responsibility should be transferred to flash-
kernel.
- Ensure tests work independently of sort implementation
- Add pattern matching for machines
- A requirement has come up to permit a simple form of pattern matching
(specifically shell-style globbing) in the Machine field of the
database. This commit implements this via a "case" match.
- Add minor board revisions to db/all.db
- Added entries for the Pi 4B rev 1.5, and moved CM4 and 400 models to
their own entries for the sake of clarity
- Added note in db/all.db above Pi entries about "incorrect" DTB-Id (LP:
1928314)
- Install u-boot binaries in addition to u-boot scripts for the Pi
- Copy overlay_map.dtb into overlays/ sub-directory instead of the root of
the boot partition (LP: 1918110)
- Include overlays/README in the files copied by Method: pi
- Use generic-revision catch-alls for each model rather than relying on a
single Pi catch-all to avoid a confusing selection of "the one DTB" for
a given board (even though all other DTBs will still be copied anyway)
(LP: 2038087)
- Add missing Pi Zero 2W entry
- Add missing Pi 5B entry
- Add raspi-realtime kernel flavor to bcm2711 and bcm2712 based Pi boards
(LP: 2051960)
- db/all.db: Fix Raspberry Pi 2 entry for noble. Here we can assume it is
definitely the 64-bit revision (1.2) board, but this change must not be
backported earlier than noble where this assumption does not hold (LP:
2060856)
- db/all.db: add CM5 entry (LP: 2086774)
- db/all.db: Add entry for Raspberry Pi 500 (LP: 2092216)
- db/all.db: Add CM5 Lite to flash-kernel database
- Implement an A/B boot mechanism for the Raspberry Pi. This adds the new
flash-kernel-piboot package, which contains the new piboot-try-reboot
and piboot-try-validate services
- Enable the hardware watchdog during migration of the boot configuration
- Report failure of new boot assets in motd
- Show --help if no options specified to piboot-try
- Ensure validation is done before motd displays
- Do not execute piboot-try when method != pi-try
[ Heinrich Schuchardt ]
* db/all.db: Add new machines (LP: #2141432):
- Xunlong Orange Pi RV
- SpacemiT K3 Pico-ITX
- ultrarisc,dp1000
-- Dave Jones <dave.jones at canonical.com> Wed, 11 Feb 2026 21:59:28
+0000
** Changed in: flash-kernel (Ubuntu Resolute)
Status: New => Fix Released
--
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/2141432
Title:
New machines: Xunlong Orange Pi RV, SpacemiT K3 Pico-ITX,
ultrarisc,dp1000
Status in flash-kernel package in Ubuntu:
Fix Released
Status in flash-kernel source package in Noble:
New
Status in flash-kernel source package in Questing:
New
Status in flash-kernel source package in Resolute:
Fix Released
Bug description:
[ Impact ]
The following new entries in /usr/share/flash-kernel/db/all.db are
needed to support the boards:
Machine: Xunlong Orange Pi RV
Kernel-Flavors: any
DTB-Id: starfive/jh7110-orangepi-rv.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools
Machine: SpacemiT K3 Pico-ITX
Kernel-Flavors: any
DTB-Id: spacemit/k3-pico-itx.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.uboot-generic
Required-Packages: u-boot-tools
Machine: ultrarisc,dp1000
Kernel-Flavors: any
DTB-Id: ultrarisc/dp1000-titan-v1.dtb
The first two relate to upstream kernel entries. The UltraRISC entry
relates to a vendor kernel.
[ Test Plan ]
Run `sudo flash-kernel` on the boards an check that the correct
device-tree is copied.
[ Where problems could occur ]
The database could be corrupted when editing, resulting in a failure
to install device-trees.
[ Other Info ]
n/a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2141432/+subscriptions
More information about the foundations-bugs
mailing list