You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm excited about this but was wondering if this supports Wayland? Since you mention 'coolbits' as a requirement I'm guessing that's a no. I'm attempting to migrate to Wayland and only gaming is a problem. I can overclock with NVML but changing the power-limit is not supported for my GPU yet via NVML. I can do that on nvidia-smi but that only works properly on X11. Right now if I put my clock where I want it I'll get those weird artifacts indicative of an unstable overclock because I couldn't raise my power-limit. I'm really wanting to figure this out on Wayland and would appreciate anything.
The text was updated successfully, but these errors were encountered:
changing the power-limit is not supported for my GPU yet via NVML.
I don't think changing power limit has ever been possible through anything but NVML, sounds like the issue of being unable to set power limit is somewhere else
I distinctly remember doing this with nvidia-smi in the past while I was using X11. It's worth noting I've had quite a few driver changes since then. I think now I'm on 565 something. Not entirely sure what it was then. I do know from Nvidia that all there is only partial NVML support for GeForce branded GPUs.
I'm excited about this but was wondering if this supports Wayland? Since you mention 'coolbits' as a requirement I'm guessing that's a no. I'm attempting to migrate to Wayland and only gaming is a problem. I can overclock with NVML but changing the power-limit is not supported for my GPU yet via NVML. I can do that on nvidia-smi but that only works properly on X11. Right now if I put my clock where I want it I'll get those weird artifacts indicative of an unstable overclock because I couldn't raise my power-limit. I'm really wanting to figure this out on Wayland and would appreciate anything.
The text was updated successfully, but these errors were encountered: