Yesterday I did a dnf update and it installed some kernel-cores, like kernel-rpi-16k-core-6.12.103 and kernel-rpi-4k-6.12.103 (I didn’t remember it installed kernel-rpi at the same time though) then it did not boot any more after rebooting. the green light turned back to red after less than 10 seconds
Is it possible to rescue it?
Do you know what kernel version you were running prior to dnf update?
kernel-rpi-16k-6.12.90 I believe
Well I was wrong, it was 6.12.80-12.el10.altarch.aarch64+16k
can you mount the storage and share a directory listing of /boot and /boot/efi? You should be able to temporarily hardcode the previous kernel in config.txt and get it to boot again.
Thanks! I managed to get the Pi booting again by mounting the SD card on another Linux machine.
I think I have identified what happened. This installation dates back to the earlier Rocky Linux 10 Raspberry Pi image, when the RPi kernel was still based on 6.6. It appears that my system never had the newer kernel-rpi / kernel-rpi-16k meta packages installed. Instead, it only has the underlying packages:
kernel-rpi-16k-core
kernel-rpi-16k-modules-core
kernel-rpi-4k-core
kernel-rpi-4k-modules-core
After the recent update, kernel-rpi-16k-core-6.12.103-1.el10.altarch.aarch64 was installed. The update also replaced /boot/efi/kernel_2712.img with the 6.12.103 16K kernel. However, /boot/efi/initramfs_2712 was not regenerated and was still the initramfs for:
6.12.80-12.el10.altarch.aarch64+16k
I verified this with lsinitrd. So the Pi was trying to boot a 6.12.103 kernel with a 6.12.80 initramfs, which appears to be what caused the boot failure. I mounted both the root partition and EFI partition on another Linux machine. The old 6.12.80 kernel was still available at/lib/modules/6.12.80-12.el10.altarch.aarch64+16k/vmlinuz. I backed up the new kernel_2712.img and copied the old kernel back
cp /boot/efi/kernel_2712.img /boot/efi/kernel_2712.img.6.12.103.bak
cp /lib/modules/6.12.80-12.el10.altarch.aarch64+16k/vmlinuz \
/boot/efi/kernel_2712.img
Then it booted successfully. So I think I might have to manually install the kernel-rpi-16k(and 4k if necessary)?
Well I found another issue with the current 6.12.103-1.el10.altarch packages. Both kernel meta-packages currently have unsatisfied dependencies:
# dnf install kernel-rpi-16k
nothing provides kernel-16k-modules-uname-r = 6.12.103-1.el10.altarch.aarch64+16k
needed by kernel-rpi-16k-6.12.103-1.el10.altarch.aarch64
# dnf install kernel-rpi
nothing provides kernel-core-uname-r = 6.12.103-1.el10.altarch.aarch64
nothing provides kernel-modules-core-uname-r = 6.12.103-1.el10.altarch.aarch64
nothing provides kernel-modules-uname-r = 6.12.103-1.el10.altarch.aarch64
So neither kernel-rpi nor kernel-rpi-16k can currently be installed from altarch-rockyrpi.
I’ll keep the Pi running on 6.12.80-12.el10.altarch.aarch64+16k for now and wait for some possible fixes 
So by checking dnf history what it installed yesterday were
kernel-rpi-16k-core-6.12.103...
kernel-rpi-16k-modules-core-6.12.103...
yet the kernel-rpi-16k was asking for dependencies of other names so it wasn’t installed
Thank you for the details. Happy its working. We’ve not run into this issue, but with that said, i have several Pi 5s and will test as/when able.
--Bryan
Found a test rig.
Here’s what rpm -qa |grep kernel-rpi show’s on my working system.
kernel-rpi-4k-core-6.12.80-11.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.80-11.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.12.80-11.el10.altarch.aarch64
kernel-rpi-16k-core-6.12.80-11.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-16k-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-16k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-firmware-6.12.103-1.el10.altarch.aarch64
I’d be curious to know what that command shows on your unit.
I also show my initramfs wasnt regenerated, but it didnt cause any issues in my case. Aug 21 would be around when we released 103 (if i had to guess without looking)
-rwx------. 1 root root 29M Jun 8 09:50 initramfs_2712
-rwx------. 1 root root 29M Nov 16 2025 initramfs8
-rwx------. 1 root root 8.9M Aug 21 19:37 kernel_2712.img
-rwx------. 1 root root 8.9M Aug 21 19:37 kernel8.img
So what `rpm -qa |grep kernel-rpi` returens are
kernel-rpi-4k-modules-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-4k-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-16k-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-16k-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-16k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-firmware-6.12.103-1.el10.altarch.aarch64
So the problem is that kernel-rpi-16k-modules-6.12.103-1.el10.altarch.aarch64is not provided (just checked Rocky Linux Repository) while
dnf repoquery --requires kernel-rpi-16k
kernel-16k-core-uname-r = 6.12.103-1.el10.altarch.aarch64+16k
kernel-16k-modules-core-uname-r = 6.12.103-1.el10.altarch.aarch64+16k
kernel-16k-modules-uname-r = 6.12.103-1.el10.altarch.aarch64+16k
So it cannot be installed (wasn’t even asking to install when dnf update). then the boot will fail. As for initramfs, it is automatically generated when installing kernel-rpi-16k-core-6.12.103-1.el10.altarch.aarch64(and failed)
dnf history info has these at the end
1 '/lib/modules/6.12.103-1.el10.altarch.aarch64+4k/vmlinuz' -> '/boot/efi/kernel8.img'
2 dracut[F]: /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+4k/modules.dep is missing. Did you run depmod?
3 '/lib/modules/6.12.103-1.el10.altarch.aarch64+16k/vmlinuz' -> '/boot/efi/kernel_2712.img'
4 dracut[F]: /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+16k/modules.dep is missing. Did you run depmod?
I had the same issue. System patched last night and would not boot. I did what was posted and now. I"m booting. Something is up with 103 kernel.
root@svpl07:~# rpm -qa | grep -i kernel-rpi
kernel-rpi-16k-modules-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-16k-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.80-12.el10.altarch.aarch64
kernel-rpi-16k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-4k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-firmware-6.12.103-1.el10.altarch.aarch64
So when will the kernel-rpi-*k-modulespackages be added?
I must be missing something?
HI,
I can confirm same issue after upgrading and latter reboot the rpi5.
I was able to reproduce on a fresh install from the image Rocky-10-SBC-RaspberryPi-10.0-20250610.2.aarch64.raw.xz
before update:
# rpm -qa|grep kernel
kernel-rpi-4k-modules-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-4k-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-16k-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-firmware-6.6.77-8.el10.altarch.aarch64
after:
# rpm -qa |grep kernel|sort
kernel-core-6.12.0-211.58.1.el10_2.aarch64
kernel-modules-6.12.0-211.58.1.el10_2.aarch64
kernel-modules-core-6.12.0-211.58.1.el10_2.aarch64
kernel-modules-extra-6.12.0-211.58.1.el10_2.aarch64
kernel-rpi-16k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-16k-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-16k-modules-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-4k-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-4k-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.12.103-1.el10.altarch.aarch64
kernel-rpi-4k-modules-core-6.6.77-8.el10.altarch.aarch64
kernel-rpi-firmware-6.12.103-1.el10.altarch.aarch64
ll /boot/efi/{initramfs,kernel}*
-rwx------. 1 root root 23599723 10 jun 2025 initramfs_2712
-rwx------. 1 root root 23599824 10 jun 2025 initramfs8
-rwx------. 1 root root 9318642 25 sep 02:32 kernel_2712.img
-rwx------. 1 root root 9314269 25 sep 02:32 kernel8.img
I see the messages log around installation saying
Sep 25 02:32:09 builderpi5 dracut[12258]: *** Hardlinking files done ***
Sep 25 02:32:09 builderpi5 dracut[12258]: *** Store current command line parameters ***
Sep 25 02:32:09 builderpi5 dracut[12258]: *** Creating image file '/boot/initramfs-0-rescue-09e0299cae8648ca8dc61d3d5a8f85e0.img' ***
Sep 25 02:32:09 builderpi5 dracut[12258]: Using auto-determined compression method 'pigz'
Sep 25 02:32:27 builderpi5 dracut[12258]: *** Creating initramfs image file '/boot/initramfs-0-rescue-09e0299cae8648ca8dc61d3d5a8f85e0.img' done ***
Sep 25 02:32:29 builderpi5 dracut[21409]: dracut-107-9.el10_2
Sep 25 02:32:30 builderpi5 dracut[21412]: Executing: /usr/bin/dracut -f /boot/efi/initramfs_2712 6.12.103-1.el10.altarch.aarch64+16k
Sep 25 02:32:30 builderpi5 dracut[21412]: /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+16k/modules.dep is missing. Did you run depmod?
Sep 25 02:32:30 builderpi5 dracut[21563]: dracut-107-9.el10_2
Sep 25 02:32:30 builderpi5 dracut[21566]: Executing: /usr/bin/dracut -f /boot/efi/initramfs8 6.12.103-1.el10.altarch.aarch64+4k
Sep 25 02:32:31 builderpi5 dracut[21566]: /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+4k/modules.dep is missing. Did you run depmod?
manually running them does regenerate the initramfs
/usr/bin/dracut -f /boot/efi/initramfs_2712 6.12.103-1.el10.altarch.aarch64+16k
/usr/bin/dracut -f /boot/efi/initramfs8 6.12.103-1.el10.altarch.aarch64+4k
and later shows
ll /boot/efi/{initramfs,kernel}*
-rwx------. 1 root root 30219231 25 sep 03:02 /boot/efi/initramfs_2712
-rwx------. 1 root root 30223350 25 sep 03:06 /boot/efi/initramfs8
-rwx------. 1 root root 9318642 25 sep 02:32 /boot/efi/kernel_2712.img
-rwx------. 1 root root 9314269 25 sep 02:32 /boot/efi/kernel8.img
after that I was able to reboot
looking at dep files there is a race condition between dracut and depmod, dep files are 1 second younger than the moment dracut run…
[root@builderpi5 rocky]# ll /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+4k/modules.dep
-rw-r--r--. 1 root root 212260 25 sep 02:32 /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+4k/modules.dep
[root@builderpi5 rocky]# ll /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+16k/modules.dep
-rw-r--r--. 1 root root 212260 25 sep 02:32 /usr/lib/modules/6.12.103-1.el10.altarch.aarch64+16k/modules.dep
see bug 13894
Of course you were.
I thought I said it very clearly.
The problem is that in https://dl.rockylinux.org/pub/sig/10/altarch/aarch64/altarch-rockyrpi/Packages/k/ there is only kernel-rpi-**-modules-core but no kernel-rpi-**-modules, that’s why the kernel-rpi cannot be installed. dnf updateinstalled kernel-rpi-**-core which automatically tried to build that initramfs and will fail of course. After that a reboot will definitely result in a boot failure.
I check that page almost every single day waiting for it to be fixed
Being rude wont get you an answer quicker.
What makes you think that subpackage should exist? Its not in the spec (that i can see) and on my known working systems, its not installed as previously shared.
Have you tried a fresh install with fresh storage by chance?
I have a RPi 5 with RL10 pending to update a lot of packages, including the kernel 6.12.103-1.el10.altarch.
Do you know if it’s already safe to execute the update or better wait for a fix to this booting issue?
Thanks.
There is a fix a few posts above from @jppialasse so you could do that and everything would work fine.
I know, but my RPi is in a remote location, so if it don’t boot I’ll be unable to repair it.
Thanks.