Wayland BlackScreen On Login

General system Kernel, boot, graphics & hardware
1

I recently upgraded my system after not updating it for about 2 months

Now when logging into wayland i get a black screen on my primary monitor and a single _ on my second monitor

if i log into x11 first then into wayland my computer outputs some TTY text, stopping at
[ok] reached target Graphical Interface

in both instances if i hit the power button on my PC i get TTY output for the shutdown, so the computer isn’t “frozen”, just stuck somehow

i extracted some of my journalctl logs related to the period of time just before and after the login, this is from a fresh boot directly into wayland, so the black screens and single underscore
https://pastebin.com/s2b8K4xL

I would much rather use wayland, scaling per monitor and HDR are great, and it seems to be the future

tl;dr Im using the KDE Plasma DE

2

Welcome @Wisher! :wave: :sunglasses: :enos_flag:

I have two questions:

  1. Do you have an Nvidia GPU?
  2. Did you activate HDR in KDE?

It would be likely you can still log in with X11 without this issue.

3

When running a rolling release distribution it’s not recommended to only update once every two months, I would say the minimum would be to update once a week.

This would make me have the same question as @Bink.

But if I were to guess it sounds like an Nvidia issue where the Nvidia driver isn’t able to load so the graphical environment can’t start because of it

4

Yes to both NVIDIA gpu (RTX 3090) and HDR was enabled last the desktop was working

is there a config file somewhere i can try disabling the HDR in wayland to see if thats the issue

5

I do normally update more often, there was just some stuff going on

Yeah, im leaning towards the NVIDIA issue aswell, though i have followed the Arch Wikis steps to change the nvidia_drm.modeset and fbdev settings, took me a bit to figure them out with dracut but im pretty sure they are set correctly

though sudo cat /sys/module/nvidia_drm/parameters/fbdev emits N, not sure if that is meant to be Y or not

6

Try reinstalling your Nvidia packages and then reboot, could be that something went wrong during compiling of the new kernel module as if I remember correctly EndeavourOS uses nvidia-dkms by default.
https://discovery.endeavouros.com/nvidia/new-nvidia-driver-installer-nvidia-inst/2022/03/

7

Thank you for the suggestion, i’ll give that a shot

though a quick yay -QS nvidia shows normal looking packages, not the dkms, but i’ll go ahead and uninstall/reinstall the current packages

[wisher@wisher-endeaouros ~]$ yay -Qs nvidia
local/egl-wayland 2:1.1.14-1
    EGLStream-based Wayland external platform
local/gwe 0.15.9-1
    A system utility for controlling NVIDIA GPUs
local/lib32-libvdpau 1.5-2
    Nvidia VDPAU library
local/lib32-nvidia-utils 555.58.02-1
    NVIDIA drivers utilities (32-bit)
local/lib32-opencl-nvidia 555.58.02-1
    OpenCL implemention for NVIDIA (32-bit)
local/libvdpau 1.5-3
    Nvidia VDPAU library
local/libxnvctrl 555.58.02-1
    NVIDIA NV-CONTROL X extension
local/nvidia 555.58.02-4
    NVIDIA drivers for linux
local/nvidia-hook 1.5-2
    pacman hook for nvidia
local/nvidia-inst 24-1
    Script to setup nvidia drivers (dkms version) in EndeavourOS
local/nvidia-settings 555.58.02-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 555.58.02-1
    NVIDIA drivers utilities
local/opencl-nvidia 555.58.02-1
    OpenCL implemention for NVIDIA
8

no luck, reinstalling the nvidia package didn’t seem to change anything. Didn’t see any errors in pacmans output during the installation either

9

Try logging into an X11 session and check what your Xorg.log says, I would think you should be able to find something there since you have a similar problem with both X11 and Wayland. Which Nvidia gpu are you using and what happens when you run nvidia-smi on your system? Do you have an Xorg configuration(/etc/X11/xorg.conf) on your system, if so try renaming that file and then running nvidia-xconfig to generate a new configuration and then reboot. What happens then?

10

The issue is the result of activating HDR under Wayland, with an Nvidia GPU.

I did the same thing, have the same issue, and yet to have a working fix, other than just using X11 instead. It’s an issue echoed by other users also.

My hope is an update will fix it at some point, because manual interventions have so far failed.

1 Like
11

anyone tried to reset kwin settings?
mv ~/.config/kwinrc ~/.config/kwinrc.bak
mv ~/.config/kwinoutputconfig.json ~/.config/kwinoutputconfig.json.bak
sudo systemctl restart sddm

2 Likes
12

Editing this to disable HDR, or renaming the file as you mentioned, didn’t help in my case.

I’d not tried renaming kwinrc also. Thanks for the suggestion, I’ll try that :+1:

13

X11 is working as expected so far, its just wayland

GPU is NVIDIA RTX 3090

14

This worked!

Ofcourse if has disabled HDR, but that is more than likely the issue, now i can periodically try and turn it back on after updates!

Thank you so much for you’re help

2 Likes
15

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