Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
AMDx64BTOffline
Post subject: Error xrandr rotation screen nvidia  PostPosted: 05.06.2011, 21:29



Joined: 2011-05-16
Posts: 5

Status: Offline
Some months ago, after an update, I get an error when I I try to rotate the screen using xrandr with nvidia card. Anyway the 3D applications work well. I have reinstalled the kernel and the nvidia commercial drivers, but rotation doesn't work.Any suggestion to get working again xrandr?

$xrandr -o right
X Error of failed request: BadMatch (invalid parameter attributes)
Major opcode of failed request: 154 (RANDR)
Minor opcode of failed request: 2 (RRSetScreenConfig)
Serial number of failed request: 14
Current serial number in output stream: 14
 
 View user's profile Send private message  
Reply with quote Back to top
towoOnline!
Post subject: RE: Error xrandr rotation screen nvidia  PostPosted: 05.06.2011, 21:42



Joined: 2010-09-13
Posts: 497
Location: Pößneck / Thüringen
Status: Online!
Nvidia has never had xrandr support with their drivers.
Use nvidia-settings instead for rotation.
 
 View user's profile Send private message  
Reply with quote Back to top
AMDx64BTOffline
Post subject: RE: Error xrandr rotation screen nvidia  PostPosted: 05.06.2011, 23:30



Joined: 2011-05-16
Posts: 5

Status: Offline
I have added RandRRotation to xorg.conf:
Section "Device"
Option "RandRRotation" "On"

Now when I execute nvidia-settings I have the panel to rotate the screenm but when I click over the button to rotate the nvidia-settings quit with a bug message. What I am doing wrong?

$ nvidia-settings

The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 289 error_code 2 request_code 154 minor_code 2)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)


And using the terminal I get the same error:

$ xrandr -o left

X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 154 (RANDR)
Minor opcode of failed request: 2 (RRSetScreenConfig)
Value in failed request: 0x556
Serial number of failed request: 14
Current serial number in output stream: 14
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio