Bug 19924

Summary: Regression on xf86-video-ati driver from git version of Jan 28 on X200M cards
Product: xorg Reporter: Ge@@ru <geaaru>
Component: Driver/RadeonAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg log none

Description Ge@@ru 2009-02-03 02:08:18 UTC 
I update xf86-video-ati driver to git version of Jan 28 but seems that dual head doesn't work fine with my X200M ati card (on hp pavilion dv8002).
While with previous version 6.10.0 this problem doesn't happen.
I use gentoo environment.
With xrandr i can configure dual head correctly but then from vga output seems that frequency used is wrong.

Thanks,
Ge@@ru
Comment 1 Alex Deucher 2009-02-03 07:56:15 UTC 
this should be fixed in git master.  If you are still having problems, please attach your logs from the working and non-working cases.
Comment 2 Ge@@ru 2009-02-03 10:19:06 UTC 
Created attachment 22529 [details] [review]
Xorg log

Hi, i try last git version of Feb 3 but problem is not resolved.
What happens: if i try to connect my laptop to my SONY TV through VGA output with this xrandr command:
xrandr --addmode VGA-0 1024x768
xrandr --output LVDS --mode 1440x900 --output VGA-0 --mode 1024x768 --left-of LVDS
on SONY TV i see only black screen (i need call xrandr --addmode because seems that from VGA of the SONY screen there isn't EDID communication and so driver couldn't identify supported screen resolutions).

Some commands with version 6.10.0 of the xf86-video-ati driver works fine.

Ge@@ru
Comment 3 Alex Deucher 2009-02-03 16:47:42 UTC 
This should be fixed in commit 16e01a5796a8e8b86ad25d3aa45b9e7044dc72d1

Let me know if you are still having problems.
Comment 4 Ge@@ru 2009-02-05 01:41:23 UTC 
I confirm that now works.
Thank you very much.

Ge@@ru

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.