Nvidia X Server Settings under Wayland has no options

Hello,
Im using Wayland with my PC and missing all my adjustment from my Nvidia settings which i had made under X11.

Adjustments like Color and Filter settings, are no longer there:

Dithering: Temporal
Digital Vibrance: 36
Color Correction:
Brightness: 0
Constrast: 0,096
Gamma: 0,720

That’s my old settings from the X11 nvidia panel, how can i make this adjustments now?

But also my other command’s are no longer working.
How can i disable G-Sync right now under Wayland?

Here i had 2 bash scripts, to switch between CompositionPipeline On/Off and to disable G-Sync are no longer working at all:

#!/bin/bash
nvidia-settings -a currentmetamode="DP-4:2560x1440_144 { ForceCompositionPipeline=Off, AllowGSYNC=Off }"
#!/bin/bash
nvidia-settings -a currentmetamode="DP-4:2560x1440_144 { ForceCompositionPipeline=On, AllowGSYNC=Off }"

Every single adjustment is blocked right now under Wayland and my Dell Monitor is barely useable, specially with the missing Temporal Ditherfilter.

1 Like

kscreen-doctor is capable of doing a lot of configuration - if it is enough - I don’t know.

You may need to do a deep-dive into documentation to learn everything…

To get an idea of what can be done - run the command to get the current configuration

 $ kscreen-doctor -o
Output: 1 DP-2 80f20ad0-a79c-4d6d-bc64-7773ced8245e
        enabled
        connected
        priority 1
        DisplayPort
        replication source:0
        Modes:  1:5120x1440@120.00*!  2:3840x1080@119.97  3:3840x2160@120.00  4:3840x2160@119.88  5:3840x2160@60.00  6:3840x2160@59.94  7:3840x2160@50.00  8:5120x1440@59.98  9:3440x1440@120.00  10:3440x1440@59.97  11:3840x1080@59.97  12:2560x1440@120.00  13:2560x1440@59.95  14:1920x1080@120.00  15:1920x1080@119.88  16:1920x1080@60.00  17:1920x1080@60.00  18:1920x1080@59.94  19:1920x1080@50.00  20:1680x1050@59.95  21:1600x900@60.00  22:1280x1024@75.03  23:1280x1024@60.02  24:1440x900@59.89  25:1280x800@59.81  26:1152x864@75.00  27:1280x720@60.00  28:1280x720@60.00  29:1280x720@59.94  30:1280x720@50.00  31:1024x768@75.03  32:1024x768@70.07  33:1024x768@60.00  34:832x624@74.55  35:800x600@75.00  36:800x600@72.19  37:800x600@60.32  38:800x600@56.25  39:720x576@50.00  40:720x480@60.00  41:720x480@59.94  42:640x480@75.00  43:640x480@72.81  44:640x480@66.67  45:640x480@60.00  46:640x480@59.94  47:720x400@70.08  48:1600x1200@59.87  49:1600x1200@119.82  50:1280x1024@119.83  51:1024x768@119.80  52:1920x1200@59.88  53:1920x1200@119.90  54:1280x800@119.85  55:1600x900@119.95  56:1368x768@59.88  57:1368x768@119.83  58:1280x720@119.86 
        Geometry: 0,0 5120x1440
        Scale: 1
        Rotation: 1
        Overscan: 0
        Vrr: Automatic
        RgbRange: Full
        HDR: disabled
        Wide Color Gamut: disabled
        ICC profile: none
        Color profile source: EDID
        Color power preference: prefer accuracy
        Brightness control: supported, set to 51% and dimming to 100%
        Color resolution: automatic (16), range: [8; 16] bits per color
        Allow EDR: unsupported
        Sharpness control: unsupported

1 Like

Looks bad, Wayland is a joke for Nvidia Card Owner’s.

kscreen-doctor -o
Output: 1 DP-3 34335294-6e65-4687-85f4-87596f862250
        enabled
        connected
        priority 1
        DisplayPort
        replication source:0
        Modes:  1:2560x1440@59.95!  2:2560x1440@144.00*  3:2560x1440@120.00  4:2560x1440@99.95  5:2560x1440@84.98  6:2560x1440@23.97  7:1024x768@60.00  8:800x600@60.32  9:640x480@59.94 
        Geometry: 0,0 1970x1108
        Scale: 1.3
        Rotation: 1
        Overscan: 0
        Vrr: Automatic
        RgbRange: unknown
        HDR: incapable
        Wide Color Gamut: incapable
        ICC profile: none
        Color profile source: sRGB
        Color power preference: prefer efficiency and performance
        Brightness control: supported, set to 13% and dimming to 100%
        DDC/CI: allowed
        Color resolution: unknown
        Allow EDR: unsupported
        Sharpness control: unsupported

I have absolute no clue, how to improve the Monitor Output.

Honestly out of curiosity: Why do you need to tweak all that? I have an Nvidia card, and it just works. It just worked on X11, and it’s just worked on Wayland. Apparently I’ve been a lucky git, since I hear a lot of complaints about Nvidia support on Linux in general, but I’ve never had any.

