http://bugs.freedesktop.org/show_bug.cgi?id=13173
--- Comment #11 from Alex Deucher <[EMAIL PROTECTED]> 2008-02-25 11:01:05 PST --- The problem is with randr 1.0, there was no concept of crtcs or outputs, so the "head" was whatever ended up being detected as connected (DVI, VGA, etc.). With randr 1.2 you have multiple crtc and outputs and one output and one crtc get chosen as the "compat" output and crtc (which very well may be different than what you got under randr 1.0 and the old driver). Now, if you use the xrandr 1.0 compatibility layer, it will change the mode on the compatibility crtc and output even though you may have them routed differently using xrandr 1.2 commands; that particular crtc and output may not even be currently associated. I'm not sure why the randr compat stuff permanently breaks changes via randr 1.2 though. Does forcing the crtcs help when attempting to reset the modes using randr 1.2? xrandr --output DVI-0 --crtc 1 --mode 1280x1024 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
