Black Screen after updating to 6.1.5-200.fc37 w/NVIDIA Drivers

+1 black screen before luks decryption on what should be the latest nvidia drivers. Fedora 37. Driver version 525.78.01.

+1

I too, cannot enter LUK encrypted drive. Also running Nvidia drivers. Fell back to previous instance. Hope a fix comes soon. Pinned current working deployment.

Another +1.
My installation of Fedora Kinoite 37, with kernel 6.1.5 and Nouveau driver, is getting stuck on the KDE logo after the sddm login (both with Wayland and Xorg).
With kernel 6.0.18, not problem at all.

1 Like

To keep the old kernel, you will probably want to use dnf versionlock,
https://dnf-plugins-core.readthedocs.io/en/latest/versionlock.html

If you need to find an older kernel and install it, https://fedoramagazine.org/install-kernel-koji/ is a good place to start.

1 Like

Proprietary NVIDIA drivers are broken (all branches) on Fedora Linux kernel 6.1.x due to unset CONFIG_FB_EFI config option.

RHBZ issue: 2161104 – Kernel 6.1.5 - 6.2.0.alpha is missing VESAFB+EFIFB support, breaking the NVIDIA driver

3 Likes

+1
F36 KDE spin
Kernel 6.1.5-100.fc36.x86_64
Nvidia Driver 525.78.01
LUK encrypted
X11


Sometimes I get a black screen after loading kernel. I can type my password for LUK encryption but without a prompt. I’m able to access the system.
Sometimes it’s stuck on “loading kernel 6.1.5-200” instead of the black screen. I can still type my password blindly and access the system.


While running the new kernel

  • One of my screens is disabled. I don’t know why. I have to open “Nvidia X server settings” and enable it again, I can’t do it from KDE settings. Therefore, this setting is not saved after reboot, I would have to “Save to X Configuration File” from the “Nvidia X server settings” I suppose.
1 Like

Some with this issue seem to be using an encrypted drive.
It seems the password prompt for unlocking the drive is not displayed and leaves one with the black screen.

One solution may be to simply enter the password even without the prompt then press enter and the system could unlock and continue.

There have been similar issues in the past at times. A search for “black screen” gives a lot of results and you may find a solution in one of those posts.

2 Likes

Jeff Vcomputersavvy Q&A Leader

Some with this issue seem to be using an encrypted drive.
It seems the password prompt for unlocking the drive is not displayed and leaves one with the black screen.

One solution may be to simply enter the password even without the prompt then press enter and the system could unlock and continue.

This work for me. Will have to be patient, there is no feedback, but it made it to desktop.

1 Like

Perhaps it could be fixed in 6.1.7. See https://bodhi.fedoraproject.org/updates/FEDORA-2023-fa03351c58#comment-2847312

1 Like

I have the same problem as described in the original post and my disk is encrypted. With vanilla kernel 6.1.7-250.vanilla.fc37 it appears my system is normal now.

Using a vanilla kernel is not the same as using the kernel from fedora. We are waiting for the 6.1.7 fedora kernel which seems to promise the fix.

Over on:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-0597579983

6.1.7-200-fc37 has been approved and push to stable. What is the next process that happens before it’s in the fedora-updates repository?

It still shows as testing.

This update has been pushed to testing.

[ 14 hours ago ](https://bodhi.fedoraproject.org/updates/FEDORA-2023-0597579983#comment-2852346)

This update can be pushed to stable now if the maintainer wishes

[ 14 hours ago ](https://bodhi.fedoraproject.org/updates/FEDORA-2023-0597579983#comment-2852375)

That issue is resolved for me since kernel 6.1.7 hit stable.

Issue resolved for OP in 6.1.7 stable. Good stuff. Thank you guys for all your input and thank you @computersavvy for that temporary solution, which let some of us continue to work while we waited for 6.1.7. Now we know: blank screen at encryption prompt? Type it in anyways and be patient.

2 Likes

3 posts were split to a new topic: Cannot boot 6.1 kernels

Different problem now that the new kernel landed. First I get an error message right before the Plymouth login screen stating NVIDIA kernel module missing: failing back to nouveau.

The second thing I noticed after I uninstalled the akmod and Nvidia drivers, rebooted, reinstall Nvidia drivers it downloads the kernel-headers-6.1.5-200.fc37.x86_64 instead of kernel-headers-6.1.7-200.fc37.x86_64. Is this normal? What version of the kernel-headers do any of you have?

Could TPM 2.0 and/or ‘Secure Boot’ cause this? I recently enabled both to play a game on Windows (which is the way they are trying to combat cheating), while waiting on this kernel to be pushed to stable. I turn off both TPM and secure boot, but has no effect.

1 Like