[Bug 482838] New: RandR in Xserver 1.6.0 doesn't reactivate re-cloned outputs
https://bugzilla.novell.com/show_bug.cgi?id=482838 Summary: RandR in Xserver 1.6.0 doesn't reactivate re-cloned outputs Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: ASSIGNED Severity: Major Priority: P5 - None Component: X.Org AssignedTo: mhopf@novell.com ReportedBy: mhopf@novell.com QAContact: xorg-maintainer-bugs@forge.provo.novell.com CC: sndirsch@novell.com Found By: --- xrandr --verbose --output a --left-of b -> a uses CRTC0, b uses CRTC 1 xrandr --verbose --output b --crtc 0 -> both a,b use CRTC0 xrandr --verbose shows that X has the view that both outputs are active and using the same CRTC. Using the radeonhd driver and -logverbose 7 shows that the driver doesn't get an rhdRROutputDpms() activation of the re-cloned output: (II) RADEONHD(0): State at POST-CrtcDpms: RRCrtc #0 [rhd CRTC 1]: active 1 [1] mode unnamed (1680x1050) +0+0 RRCrtc #1 [rhd CRTC 2]: active 0 [0] mode unnamed (0x0) +1680+0 RROut DVI-I_1/analog [Out DAC A Conn DVI-I 1] Crtc null [null] [inactive] disconnected RROut DVI-I_1/digital [Out TMDS A Conn DVI-I 1] Crtc CRTC 1 [CRTC 1] [active] connected RROut TV_SVIDEO [Out DAC B Conn TV SVIDEO] Crtc null [null] [inactive] disconnected RROut DVI-I_2/analog [Out DAC B Conn DVI-I 2] Crtc null [null] [inactive] disconnected RROut DVI-I_2/digital [Out TMDS B Conn DVI-I 2] Crtc CRTC 1 [CRTC 2] [inactive] connected This clearly indicates a bug in the RandR implementation in the Xserver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=482838 Matthias Hopf <mhopf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=482838 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=482838#c1 --- Comment #1 from Stefan Dirsch <sndirsch@novell.com> 2009-03-09 20:02:01 MST --- Related upstream bug? https://bugs.freedesktop.org/show_bug.cgi?id=14570 Related commits to xrandr? commit 39a16783a3d1c0c722b4b18fab60a91b9f6ed578 Author: Matthias Hopf <mhopf@suse.de> Date: Fri Mar 6 14:49:43 2009 +0100 Revert "Move outputs among crtcs as necessary. Fixes 14570" This reverts commit 4dcc8ae1a6903434def1a2706f7c68ff9e2a17c4. The commit broke uncloning completely again. commit 4dcc8ae1a6903434def1a2706f7c68ff9e2a17c4 Author: Hong Liu <hong.liu@intel.com> Date: Mon Mar 10 21:37:09 2008 -0700 Move outputs among crtcs as necessary. Fixes 14570 This patch makes new requests override existing crtc allocations. Outputs with restricted crtc usage can now force existing outputs to switch automatcially. I've now applied the first one to our xrandr-1.2.99.4 package. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=482838 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=482838#c2 --- Comment #2 from Matthias Hopf <mhopf@novell.com> 2009-03-10 08:53:47 MST --- Created an attachment (id=278484) --> (https://bugzilla.novell.com/attachment.cgi?id=278484) Patch for xserver This has been fallout from panning support. We cannot do a shortcut at this particular point, because the crtcs of outputs might have changed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=482838 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=482838#c3 --- Comment #3 from Matthias Hopf <mhopf@novell.com> 2009-03-10 08:58:45 MST --- xrandr was broken as well, the first xrandr call in the bug description wouldn't work without the patch you already applied. There still seems to be something weird in radeonhd, but that's a different bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=482838 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=482838#c4 Matthias Hopf <mhopf@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mhopf@novell.com |sndirsch@novell.com Severity|Major |Normal --- Comment #4 from Matthias Hopf <mhopf@novell.com> 2009-03-10 09:01:06 MST --- Doesn't need an urgent update, thus reassigning. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=482838 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=482838#c5 Stefan Dirsch <sndirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #5 from Stefan Dirsch <sndirsch@novell.com> 2009-03-10 09:15:03 MST --- fixed for factory and X11:XOrg. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=482838 User mhopf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=482838#c6 --- Comment #6 from Matthias Hopf <mhopf@novell.com> 2009-03-10 09:42:46 MST --- Gosh, you're fast. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com