$ ln -sf uInitrd-5.10.110-rockchip-rk3588 uInitrd
$ ln -sf vmlinuz-5.10.110-rockchip-rk3588 Image
Then I could boot again on the old kernel.
It looks like I simply missed the `linux-dtb-current-rockchip-rk3588` package, so I installed it:
$ apt-get install linux-dtb-current-rockchip-rk3588
Then I reinstalled the kernel so the post-install scripts redo the symbolic links for me (I didn't use `apt-get install --reinstall` because the `/boot` partition is too small for doing that):
$ apt-get remove linux-image-current-rockchip-rk3588
$ apt-get install linux-image-current-rockchip-rk3588
And it worked, before:
$ uname -a
Linux orangepi5 5.10.110-rockchip-rk3588 #trunk.0112 SMP Sat Dec 31 16:41:56 UTC 2022 aarch64 GNU/Linux
after:
$ uname -a
Linux orangepi5 6.10.6-current-rockchip-rk3588 #1 SMP PREEMPT Mon Aug 19 04:05:40 UTC 2024 aarch64 GNU/Linux
Why do the `linux-dtb-current-rockchip-rk3588` package isn't a hard-dependency of `linux-image-current-rockchip-rk3588`? That looks to be a packaging bug to me.
