Quoting Vagrant Cascadian (2025-04-13 05:42:01) > On 2025-04-12, Johannes Schauer Marin Rodrigues wrote: > > $ apt-cache policy linux-image-arm64 > > linux-image-arm64: > > Installed: 6.12.19-1+reform20250322T135019Z > > Candidate: 6.12.22-1+reform20250411T222458Z > ... > > $ sudo apt full-upgrade > ... > > Removing linux-headers-6.12.16-mnt-reform-arm64 > > (6.12.16-1+reform20250219T175041Z) ... > ... > > flash-kernel: A higher version (6.12.19-mnt-reform-arm64) is still > > installed, no reflashing required. > ... > > Setting up linux-image-6.12.22-mnt-reform-arm64 > > (6.12.22-1+reform20250411T222458Z) ... > ... > > Installing > > /usr/lib/linux-image-6.12.22-mnt-reform-arm64/amlogic/meson-g12b-bananapi-cm4-mnt-reform2.dtb > > into > > /boot/dtbs/6.12.22-mnt-reform-arm64/amlogic/meson-g12b-bananapi-cm4-mnt-reform2.dtb > ... > > Setting up flash-kernel (3.109+reform1) ... > > So, at this point, you had 6.12.19 and 6.12.22 installed, 6.12.16 was > removed ... and flash-kernel was just updated ... without re-running the > flash-kernel scripts for 6.12.22 ... although the "Installing > /usr/lib/linux-image-6.12.22...reform.dtb" was from (the older?) > flash-kernel, no?
Oh wait, is this maybe tripping up flash-kernel? The "Installing
/usr/lib/linux-image-6.12.22...reform.dtb" messages come from the kernel hook
script of the reform-tools package (also in Debian main). That hook script
copies the dtbs of MNT platforms into /boot/dtbs/. This is necessary so that:
- when you move your /boot to a different platform, it will already have the
required dtbs in /boot
- making the /boot partition bit-by-bit reproducible across system images for
all the MNT SoMs
Is it possible that flash-kernel gets confused that there are already files in
/boot/dtbs/ that it did not install itself?
> > $ uname -a
> > Linux kodi 6.12.19-mnt-reform-arm64 #1 SMP Debian
> > 6.12.19-1+reform20250322T135019Z (2025-03-22) aarch64 GNU/Linux
>
> And because flash-kernel was not run for 6.12.22, you end up booted to
> 6.12.19?
Yes.
> Presuming this isn't some bizarre fluke, then this bug is likely present
> in most versions of flash-kernel, as that code has not been touched for
> at least a 2-5 years...
>
> I vaguely recall a bug or merge request coming from Ubuntu that might be
> related...
I will try to reproduce this issue later using Debian kernels. My hunch is,
that the problem is that a new kernel version got installed at the same time
that flash-kernel got upgraded. Because at the time that 6.12.22 is installed,
flash-kernel should have been run but instead we see this in the log:
flash-kernel: deferring update (trigger activated)
And then the only other flash-kernel related message is:
Setting up flash-kernel (3.109+reform1)
So maybe this is about the order of triggers? Instead of "deferring update",
flash-kernel should've been run at the point of "Setting up
linux-image-6.12.22", no?
Thanks!
cheers, josch
signature.asc
Description: signature
