Setting mode with xrandr fails after changing panning region
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
X.Org X server |
Confirmed
|
High
|
|||
x11-xserver-utils (Ubuntu) |
Triaged
|
Medium
|
Chris Halse Rogers |
Bug Description
Binary package hint: x11-xserver-utils
The problem was observed on both Karmic and Lucid (current as at March 2, 2010) using both the open-source radeon driver and the proprietary fglrx driver on different ATI cards (at least RV730 and RV740).
Steps to reproduce (with a 1900x1200 DFP monitor using the fglrx driver, output names are different with radeon):
- xrandr --output DFP1 --mode 1440x900
- xrandr --output DFP1 --panning 1920x1200
- pan around
- xrandr --output DFP1 --panning 1440x900
- xrandr --output DFP1 --mode 1920x1200
Expected result:
- DFP1 should switch mode to 1920x1200, adjusting the desktop size as appropriate
Actual result:
- mode does not change from 1440x900
- the terminal shows the following message: "xrandr: Configure crtc0 invalid time"
- the system remains usable but the mode cannot be changed using xrandr on DFP1
After restarting the Xserver, modes can be changed again.
One of our engineers found a workaround in xrandr. It allows the mode to be changed but there are still other error messages:
--- bak/x11-
+++ x11-xserver-
@@ -1346,7 +1346,10 @@ crtc_apply (crtc_t *crtc)
if (s == RRSetConfigSuccess && crtc->panning_info) {
if (has_1_3)
+ {
+ crtc->panning_
s = XRRSetPanning (dpy, res, crtc->crtc.xid, crtc->panning_
+ }
else
}
Changed in xorg-server: | |
status: | Unknown → Confirmed |
tags: | added: lucid |
Changed in x11-xserver-utils (Ubuntu): | |
assignee: | Bryce Harrington (bryceharrington) → Chris Halse Rogers (raof) |
tags: | added: hardy |
Changed in xorg-server: | |
importance: | Unknown → Medium |
Changed in xorg-server: | |
importance: | Medium → Unknown |
Changed in xorg-server: | |
importance: | Unknown → Medium |
Changed in xorg-server: | |
importance: | Medium → High |
Thanks, btw if you attach patches to the bug report (and make sure they're marked as patches) rather than paste them in, they'll show up in my patch review queue which ensures they'll get attention. It's just lucky happenstance I noticed this one come in just now; since this package does not often get reviewed this likely would have gotten lost in the shuffle.