this post was submitted on 08 Aug 2023
26 points (96.4% liked)

Linux Gaming

16072 readers
33 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS
 

Title, I can't switch to Wayland because of nVidia (and because I love Awesome WM).

all 26 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 1 year ago (3 children)

X11 doesn't limit it, but you will want to enable "Force composition pipeline" to prevent screen tearing. nvidia and Wayland work together btw. It's not a match made in heaven but they do work.

[–] [email protected] 5 points 1 year ago

It’s simply not worth it. I used Wayland for a couple years but ended up switching back to X11 on nVidia hardware.

[–] [email protected] 3 points 1 year ago

It does work, but its just really glitchy and unstable. Idk how many times Ive woke my pc from sleep and my cursor was just a giant square of gibberish pixels. Or the fact that night light still does not work on GNOME + Wayland because the proprietary driver does not support GAMMA_LUT (this issue has been open for years btw)

[–] UkaszGra 3 points 1 year ago

I think forcing pipeline enables vsync or something because there is noticeable input delay when playing on 60hz screen.

[–] [email protected] 4 points 1 year ago (2 children)

Why can't you have Wayland with Nvidia?

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)
  1. I love my AwesomeWM setup. Unless someone completely rewrites it, it will never work with Wayland (as far as I have read the gh issues).

  2. I need this PC to "just work" and I have seen a lot of problems with Wayland and Nvidia drivers, top-quality gaming is a secondary on this one so X11 has been the choice.
    Though I am aware stuff is getting better, should probably try it anyway

[–] [email protected] 4 points 1 year ago* (last edited 1 year ago)

Thank you everyone, was rather sure that variable refresh rates of different monitors were a hard problem for X11.

So, in nvidia-settings I made my 120Hz one the primary and set the refresh rate from auto to the highest for both monitors (120, 60)

The only difference I noticed was that easyeffects window is now completely unreadable, somehow the text and frames bleeds out/blurs and only gets sharp when hovered with mouse but still buggy. Force-compositon-pipeline did not help there.
Will have to diagnose tomorrow.

[–] [email protected] 4 points 1 year ago

Short answer: yes.

Long answer: yyyyyyyyeeeeeeesssssssssss...

[–] [email protected] 2 points 1 year ago

No. I have a 144Hz monitor and a 60Hz monitor and both work at their maximum frame rate.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

No, you can force it to run both monitors at the highest refresh rate, but this can cause tearing on the lower refresh rate monitors. From what I remember, you can choose the monitor to sync to in the Nvidia X settings.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Edit: here's the relevant commit that addresses this (I think).

No. I can't remember what the default behaviour is now. But that isn't true anymore. Source: I'm currently on X11 and my 144 Hz works next to my 75 Hz one with nvidia.

[–] [email protected] 2 points 1 year ago (1 children)

Are you sure your are running nvidias drivers? Not the generic ones?

[–] [email protected] 3 points 1 year ago

Yeah pretty sure, nvtop, nvidia-settings etc

[–] [email protected] 1 points 1 year ago

no but gsync is broken