$ nvidia-settings --assign CurrentMetaMode="HDMI-0: 1920x1080 { ForceCompositionPipeline = On }"
ERROR: Error resolving target specification '' (No targets match target specification), specified in assignment 'CurrentMetaMode=HDMI-0: 1920x1080 { ForceCompositionPipeline = On }'.
$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected primary (normal left inverted right x axis y axis)
DVI-I-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm
1920x1080 60.0*+ 59.9 50.0 60.1 60.0 50.0
1680x1050 60.0
1600x900 60.0
1440x900 59.9
1400x1050 60.0
1280x1024 60.0
1280x800 59.8
1280x720 60.0 59.9 50.0
1152x864 60.0
1024x768 60.0
800x600 60.3
720x576 50.0
720x480 59.9
640x480 59.9 59.9
DP-0 disconnected (normal left inverted right x axis y axis)
DVI-D-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
NVIDIA drivers 346.47, GTX 660, FullHD monitor connected via HDMI.
I guess it has something to do with my VNC screen, but then I’m confused as to how I can use VNC and NVIDIA simultaneously. nvidia-bug-report.7z (171 KB)
Aha, here’s the problem:
[ 10.236] (EE) Not enabling extension NV-CONTROL: maximum number of events or errors exceeded.
The X11 protocol has a limit to the number of errors and events combined, and loading both the VNC module and the NV-CONTROL extension ends up trying to allocate too many. Without the NV-CONTROL extension, nvidia-settings can’t communicate with the X driver.
XvMC and DGA are two extensions you will definitely not be missing ever, and disabling them frees up slots for all the Nvidia extensions. It used to be possible to disable XvMC and DGA in xorg.conf, but at some point they were made an integral part of X, so now patching is required.