• 1 Post
  • 21 Comments
Joined 1 year ago
cake
Cake day: October 31st, 2023

help-circle







  • You either come up with something like frog-protocols to try and actually get things done, or you can wait for Wayland devs to endlessly bikeshed. Getting some amount of harmless fragmentation on an open source project seems much better than waiting 4 years (and counting) for them to start actually working on implementing HDR.




  • I’m running Wayland. I do feel that Plasma is using my iGPU to render the desktop since it’s quite noticeable some stutters and lower performance compared to disabling the iGPU and having both monitors on my dGPU, but unfortunately I can’t really chose what gets rendered by what. On Windows, this setup works fine, I can chose Firefox to use the “power saving” or whatever and it runs on my iGPU, videos get decoded by it.

    I tried plugging my monitors on my motherboard (I have a HDMI and DP outputs) and it works as expected, everything renders on the iGPU and I’d need prime-run for my games, though this is far from ideal since I lose VRR and HDR.






  • Running endeavourOS with a 3080 and Plasma since 5.25 (on 6.1.2 now). Never ran x11 and I don’t intend to ever again. My experience is mixed, so to say. There are a few things keeping me on Windows but (very) slowly I’m getting there.

    About HDR. I didn’t need to do anything extra to get it enabled on my desktop, simply toggling it on settings works.=, and I can also get mpv to work with some tweaks so I can watch films. On games I would need gamescope to run it, but that comes with a set of issues like not having Steam Overlay and Input, so for HDR games I run them on gamescope without overlay, and every other game I just run them normally. I also have a lengthy writeup on trying to get gamescope to run with the Steam overlay, but ultimately it’s one or the other right now.

    On NVIDIA drivers, for me the 555 and explicit sync patches have made things worse. I never had issues with things flickering on 550 except for Electron apps, which would flicker and have awful input lag, but that’s easily fixed by setting ELECTRON_OZONE_PLATFORM_HINT=wayland on my /etc/environment. The issue with 555 drivers is that there are some VRAM leaks happening. They fill ridiculously fast, even just dragging a window will make kwin use 2GB of VRAM. Since there is no shared VRAM at all on NVIDIA Linux, as soon as I hit my 10GB cap, Xwayland will crash along my game and Steam, and sometimes my desktop too. On 550, I would only get framedrops for a while. I should also note that the proprietary and open drivers have no difference at all for me, and enabling or disabling GSP firmware also has no difference.

    Lastly, VRR. It will not work at all if you have more than one monitor connected and enabled on your NVIDIA card. A workaround if you have a second GPU (or your CPU’s iGPU) is to plug your extra monitors there, and then VRR will work on your main screen. A second option would be to disable your extra monitors anytime you would play a game, but that’s not ideal at all.


  • I’m using a 3080 under Plasma, and I thought 555 was doing great, since I could finally use electron apps without input lag or flickers. I didn’t bother much with gaming since VRR does’t work if the NVIDIA GPU has more than one display enabled on it (you can use a second GPU or an iGPU to workaround that). I decided to give it a go anyways, wrote a script that turns off my second screen when I open a game and enables it again when it closes.

    Unfortunately, 555 was unusable for me. After a short while, Xwayland would crash and either Steam and the game would instantly close or my entire system would freeze, requiring a reboot. I thought this was an issue with Steam, so after some extensive log collection, I opened an issue on their GitHub and shortly after a dev analysed them and told me that my issue was likely due to explicit sync, and asked me to downgrade to a pre-explicit sync driver.

    I went back to 550.90 and my crashes stopped completely. It also stopped a coredump spam of glsdisplay by Steam, and also fixed a power draw bug in which my GPU would never go below 100W, even on idle. I never had issues with games flickering previously, and I still don’t have it now, and I was able to fix the electron apps flicker and input lag by setting ELECTRON_OZONE_PLATFORM_HINT=wayland on my env, so for now I’m sticking to 550.

    I also opened a bug report on NVIDIA’s forums and I’m waiting for any input.





  • From my experience using Plasma 6+ and a NVIDIA card, I keep HDR on on my main display (Odyssey Neo G7).

    No issues with washed out colours on the desktop, everything looks fine

    I can watch HDR videos using the included Haruna player or MPV.

    Firefox has no HDR support outside Mac OS, so no HDR on YouTube.

    For games, it depends. Some games can detect HDR and work fine, but for most I have to use gamescope, which in itself brings some issues like not having the Steam overlay, games freezing randomly or just having terrible performance due to niceness (everything has a workaround though, but that requires some tinkering). Check my comments about the issues and workarounds

    For game scope running HDR, there’s a lot of people and guides telling you to use countless flags that don’t really do anything at all. The best thing to do is to read its documentation. I use the following flags as startup parameters on my Steam games:

    gamemoderun gamescope  -W 3840 -H 2160 -r 165 --hdr-enabled --hdr-itm-enable --hdr-itm-sdr-nits 300 -f -e --mangoapp -- %command%
    

    gamemoderun just enables game-mode, which can bring some small performance improvements.

    -W -H -r flags are to determine resolution and desired refresh rate. You might be able to omit those flags but I have had some issues with that.

    --hdr-enabled is the only flag needed to get HDR working. Nothing else. (except from enabling it on your DE)

    --hdr-itm-enable --hdr-itm-sdr-nits are for inverse tone mapping for non HDR games, it’s the same as Windows Auto HDR.

    -f is full-screen, but to be fair I don’t think this one is doing anything, but I need to test better.

    -e is to enable Steam integration, which should be the overlay and input, but its broken (there’s a workaround, check the last comment made by me there)

    --mangoapp is to run mangohud, this flag is preferred over running mangohud before %command%. It’s partially broken this way because it does not dispaly the GPU or gamemode info. Running it as mangohud works 100% fine but apparently there are some issues with it that are beyond my knowledge.