Virkkunen

My two cents, I could say the same as the author. My Windows work laptop most of the times cannot wake up from sleep (you know, opening the lid after it's closed) so I have to force a restart. There's a 50% or less chance that Bluetooth and WiFi won't work at all (they won't be displayed on Windows, like it's not even a feature) after I turn the laptop on, so most of my pre-work morning is restarting the laptop until it's working as intended. It's the third laptop I got from them, they're different models but they're all HP, and they all had problems. The Macs and the same HP laptops running Linux have none of these issues.

At this point we should just rename it to Lenny

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.

That... Makes sense, really. And how would you do on about it? Just switching the cable to the motherboard IO? No need to use stuff like optimus?

Sadly I will have to live with this issue since my 5900x has no iGPU, but I do plan to upgrade to a 7800x3d

The input lag and flickering on Electron apps was fixed with the explicit sync drivers.

VRR does not work if you have a NVIDIA card and more than one monitor enabled. If you disable extra monitors it'll work, but that's hardly a workaround (and it's one of the main reasons I'm still on Windows).

I'm also getting a lot of xwayland crashes while playing or simply when trying to drag a window, those crashes freeze my entire PC and I have to reboot.

To be fair, most, if not all of my issues preventing me from fully moving to Linux seem to be fixed by using an AMD card, but I'm not in the market for a new card (I have a 3080) nor do I want to lose DLSS, which is a game changer to me.

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.

You can install beta NVIDIA drivers with Optimus on A laptop and you'll be able to see the fat Tux!