Don’t hold your breath just yet, it’s a step in the right direction but it’s far from being fully Wayland ready. I think the driver will only be fully ready some time after explicit sync protocol lands in Wayland (see https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90)
“hey here’s news. Maybe. I can’t actually tell you. It’s just what I was told. This hasn’t been relevant to me since it once was. But here’s a blog post about it. I like cheese.”
Really weird article. A bunch of snarky comments from the author that add nothing to the conversation. “It’s been a decade since I touched an Nvidia card, so I’m just giving you the info I read in a changeling. Couldn’t tell you if it was true or not, so fuck you!”
I am also not a fan of this website, but NVIDIA proprietary drivers are notoriously bad especially with Wayland, so I was thinking that people might find it useful and upgrade their drivers.
I found CS:GO 2 stopped working after upgrade to driver v545 from v535. Anyone else noticed the same?
Known bug, NVIDIA says they are working on patching it by the next minor release:
https://forums.developer.nvidia.com/t/cs2-stuck-on-valve-logo-on-startup-545-beta-branch/269778/21
My desktop would crash back to login screen after playing mass effect legendary edition. After exiting the game, if the desktop idle for a while, the moment the automatic screen off kick in, the CPU fan would whirl and if I wiggle the mouse, the desktop would immediately crash back to the login screen. Not sure whose fault it is, nvidia 545, EA, wayland or gnome.
I use an Nvidia laptop, and none of the issues I have with Wayland are from the GPU.
