Updated using Discover, couldn’t login after reset with kernel kernel-6.14.3-300.fc42.x86_64
. So I switched to kernel-6.14.2-300.fc42.x86_64 which boots normally.
Sometimes this happens, it is rare.
If it happens again with 6.14.4 then you can increase the number of Kernels you system will keep (default is 3).
If you want to you can file a bug at https://bugzilla.redhat.com/
It did also happen on 6.14.4. Just black screen forever. Then I reset and logged in with 6.14.2 again, just on a hunch removed nvidia driver and re-install it. Now I can boot on 6.14.4.
Same issue here on an Acer Aspire A315 with hybrid Intel + NVIDIA graphics (i5-1135G7, NVIDIA MX350). Kernel 6.14.3 and 6.14.4 both failed to boot with a black screen. Booted into 6.14.2, switched graphics mode from “integrated” to “hybrid” whith envycontrol extension, then rebooted into 6.14.4 — it worked fine. No need to reinstall the NVIDIA driver; just enabling hybrid graphics before switching kernels resolved the issue.
2 Likes
That’s nice and all, but it’s still a work around. We shouldn’t be needing to worry about fixing black screen before/after every kernel upgrade.
Why the driver of NVIDIA always makes so much wrong? Even on Windows.
Yes Nvidia driver always gives a headache. But I’m not so sure it is the Nvidia driver to blame this time. I didn’t touch the driver, just did a normal fedora update, which updated the kernel. And it broke. There was no Nvidia driver update, and it was working fine on kernel 6.14.2.
gpio: mpc8xxx: Fix wakeup source leaks on device unbind
media: chips-media: wave5: Fix gray color on screen
talk abuou driver
Upd. After the 6.14.5 kernel update, I’m facing the same issue again. The previous steps that helped with 6.14.4 no longer work. 
I tried:
sudo akmods --kernels 6.14.5-300.fc42.x86_64 --force
sudo dracut --force /boot/initramfs-6.14.5-300.fc42.x86_64.img 6.14.5-300.fc42.x86_64
disabling Secure Boot
But the result is still the same — black screen
How I solved was completely removing everything related to Nvidia and reinstalling from rpmfusion. After that, I survived a few kernel updates (for now).
I also found this solution myself two days ago (though I ended up reinstalling the system because I broke it after deleting the NVIDIA driver). And I also had to disable Secure Boot before doing that.
Same problem again with kernel 6.14.6 
Does anyone know the reason why this is happening?
Looks like I’m getting this on 6.14.6 now
When I used Fedora 41, I never had this kind of problem after a kernel update. There was only one time when the issue was caused by the NVIDIA driver itself, not the kernel. Now, with Fedora 42, it seems that the NVIDIA driver only works with the kernel version that was active at the time of installation (and with previous ones). For example, last week I reinstalled the system and installed the driver while running kernel 6.14.5 — everything worked fine. But after the system updated to 6.14.6, the NVIDIA driver no longer worked, and the system failed to boot completely. Yesterday I reinstalled Fedora again, installed the NVIDIA driver on kernel 6.14.6, and now it works again.
I’m expecting another kernel update soon, and I honestly don’t know whether the driver will survive it or not.
Looks like reinstalling Nvidia drivers worked for me on 6.14.6
1 Like
In another threads about this issue and also on Reddit, I read one more suggestion: next time a kernel update is released, update the system through the terminal instead of the GNOME Software Center, and wait about 5 minutes before rebooting. This way, the akmods kernel modules should be built properly. So that’s what I plan to do when the next update comes.
For today when i was messing with repositories (i removed from my kde discover and its dependencies - fedora-workstation repos and google-chrome) so i had to add them manually and reinstall google chrome and nvidia drivers, then didnt catch up immedietly after installing. so i rebooted as i didnt observed building of nvidia modules (from top). right after boot i saw black screen. but when i moved to tty i run top i observed that nvidia kmods are during building. so i waited. when they finished, login screen appered.
just my 2 cents.
1 Like
Oh thanks for your thoughts. It might help in the future. I didn’t think in that way.