I’ve updated a Fedora Workstation to v39 (and v40 yesterday). During the upgrade process I did not see any errors. Booting also gave me no problems, but when I tried to login my system froze for about 1 minute, and then send me back to the login screen. When I reboot my system and select a different kernel version (5.2.17-300.fc30.x86_64) I could succesfully login, but I can’t login using the latest installed kernel (5.3.11-300.fc31.x86_64).
Now this is the first time I noticed that my system hasn’t updated my kernel in a loooong time. I assumed that when I updated/upgraded my system it would automatically update my kernel as well, but aparently something is broken.
Anyone got some ideas on how I can:
Repair dnf so it automatically updates the kernel properly?
How much free space do your root and boot partitions have? If you have been upgrading since Fedora 30 your partitions may be too small.
There are ways to “lock” or “protect” specific packages and also ways to limit the number of kernel versions that are installed. Is it possible you used the version-lock plugin or added a file in /etc/dnf/protected.d?
It is helpful if you provide the output from inxi -Fzxx and df -lH so we have a full picture of your hardware platform.
You might want to try booting the Live USB to check that your system can run Fedora 40.
I have to ask, is this an honest mistake ? You mentioned Fedora 39 > Fedora 40 but the kernels you are listing are from Fedora 30 and Fedora 31 respectively
I have to ask, is this an honest mistake ? You mentioned Fedora 39 > Fedora 40 but the kernels you are listing are from Fedora 30 and Fedora 31 respectively
Hi hammerhead corvette, yes, the kernels are from Fedora 30 and 31. I’ve never noticed that the kernels were never updated, so apparently something went wrong years ago…
The reason to try this is so we can see if the kernel will update with a distro-sync command from dnf. Please try it and report back with feedback. If not we would need to try other things to see what is blocking the kernel from updating.
Please post the output of lsblk -f
That output from df -lh seems to indicate this machine is booting in legacy mode and may not have the required BIOS boot partition for doing so with the newer fedora versions. Lsblk would provide that info.
If that is the case then it would probably be best to do a new clean reinstall so the partitions are properly configured for the newer kernels (and maybe even switch over to UEFI booting)
when a filesystem is nearly full, rotating disks need to use a lot of head movement to put data in empty spaces. This increases the chances that an
older disk will fail
linux filesystems can optimize disk layout to improve performance. When a disk is nearly full (90% is a common threshold), those optmizations no longer work, so disk access slows
Shuttle BIOS Download version 2.06 says: “Caution 1: This BIOS only for Motherboard V2.0” but you appear to have V1.0.