Display Manager (sddm, lightdm,...) not starting with Nvidia driver

I have recently reinstalled Fedora 37 KDE spin due to many issues when installing the proprietary Nvidia driver.

As soon as I install the Nvidia driver and boot up the computer, sddm does not start, but only a black screen with a functional mouse curser appears. So I can not even log in properly.
Same issue with lightdm.

I have to switch to tty3 or tty4,… to log in and startx
running startx, KDE starts normally, no issue so far (except diagonal tearing on an external monitor as mentioned here: Diagonal Screen Tearing since 525.78.01 - Thinkpad P1 Gen2 T2000 - #6 by fhortner)

So I decided to completely uninstall the nvidia driver.
As soon as the Nvidia driver is uninstalled, SDDM works again as expected.

As soon as the Nvidia driver is installed again, SDDM also does not work anymore.

I already tried to add

xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto

to /etc/sddm/Xsetup
without any effect

nvidia-bug-report ran from tty3 before startx was executed
nvidia-bug-report.log.gz (140.9 KB)

When loging in on tty3, I can restart sddm via

sudo systemctl restart sddm

or

sudo systemctl restart lightdm

and sddm/lightdm starts on tty2.
After logging in, KDE gives me the following error:

SELinux is preventing gdb from ‘read’ accesses on the chr_file nvidiactl.

The is no issue when using nouveau driver (where I have massive diagonal screen tearing. Thus I can not run nouveau regularly).

nvidia-bug-report after starting sddm via

sudo systemctl restart sddm

on tty3

nvidia-bug-report.log.gz (167.1 KB)

The nvidia driver is loading too late, please try embedding it into the initrd. Should be like this:
https://www.suse.com/support/kb/doc/?id=000019945

Strange thing is, no issue with Fedora 36.

We checked and reinstalled F36 with Nvidia 525.89.02 - no issue with SDDM under F36

Upgrade to Fedora 37 and again SDDM does not start.

removing

nvidia-drm.modeset-1

and

initcall_blacklist=simpledrm_platform_driver_init

from the kernel parameter did the trick.
If either of both is active, display manager does not start.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.