Wayland dark screen in Wayland session since 50th release kernel 6.8 update when an Nvidia card provided of 550 proprietary driver are applied.
Hi - folks here would likely need some more information to help diagnose, so including your system information from the Info Center app (using the Copy Details button) would be helpful.
However, the general description given reminded me of these bugs: 481950 – Dark screen in wayland with NVIDIA GPU and 489521 – (ICC, Profile) ICC profiles too dark on KDE Wayland Nvidia 555 driver
Do either of those match what you’re experiencing?
Hi. I use an Nvidia card on my system provided of proprietary drivers. These are the specs of my system:
Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-51-generic (64-bit)
Graphics Platform: X11
Processors: 4 × AMD Athlon™ … Quad Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 1030/PCIe/SSE2
Nvidia driver: 550.120
Now every time the kernel get updates some nvidia kernel package is updated too. The operating system worked good on Wayland session up to the 49 release of the 6.8 kernel. The screen has gone black after 50 release update of the kernel unlike X11. The wayland session refuses to boot and after some attempts the operating system turns to login page.
About that reference. The issue didn’t affect any releases of the 6.8 kernel before the 50th. So the issue deals with Nvidia kernel package. Some kind of incompatibility has occurred with 550.120 Nvidia driver from the 50th releases of the 6.8 kernel that now is the 51th.
I can assume that these packages are responsible of the problem:
- nvidia-kernel-common
- nvidia-kernel-source
Ah, you meant dark as in totally black 
Sounds like it might be the issue that started this thread, then (linking to a step that has solved it for a lot of folks): CRITICAL: Black screen in Wayland after recent update - #6 by prasadmurthy
Do you think that 565 Nvidia drivers will fix the issue? I would avoid to add personal modifications to system files which could cause future conflicts.
I definitely understand not wanting to set up a “house of cards” for future updates by messing with installed system files!
However, in the case of specifying kernel module options as was described in that post, instead of modifying an existing installed file, it’s doing so by adding a file to a directory (/etc/modprobe.d/) that’s specifically designated to hold user-defined additions to the system’s base configuration.
When a future updates arrives, it shouldn’t overwrite that directory - and if the setting you’ve applied there becomes incompatible with some future version of the software, then all that’s needed is to delete that .conf file and update the initramfs as described, and it’s gone.
Not to say those things can’t cause problems sometimes, but that approach is relatively low-risk compared to ones that involve modifying files in /usr, for example.
(If there are 565 drivers that are built to be compatible with the currently in-use kernel for Neon, I suppose that could be worth a try…but I don’t have any direct experience with how 565 drivers are working on Ubuntu, so I’d take the advice of anyone who is actually using or working on that base over mine )
1 Like
many thanks. So, I will wait for 565 Nvidia drivers from official repository and if the issue persists I’ll apply the workaround as described in the discussion you notified to me.
Total noob here and would love a solution to this. I have no plasma other than the login screen. Also, my default used to be X11 and now it is Wayland, the difference?
the solution is to make the file nvidia.conf described in the link johnandmegh has posted into the folder suggested just writing options nvidia_drm fbdev=1 in this file. So run the command sudo update-initramfs -u by terminal and reboot the system.