Talk: Proprietary Nvidia driver shows a black screen instead of a virtual terminal or a graphical session

Ask Fedora
,
24

I am experiencing the described behaviour on f35 after performing the most recent update to kernel 5.17.11-200.fc35.x86_64 (and several other packages) in combination with the proprietary nvidia-driver (version 510.68.02-1.fc35) installed through negativo17’s repo.
The GPU inside my mobile workstation is a Quadro P1000 (GP107GL-A).

By choosing an older kernel (5.17.7-200.fc35.x86_64) through grub, luckily I still can start my system.

Then, when comparing the systemd-journals of the recent boots i get through the still working kernel, I can see that

  • for kernel 5.17.7 there are fb-related entries of :

kernel: efifb: probing for efifb
kernel: efifb: No BGRT, not showing boot graphics
kernel: efifb: framebuffer at 0x71000000, using 8100k, total 8100k
kernel: efifb: mode is 1920x1080x32, linelength=7680, pages=1
kernel: efifb: scrolling: redraw
kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
kernel: Console: switching to colour frame buffer device 240x67
kernel: fb0: EFI VGA frame buffer device

  • while with 5.17.11 this section reads:

kernel: [drm] Initialized simpledrm 1.0.0 20200625 for simple-framebuffer.0 on minor 0
kernel: Console: switching to colour frame buffer device 240x67
kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Then later, at about thei height where the journal-entries stop for kernel 5.17.11, one of the first lines that are only present on the still working kernel read

systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:nvidia_0.

which might be an indication that this is indeed related to the proprietary nvidia driver as described in one of the earlier posts.

For me, it is not an option to go back to nouveau because I too often need cuda and rawhide… well… not on my productive system please.

So in essence: the issue described seems not only limited to Fedora 36 but also seems to be affecting Fedora 35 systems. And fingers crossed that there will be a fixed driver soon.

@javierm maybe you want to consider updating the workaround mentioning staying on f35?