Hi. Sometimes, I need to switch to Windows (dual boot). Having a NVidia 4090, on Windows I am able to tweak setting on that card using (if I want to) Nvidia Control Panel of Nvidia Profile Inspector.
Now, back to TumbleWeed. Two monitors, VRR, Wayland it is. Working perfect. Latest NVidia driver (570.172).
How are the nvidia-settings taken care of? There doesnt seem a way to manually manipulate them (which is fine). Are those driver settings taken care of by Wayland protocols, deeply hidden and not to be touched?
And if you are asking about more specific settings there are experimental efforts with this and that, but still no equivalent to “Nvidia X server Settings”.
Examples: nv-settings-wayland nvidia_oc
I install the “hard way” so with “coolbits” in my X configuration files I have nvidia-settings with control over gpu/memclock and overall fan percentage
I also noticed that the discover app in KDE now has a LACT flatpak that supports nvidia now … I don’t have an up-to-date machine so I didn’t play with it much … LACT needs a systemd daemon IIRC
@hoevenvd You can also create a /etc/environment and add global options for example I only want the Nvidia GPU used first for Vulkan so I use;
## Nvidia Quadro T400 for vulkan default
MESA_VK_DEVICE_SELECT="10de:1fb2"
Now I’m running Kernel:HEAD as well for the Xe driver improvements for Intel ARC, but it doesn’t play nice with google-chrome, so I also have;
## Intel DG2 [Arc A310] Xe driver and google-chrome on Wayland
LIBVA_DRIVER_NAME=nvidia
Then to reduce mutter debug output I have;
## Reduce Mutter debugging output
MUTTER_DEBUG_FORCE_KMS_MODE=simple
Lots of tweaks can be done here depending on what gpu setup you have and whether you want it global or at run time with the likes of Steam or maybe Flatseal if using flatpaks.
Then there are specific nvidia driver tweaks vi a /etc/modprobe.d/ file to complement the rpm defaults. Or of course nvidia-setting -a <some attribute> if it’s writeable.