Or is this because I have an older card (GTX 1070 Ti).

1 Like

GTX 960 here. Also never had problems any don’t use anything other than default settings.

GTX660 here :slight_smile:

1 Like

My individual settings makes a really big difference with my Dell Monitor, I have a really bad color banding with my Display… and without the Temporal Dither Effect from Nvidia, specially around Dark Environment and Black Colors the Video’s/Picture are total ugly
im talking easily around a 60% better picture here, the color grading destroys everything.

My Display has also no Gamma settings from its OSD (On Screen Display) Menue.
The Picture looks washes out, because the default Gamma is to high on my TFT.

And the performance fps are bad in some games, so with a 144Hz Display (because of G-Sync) the frame and Hz will sync… so instead 144Hz i just get 60Hz or even less.
I like to have G-Sync deactived because of that, its really improved the Display and its good for the eyes to have always 144Hz when i play games for few hours.

G-sync or AMD Freesync makes only sense with a high refresh monitor, if you can hold atleast 90fps. As i switched to Linux and found a RTS which i played, but its always runs at 30-50fps in lategame after 25min per session and i was wondering why my eyes hurting after 2hours playtime… which i never experienced before, because i really quickly disabled it under Windows, because i knew that Free Sync and G-Sync is ■■■■■■ hyped features.

And games today has more and more worse performance, and when you should have and hold 90fps/90Hz… its won’t work with Linux and games, its a downgrade.

ForceCompositionPipeline=On also removes tearing in games, which i have even with Vsync.

2 Likes

You should look for “variable refresh rate” in the display settings and turn that off.

I don’t use KDE, but maybe this works:

$ kscreen-doctor output.DP-3.vrrpolicy.never
1 Like

Thank you so much for that info and special that command :slight_smile:

1 Like

I have the exact same issue as you do, with my home built PC. I wish I could revert back to before the last update. Been using Manjaro Plasma for the last 3 years and I’ve been absolutely loving it. This is my first time on any Linux Forum, though I’ve used 5 or 6 other Linux distros for the past 20 years. I just now joined this forum because solving this nVidia settings issue is very important to me also. :smirking_face:

nVidia is a Joke, for people who want a decent modern compositor.

1 Like

Because Intel and AMD can offer competitive graphics adapters without requiring their driver code to be proprietary. :wink:

2 Likes

That’s also true, but KDE and Gnome is even a bigger joke, trying to force nvidia user’s to using Wayland when the support is not there.

X11 will still get supported till KDE 6.8 in 2027, if you are still using a nvidia 1660 related to your profile, then you can install nvidia legacy drivers 470.xx + LTS kernel and plasma-x11-session for X11.

In the mean time, all what we can do is registry in the nvidia forum and complain about the missing X11 feature’s and hope nvidia will get their ass up and finally give us proper wayland support.

I heared really bad stuff around Intels dedicated Ark GPU’s. Specially the Linux Driver around gaming is terrible.

No I would blame nVidia every time. They want to keep their crappy code base proprietary. That’s the real problem.

1 Like

It’s Open Source. It can be fixed by ‘The Community’. Proprietary code can not be. You are at the mercy of of a Corporation that doesn’t give a rats.

2 Likes

You may forgotten that nvidia has still the open source developer who reversed engineered nvidia nouveau driver and is working for nvidia.

Even if i may sounds naive, the game is not fully lost yet. And since Intel stopped pumping money in Linux since few month, i wouldn’t be sure. Who might win this game.

Spoiler Alert: AI sucks.

1 Like

I’m not a gamer, and nVidia graphics cards have outlasted other brands in all my builds for the last 20 years and they just happen to work best with proprietary drivers. When I choose “install with proprietary driver” I expect it to deliver all the features I paid dearly for.

I have moved away from Linux distros that did not provide installation of proprietary graphics drivers in the past. I would hate to have to ditch Manjaro, as I’ve grown to love it as the best Linux distro up until now. When I hear ad hominem attacks against a hardware product, I automatically think “logical fallacy for lack of having a valid counter argument”… Is it possible that “Wayland” (whatever that is) is wittingly boycotting nVidia by limiting its operational functionality?

In other words; Is this debate about brand name politics or about finding solutions that make everyone happy with whatever they prefer to use or consider to be more durable equipment based on their own experiences? (I have not been very lucky with intel or Radeon hardware in the past.)

Just sayin’…

But with that said I will try to find a way to make the following advice work for me; ”X11 will still get supported till KDE 6.8 in 2027, if you are still using a nvidia 1660 related to your profile, then you can install nvidia legacy drivers 470.xx + LTS kernel and plasma-x11-session for X11.”

Not sure how to proceed to accomplish that, but I will try to figure it out in the next few days.

Any tips for doing that efficiently will be greatly appreciated. Thanks!

At the moment it is actually the other way around. nVidia has been very slow to make the necessary changes for wayland, which is why they are now playing catch up, to the fully Open Source AMD and Intel.

I would say that is a fair argument. I hope they catch up soon.:slightly_smiling_face:

1 Like

Actually so do I.

1 Like