|
|
#1 | |
|
Registered User
Join Date: Dec 2008
Posts: 128
|
Hi. I just updated my drivers to 256.44 and now I get this when looking at xrandr output:
xrandr: Failed to get size of gamma for output default Is this something to be concerned with? |
|
|
|
|
|
|
#2 | |
|
Registered User
Join Date: Dec 2008
Posts: 128
|
Nobody knows anything about it?
|
|
|
|
|
|
|
#3 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
primerib,
Can you please supply an nvidia bug report (see stickies), the exact xrandr command-line you're using, and also the driver version where this used to work, if any? Thanks. |
|
|
|
|
|
#4 | |
|
Registered User
Join Date: Sep 2010
Posts: 2
|
Hi Stephen, stumbled upon this thread after some googling; I was getting this with $ xrandr too. It's probably unrelated to my issue but:
I was looking into xrandr because something broke either in maverick, xorg1.9 or 256.53. Xinerama Info is not properly working, all my apps launch either in the middle of the screen, or stuck on the right side of my primary screen. My xorg.conf bit: Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 Option "TwinView" "1" Option "TwinViewXineramaInfoOrder" "DFP-0, DFP-1" Option "metamodes" "DFP-0: 1680x1050 +0+0, DFP-1: 1680x1050 +1680+0" SubSection "Display" Depth 24 EndSubSection $ xrandr outputs: xrandr: Failed to get size of gamma for output default Screen 0: minimum 3360 x 1050, current 3360 x 1050, maximum 3360 x 1050 default connected 3360x1050+0+0 0mm x 0mm 3360x1050 50.0 51.0* |
|
|
|
|
|
|
#5 |
|
Moderator
Join Date: Aug 2005
Posts: 1,327
|
This is probably just an unsupported feature in NVIDIA's driver, and not a problem. I believe the gamma APIs were added as part of XRandR 1.2, whereas the NVIDIA driver only supports XRandR 1.1.
|
|
|
|
![]() |
| Thread Tools | |
|
|