# HDR + Wayland + Nvidia - Black Screen on Login

**URL:** <https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974>\
**Category:** Plasma\
**Created:** [April 15, 2024, 3:52am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974 "2024-04-15T03:52:26Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![pr0927](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pr0927/32/91049_2.png) [@pr0927](https://forum.endeavouros.com/u/pr0927)\
**Post date:** [April 15, 2024, 3:52am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/1 "2024-04-15T03:52:26Z")

</div>

Hi all, been using KDE Plasma 6 on Wayland. I have a system with an Nvidia GPU. Previously, I had issues even logging into the system with a higher-than-60Hz refresh rate, seen here:

> [@Wayland + Nvidia - No Signal Black Screen on Login](https://forum.endeavouros.com/t/wayland-nvidia-no-signal-black-screen-on-login/51794):
>
> Hi all, a while ago I had started my Linux journey (in a more serious way, on my main PC) with EndeavourOS. I had a great time with it, but kept running into system breakages as a relative noob by installing unstable updates and throwing caution to the wind with the AUR. I could also never get Wayland to work, in spite of my best efforts. What I mean by this is - I’d switch to Wayland on the login screen, and after logging in, I’d be greeted with a black screen and eventual “no signal detected…

A fix was found - if not permanent, at least a solid temporary one:

> [@Wayland + Nvidia - No Signal Black Screen on Login](https://forum.endeavouros.com/t/wayland-nvidia-no-signal-black-screen-on-login/51794/93):
>
> For systemd-boot: If you have an nvidia card then you should only need to apply changes to: /etc/kernel/cmdline sudo nano /etc/kernel/cmdline Add these to the line of text: nvidia-drm.modeset=1 nvidia-drm.fbdev=1 Hold ctrl and tap x . Select Yes to save changed buffer. You can write the text using \_ or - . Both will work. Some add: initcall\_blacklist=simpledrm\_platform\_driver\_init But the above should not be necessary Don’t forget to: sudo reinstall-kernels After editing. For Grub: …

Everything’s been working fine since…unless I enable HDR.

At first, I didn’t realize there was even a problem - I enabled HDR, tried to watch some HDR content, then had to depart the house. I had left my system on. On returning, I came back to my two non-HDR side monitors lit, but no response from mouse/keyboard, and my main (HDR) monitor not lighting up - it remained dark.

I used the “REISUB” method and rebooted, thankfully that worked. On reboot, it showed the login screen - on login…black screen, just like before.

Everything had been working fine for weeks until I enabled HDR. I did some digging, and found this:

> [@Black screen after enabling HDR on Wayland](https://forum.endeavouros.com/t/black-screen-after-enabling-hdr-on-wayland/52025):
>
> Hello there! I just updated my install and to my pleasant surprise Plasma 6 is now out and I’m defaulted to Wayland. All seemed good, but my monitor’s settings were forgotten. I open display settings, set the resolution and scale, and seeing the option I decide to give HDR a go on one of my two monitors. Instant black screen no signal. I wait for it to reverted, and it doesn’t seem to. I rebooted, logged back in, and immediately it’s all black again. I unplugged the HDR enabled monitor and stil…

I was able to log in to an X11 session, and followed the instructions in that thread to edit **$HOME/.config/kwinoutputconfig.json** and disable HDR for my display. I saw in that thread that the OP found the settings wouldn’t stick after a reboot.

So, I tried a log out and log in (to a Wayland session) - no dice, got the black screen.

I rebooted, got back in X11, and used the solution in the thread - edit the file, then make it immutable, then reboot.

It worked! I then disabled the immutability of that file, enabled HDR, and then disabled it. Then I rebooted.

All good now. So why the thread? Because the problem isn’t solved of course - can’t use HDR on KDE Plasma 6 Wayland, at least with an Nvidia GPU.

Does anyone know of a permanent fix to make this work? Or will the “explicit sync” update in the future possibly fix all this?

---

<div class="post-metadata">

**Author:** ![pr0927](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pr0927/32/91049_2.png) [@pr0927](https://forum.endeavouros.com/u/pr0927)\
**Post date:** [April 26, 2024, 3:39am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/2 "2024-04-26T03:39:03Z")

</div>

Damn, guess nobody else having this problem, or nobody else knows the solution?

---

<div class="post-metadata">

**Author:** ![rabcor](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@rabcor](https://forum.endeavouros.com/u/rabcor)\
**Post date:** [April 26, 2024, 5:08am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/3 "2024-04-26T05:08:10Z")

</div>

I’m not sure if wayland even supports HDR. But with nvidia on wayland you were always gonna be fighting an uphill battle.

[https://wiki.archlinux.org/title/HDR\_monitor\_support](https://wiki.archlinux.org/title/HDR_monitor_support)

---

<div class="post-metadata">

**Author:** ![pr0927](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pr0927/32/91049_2.png) [@pr0927](https://forum.endeavouros.com/u/pr0927)\
**Post date:** [April 26, 2024, 5:51am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/4 "2024-04-26T05:51:03Z")

</div>

Wayland on Plasma 6 added HDR - it’s not on X11. Here’s the settings, for example:

 ![image](https://forum.endeavouros.com/uploads/default/original/3X/e/2/e20afb7f6f54f6a45a54b512002fe7fc450b1019.png)

---

<div class="post-metadata">

**Author:** ![rabcor](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@rabcor](https://forum.endeavouros.com/u/rabcor)\
**Post date:** [April 26, 2024, 6:12am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/5 "2024-04-26T06:12:12Z")

</div>

Well, it is experimental support, maybe just doesn’t work with nvidia. You may wanna try asking around in the kde community, you’re likelier to find answers there, using nvidia on wayland is already a niche thing, most people avoid it. using nvidia and using hdr on wayland at the sametime? I don’t think there are many at all, but if there are you’re likelier to find them there than here I’m afraid.

---

<div class="post-metadata">

**Author:** ![pr0927](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pr0927/32/91049_2.png) [@pr0927](https://forum.endeavouros.com/u/pr0927)\
**Post date:** [April 26, 2024, 6:42am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/6 "2024-04-26T06:42:11Z")

</div>

Hmm, I’ll check out KDE community then yeah.

That said, recently The Linux Experiment did a video on what GPUs people use - not super-scientific, but IIRC Nvidia came out on top, and KDE had a very big showing as well. I think the increase in gaming on Linux has been a driver for that (it’s what pushed me to Linux - now I use Windows only for the few games which I can’t run in ideal fashion on Linux).

---

<div class="post-metadata">

**Author:** ![rabcor](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/0ea827/32.png) [@rabcor](https://forum.endeavouros.com/u/rabcor)\
**Post date:** [April 26, 2024, 7:43am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/7 "2024-04-26T07:43:41Z")

</div>

That makes sense yeah, but did it define if it was kde wayland or kde x11 they were using?

---

<div class="post-metadata">

**Author:** ![pr0927](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pr0927/32/91049_2.png) [@pr0927](https://forum.endeavouros.com/u/pr0927)\
**Post date:** [April 26, 2024, 8:32am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/8 "2024-04-26T08:32:53Z")

</div>

To my recollection it was X11 or not mentioned - I think Wayland is still just too new for mass adoption.

Operating a bit off memory here so I might be wrong, haha.

---

<div class="post-metadata">

**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\
**Post date:** [April 26, 2024, 8:33am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/9 "2024-04-26T08:33:29Z")

</div>

> Another big one is the [merging](https://invent.kde.org/plasma/kwin/-/merge_requests/4589) of initial HDR support for gaming (which I previously reported on), that has also now been accepted, using a cut-down version of the upstream protocol that isn’t yet finished so that the Plasma team can let people test and play with the HDR implementation for gaming.

_Source:_

> **[KDE Plasma 6 goes Wayland by default, initial HDR gaming support](https://www.gamingonlinux.com/2023/11/kde-plasma-6-goes-wayland-by-default-initial-hdr-gaming-support/)**
>
> In another update on the progress of the upcoming KDE Plasma 6 desktop environment release, there's some fun details from Nate Graham.

> In the Plasma Wayland session, there’s now preliminary support for playing HDR-capable games when using an HDR-capable screen! (Xaver Hugl, [link](https://invent.kde.org/plasma/kwin/-/merge_requests/4589))

> **[Add support for playing HDR games (!4589) · Merge requests · Plasma / KWin ·...](https://invent.kde.org/plasma/kwin/-/merge_requests/4589)**
>
> This uses a protocol that's cut down from the upstream proposal, so that we can merge it quickly and use it for...

Looks still a bit like WIP, and we all know even Wayland support in general on Plasma 6 is still causing some issues all over the place.

---

<div class="post-metadata">

**Author:** ![pr0927](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pr0927/32/91049_2.png) [@pr0927](https://forum.endeavouros.com/u/pr0927)\
**Post date:** [April 26, 2024, 9:31am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/10 "2024-04-26T09:31:14Z")

</div>

Oh OK, I didn’t realize just how preliminary. Guess I will sit tight, haha. Thanks!

---

<div class="post-metadata">

**Author:** ![Vetrix](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/v/76d3ee/32.png) [@Vetrix](https://forum.endeavouros.com/u/Vetrix)\
**Post date:** [June 30, 2024, 11:22am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/11 "2024-06-30T11:22:41Z")

</div>

today after upgrading my system and my nvidia drivers to 555.58 i got the same issue but i have HDR disabled.

I was trying HDR before but was getting the same error like you but after restoring my system to a point of yesterday and just updating it broke

---

<div class="post-metadata">

**Author:** ![Vetrix](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/v/76d3ee/32.png) [@Vetrix](https://forum.endeavouros.com/u/Vetrix)\
**Post date:** [June 30, 2024, 6:00pm UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/12 "2024-06-30T18:00:52Z")

</div>

I was able to login into Wayland without my HDR Monitor and when turning it on everything froze.  
I as a lot of errors of such error in the logs.

```auto
wayland 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible

```

What worked for me was deleting **$HOME/.config/kwinoutputconfig.json**. making it immutable was sadly not working for me.  
Maybe this can help anyone also getting the problem

---

<div class="post-metadata">

**Author:** ![kmoschcau](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/kmoschcau/32/97957_2.png) [@kmoschcau](https://forum.endeavouros.com/u/kmoschcau)\
**Post date:** [July 14, 2024, 8:33am UTC](https://forum.endeavouros.com/t/hdr-wayland-nvidia-black-screen-on-login/53974/13 "2024-07-14T08:33:30Z")

</div>

Hi, just FYI [here](https://bugs.kde.org/show_bug.cgi?id=488941) is the corresponding KDE bug thread. I believe that discussion is the furthest along.
