Bug 20074 - [RV630GL] Staying in clone mode (regression)
Summary: [RV630GL] Staying in clone mode (regression)
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-12 01:28 UTC by Nicolas Bareil
Modified: 2009-02-17 08:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Nicolas Bareil 2009-02-12 01:28:50 UTC
Hi,


On my FireGL v5600, the commit 690999b682c0f954e27d9f1b3a3d8db4ef865c21 introduced a regression with my dual screen configuration, it stays in clone mode whatever I do. Because of a crtc bug (https://bugs.freedesktop.org/show_bug.cgi?id=16111), the workaround was to:

xrandr --output DVI-1 --mode 1920x1200 --crtc 1
xrandr --output DVI-1 --left-of DVI-0 

But since the commit 690999b6, it doesn't work anymore letting the screens in clone mode.

My card is:

60:00.0 VGA compatible controller: ATI Technologies Inc RV630GL [FireGL v5600]

Logs are available there:
 * http://chdir.org/~nbareil/clonebug/Xorg.fail.log (logverbose 7)
 * http://chdir.org/~nbareil/clonebug/Xorg.good.log (logverbose 7)
 * http://chdir.org/~nbareil/clonebug/Xrandr.fail.log
 * http://chdir.org/~nbareil/clonebug/Xrandr.good.log


Thanks!
Comment 1 Alex Deucher 2009-02-12 09:05:38 UTC
Can you try again with xf86-video-ati from git master?
Comment 2 Nicolas Bareil 2009-02-12 09:57:12 UTC
(In reply to comment #1)
> Can you try again with xf86-video-ati from git master?
> 

Same thing with c6e1bf75c399807716b99486ab3301aeba60fa79 the screens stay in clone mode, even after the workaround (xrandr --output DVI-1 --mode 1920x1200 --crtc 1; xrandr --output DVI-1 --left-of DVI-0 ).

You can find the Xserver log (without logverbose=7, sorry) on http://chdir.org/~nbareil/clonebug/Xorg.fail.2.log


Thank you for investigating!
Comment 3 Alex Deucher 2009-02-17 08:28:23 UTC
This should be fixed in 31bd6d28dd35021e0e706d4f094989deb856c26a
Please verify.
Comment 4 Nicolas Bareil 2009-02-17 08:51:28 UTC
(In reply to comment #3)
> This should be fixed in 31bd6d28dd35021e0e706d4f094989deb856c26a
> Please verify.
> 

It works now !

Thank you very much.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.