Open gepbird opened 1 year ago
Nevermind, I can enable second monitor in nvidia settings. Still weird that forceFullCompositionPipeline disables it.
Changing settings in the GUI doesn't preserve between reboots. Is there a nix option for controlling nvidia-settings?
When exporting the xserver configuration from nvidia settings, both monitors are in screen section metamodes:
Option "metamodes" "HDMI-0: nvidia-auto-select +1920+0, DVI-D-0: nvidia-auto-select +0+0"
but with hardware.nvidia.forceFullCompositionPipeline = true
, no monitors are specified, so I assume only the first monitor it founds will work:
Option "metamodes" "nvidia-auto-select +0+0 {ForceFullCompositionPipeline=On}"
My current workaround is to configure FullCompositionPipeline using the services.xserver.screenSection option. For my two monitor setup I configure ForceFullCompositionPipeline individually on each monitor.
services.xserver.screenSection = ''Option "metamodes" "nvidia-auto-select {ForceFullCompositionPipeline=On}, nvidia-auto-select {ForceFullCompositionPipeline=On}"'';
Describe the bug
By enabling
hardware.nvidia.forceFullCompositionPipeline
, it fixes the screen tearing as expected, but disables a 2nd monitor.Steps To Reproduce
Steps to reproduce the behavior:
open
tofalse
andforceFullCompositionPipeline
totrue
Expected behavior
Second monitor works as before.
Screenshots
Additional context
Both monitors work when
hardware.nvidia.forceFullCompositionPipeline = false
.Notify maintainers
@schuelermine
Metadata