http://bugs.freedesktop.org/show_bug.cgi?id=13173





------- Comment #5 from [EMAIL PROTECTED]  2007-11-12 03:39 PST -------
You might want to try the patches I just sent to xorg-devel about xrandr.c and
randr/rrcrtc.c - I will also push them this week. It could well be that you're
hitting the last case:

Upon recreation of the RandR internal data structures in RRCrtcNotify() the
crtc of an output could be NULLed if the crtc was shared (cloned) between two
outputs and one of them got another crtc assigned.

In this case you could only try to --off the according output and re-enable it.
The output of your xrandr command a bit strange indeed, no idea whether DVI-0
is off or just in an invalid state.

You also might want to add --crtc <x> to explicitly specify the crtc the
secondary output should be connect to, i.e. xrandr --output DVI-0 --off; xrandr
--output DVI-0 --mode 1600x1200 --crtc 1


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
xorg-driver-ati mailing list
[email protected]
http://lists.x.org/mailman/listinfo/xorg-driver-ati

Reply via email to