I have recently upgraded to F44 and through updates I see that kernel 7.0.4 is installed. When rebooting I see a short error message at the start-up screen and the kernel 6.19.14-300 is booted.
I see no other error messages and I cannot find other error messages after boot is completed.
Does anyone have an idea of how to proceed to find out why the new kernel does not start?
Truls
Boot whatever kernel works for you and post the output from ls -al /boot
Hi Steve,
here is the output.
root@P16v:~# ls -al /boot
total 543384
dr-xr-xr-x. 6 root root 4096 mai 11 21:14 .
dr-xr-xr-x. 19 root root 4096 mai 11 20:12 ..
-rw-r--r--. 1 root root 297817 april 23 02:00 config-6.19.14-300.fc44.x86_64
-rw-r--r--. 1 root root 299048 mai 7 02:00 config-7.0.4-200.fc44.x86_64
drwx------. 4 root root 4096 jan. 1 1970 efi
drwx------. 3 root root 4096 mai 11 21:12 grub2
-rw-------. 1 root root 284706949 feb. 22 22:13 initramfs-0-rescue-43235803879843339b08b2d075c3a4f9.img
-rw-------. 1 root root 191687532 mai 7 20:46 initramfs-6.19.14-300.fc44.x86_64.img
drwxr-xr-x. 3 root root 4096 jan. 3 2025 loader
drwx------. 2 root root 16384 jan. 3 2025 lost+found
lrwxrwxrwx. 1 root root 47 mai 7 20:45 symvers-6.19.14-300.fc44.x86_64.xz -> /lib/modules/6.19.14-300.fc44.x86_64/symvers.xz
lrwxrwxrwx. 1 root root 45 mai 11 21:08 symvers-7.0.4-200.fc44.x86_64.xz -> /lib/modules/7.0.4-200.fc44.x86_64/symvers.xz
-rw-r--r--. 1 root root 11602905 april 23 02:00 System.map-6.19.14-300.fc44.x86_64
-rw-r--r--. 1 root root 11687510 mai 7 02:00 System.map-7.0.4-200.fc44.x86_64
-rwxr-xr-x. 1 root root 18909224 feb. 22 22:12 vmlinuz-0-rescue-43235803879843339b08b2d075c3a4f9
-rwxr-xr-x. 1 root root 18479464 april 23 02:00 vmlinuz-6.19.14-300.fc44.x86_64
-rw-r--r--. 1 root root 162 april 23 02:00 .vmlinuz-6.19.14-300.fc44.x86_64.hmac
-rwxr-xr-x. 1 root root 18684264 mai 7 02:00 vmlinuz-7.0.4-200.fc44.x86_64
-rw-r--r--. 1 root root 160 mai 7 02:00 .vmlinuz-7.0.4-200.fc44.x86_64.hmac
You do not have an initial ram filesystem built; note there is no initramfs for version 7.0.4 - only for version 6.19.14.
This is why the boot fails immediately.
Rebuilding one can be achieved with sudo dracut --kver 7.0.4-200.fc44.x86_64 but the more important thing to ascertain is why it’s not there in the first place. The usual suspect is lack of space, so please post the output from df -h /boot.
If there is sufficient space then we can run dracut manually to recreate the ram disk, but if not it’ll just fail again so we’ll need to come up with an alternative plan.
Hi again,
a few upgrades back I ran out of /boot or /boot/efi space. My solution has been to delete the oldest kernel before installing a new one.
I do not know why this happened, but I have read somewhere that something called “bignumbers” or thelike came in at some point. There seems to be solution to this, but I have so far not found it.
Anyway, here is the output. Two kernel versions installed.
df -h /boot
Filesystem Size Used Avail Use% Mounted on
/dev/nvme0n1p2 943M 534M 345M 61% /boot
Truls
That looks like you should have enough space (345 MB) to create the 7.0.4 initramfs based on the size of the 6.19 initramfs you have installed).
Feel free to run that dracut command and after it’s finished, take a look in /boot again to make sure the initramfs-7.0.4 file is there alongside the 6.19 version. If so, then you can reboot and you should be able to start the 7.0.4 kernel up without any error messages.
If you get any errors from dracut, feel free to post them here.
Hi Flynn,
this made my kernel 7.0.4 work, but system still defaults to 6.19.14 if I don’t specifically choose 7.0.4 from the boot menu.
grub2-editenv list
saved_entry=43235803879843339b08b2d075c3a4f9-6.19.14-300.fc44.x86_64
menu_auto_hide=1
boot_success=1
boot_indeterminate=0
tmp_saved_entry=43235803879843339b08b2d075c3a4f9-7.0.4-200.fc44.x86_64
Do you know how switch the two?
Truls
I think I found out myself. The boot loader was set to load the kernel index as 1, while the latest is indexed as 0.
grubby --set-default-index=0
Did the trick.
Thanks for all help
Truls