Kernel not upgrading on upgrade F39 to F40

Fedora 40 upgrade from Fedora 39. Kernel goes into a loop after Mounted sys-kernel-config.mount Kernel Configuration File System

Used command line to upgrade to fc40. Has almost always worked in the past. After Kernel File System mounted, fedora icon on screen, with spinning icon. Continues to spin until powered off. Do not see a way to back off the upgrade, system will boot to fc39 kernel, but most (all?) of the other packages are fc40. fpaste shows a fc40 system with an fc39 kernel. Attempts to upgrade to a newer fc40 kernel have not cleared the problem. Any way out other than doing a live usb install? (my data is backed up).

Sure, can you check a couple of things before we go further ?

What does cat /etc/os-release && cat /etc/fedora-release return ?

Please shorten the title a bit and put the error message in the text :slight_smile:

during boot press Esc to get logs.

And if you do stuff we need the error messages to help

Added dnf-system-upgrade, f40

# cat /etc/os-release
NAME="Fedora Linux"
VERSION="40 (Workstation Edition)"
PRETTY_NAME="Fedora Linux 40 (Workstation Edition)"
VARIANT="Workstation Edition"

# cat /etc/fedora-release
Fedora release 40 (Forty)

Happy to shorten the title, how?

I tired to use escape to capture the log, but it did not stop, and then the screen went to the Fedora Icon screen and sat there. There was no visible disk action after the icon came on screen. There was no new log created for the fc40 boot. I have some of the last log messages from the boot, I videoed the screen as the messages went by.

[ 2.64493] systemd[1]: Started systemd- Journald.service - Journal Service.
[ OK ] Started systemd-juounald.srvice - Journal Service.
[ OK ] Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
[ OK ] Finished systemd-vconsole-setup.service - Virtual Console Setup
       Starting dracut-cmdline.service - dracut cmdline hook...
[ OK ] Finished dracut-cmdline.service - dracut cmdline hook.
       Starting systemd-udevd.service - Rule-based Manager for Device Events and Files...
[ OK ] Started systemd-udevd.service - Rule-based Manager for Device Events and Files.
       Starting systemd-udev-trigger.service - Coldplug All udev Devices...
[ OK ] Created slice system-modprobe.slice - Slice /system/modprobe.
            Starting modprobe@conf igfs.service - Load Kernel Module configs…
[ OK ]  Finished modprobe@conf igfs.service - Load Kernel Module configs…
[ OK ]  Finished systemd-udev-trigger.service Coldplug All udev Devices
             Mounting sys-kernel-config.mount – Kernel Configuration File System…
[ OK ]  Reached target remote-fs-pre-target – Preperation for Remote File Systems.
[ OK ]  Reached target remote-fs-target – Remote File Systems
             Starting plymouth-start-service Show Plymouth Boot Screen...
[ OK ]  Mounted sys-kernel-config.mount Kernel Configuration File System

I copied these by had from the last frame of the video. Happy to give you what you want.

Hello @drhitzs ,
It seems from your description that you are getting all of the update except the kernel!. When the boot reaches the point that you are waiting on, can you Ctrl Alt F2 to try to get a terminal login?

A look at the /boot directory shows all of the files that I expected to see there. Now if these files have the correct info, I do not know.

@fedora:~$ ls -l /boot
total 291008
-rw-r--r--. 1 root root    272188 May 25 19:00 config-6.8.11-200.fc39.x86_64
-rw-r--r--. 1 root root    272218 May 25 19:00 config-6.8.11-300.fc40.x86_64
-rw-r--r--. 1 root root    274203 Jun 15 19:00 config-6.9.5-200.fc40.x86_64
drwx------. 4 root root      4096 Dec 31  1969 efi
drwx------. 3 root root      4096 Jun 26 19:26 grub2
-rw-------. 1 root root 111722298 Oct 10  2023 initramfs-0-rescue-774d4438ce3340ab8d40eb8c24399896.img
-rw-------. 1 root root  37782334 Jun  6 16:21 initramfs-6.8.11-200.fc39.x86_64.img
-rw-------. 1 root root  29337344 Jun  9 21:10 initramfs-6.8.11-300.fc40.x86_64.img
-rw-------. 1 root root  29341805 Jun 26 14:18 initramfs-6.9.5-200.fc40.x86_64.img
drwxr-xr-x. 3 root root      4096 Oct 10  2023 loader
drwx------. 2 root root     16384 Oct 10  2023 lost+found
lrwxrwxrwx. 1 root root        46 Jun  6 16:21 symvers-6.8.11-200.fc39.x86_64.xz -> /lib/modules/6.8.11-200.fc39.x86_64/symvers.xz
lrwxrwxrwx. 1 root root        46 Jun  9 21:10 symvers-6.8.11-300.fc40.x86_64.xz -> /lib/modules/6.8.11-300.fc40.x86_64/symvers.xz
-rw-r--r--. 1 root root    163076 Jun 26 14:18 symvers-6.9.5-200.fc40.x86_64.xz
-rw-r--r--. 1 root root   9022570 May 25 19:00
-rw-r--r--. 1 root root   9017435 May 25 19:00
-rw-r--r--. 1 root root   9259086 Jun 15 19:00
-rwxr-xr-x. 1 root root  14215976 Oct 10  2023 vmlinuz-0-rescue-774d4438ce3340ab8d40eb8c24399896
-rwxr-xr-x. 1 root root  15650632 May 25 19:00 vmlinuz-6.8.11-200.fc39.x86_64
-rwxr-xr-x. 1 root root  15712072 May 25 19:00 vmlinuz-6.8.11-300.fc40.x86_64
-rwxr-xr-x. 1 root root  15894888 Jun 15 19:00 vmlinuz-6.9.5-200.fc40.x86_64

At this point, I am having hardware problems in another area. I want to suspend this action for the moment.

1 Like

I edited your codeblock and title, you are probably not yet allowed to do that.