Since kernel 6.9.5 I was only able to boot after disabling plymouth, so I was hoping for a fix in upcoming updates. Unfortunately, things got worse this morning, as I can no longer boot (even with plymouth disabled) with the 6.9.9 kernel update. The screen freezes after entering the LUKS password.
So now I have to select kernel 6.9.8 to boot my nvidia gpu rig.
The Linux kernel development process is driven by the needs of modern hardware, and older systems like yours tend to be left behind.
The issue you’re facing is a common problem with Linux kernel development: the “ABI” (Application Binary Interface) breaks between major kernel releases. This means that new kernel versions often introduce changes that make old software incompatible, while also introducing new bugs and regressions.
In your case, it’s likely that newer kernels have changed some internal interfaces or APIs that older systems like yours rely on. This can cause problems with device drivers, system libraries, or even the X11 windowing system (if you’re still using it).
So, in conclusion, there’s no compelling reason to upgrade your kernel if the newer versions are known to have issues and your system is working fine with
the current one.
Personally, I still use 6.8.7 and I blocked further updates:
$ cat /etc/dnf/dnf.conf
# see `man dnf.conf` for defaults and possible options
[main]
defaultyes=True
gpgcheck=True
installonly_limit=5
clean_requirements_on_remove=True
best=False
skip_if_unavailable=True
max_parallel_downloads=10
fastestmirror=True
keepcache=True
excludepkgs=sublime-text, chromium, chromium-common, kodi-mythtv-pvr, cppmyth, brave-browser, vivaldi-stable, \
kernel-6.9.*, kernel-core-6.9.*, kernel-headers-6.9.*, kernel-modules-6.9.*, kernel-modules-core-6.9.*, \
kernel-modules-extra-6.9.*, kernel-tools-6.9.*, kernel-tools-libs-6.9.*
Can’t help for Plymouth though, I’ve didabled it in Fedora 38.
“The Linux kernel development process is driven by the needs of modern hardware, and older systems like yours tend to be left behind.”
I don’t know why you assume my hardware is old.
My rig specs:
I also have an Intel Thinkpad that is older than this rig and I have no problem with kernel 6.9.9.
My bad. Please accept my apologies.
You probably forgot that he uses a Nvidia rig. The Linux drivers are always behind with closed source drivers. Small changes mostly need some adaptions. The community is doing a great job to keep up with the changes. Unfortunately Nvidia is the “brake on fun” (Spass Bremse, in German).
As you said, using older Kernel is a workaround but not really a solution. If you want peace wit your Linux system it is best, to use for your commercial activities, Hardware with better support for opensource systems like Linux.
Intel Thinkpad is a nice example for compatible hardware 
FWIW, I use the stable, non-free NVIDIA drivers (555.58.02) from RPM Fusion on this rig.
You need to provide enough detail to allow others with access to similar hardware to reproduce the issue.
inxi -Fzxx in a terminal (as preformatted text using the </> button from the top line of the text entry screen).journalctl --no-hostname -b <N> where <N> is the number of the most recent failed boot (e.g. N=-1 if you booted to 6.9.8 after 6.9.9 froze). Try to find some -g (grep) strings that select the relevant lines. When the nvidia driver fails, the system should fall back to nouveau, so using nvidia or nouveau as grep strings may be useful. Once you have identified lines that seem relevant to your problem, use journalctl --no-hostname -b <N> -g <string>| cat to get text with compete lines and post as pre-formatted text.5 posts were split to a new topic: Black Screen on Boot kernel 6.9.7
A post was split to a new topic: Black Screen on boot | kernel 6.9.x