Bug 10697

Summary: ATI 6.6.191 + Xserver 1.2.99 does not find any monitor
Product: xorg Reporter: Brice Goglin <brice.goglin>
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: git   
Hardware: Other   
OS: All   
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413500
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log from ati 6.6.191 (not working)
none
working xorg.conf
none
Xorg.0.log from ati 6.6.3-2 (working)
none
Xorg.0.log from ati 6.6.192 (not working) none

Description Brice Goglin 2007-04-20 17:04:16 UTC
Bug reported by Marcin Juszkiewicz (and confirmed by Piotr Roszatycki and Stefano Rivoir) on the Debian BTS about 2 months ago.

Xserver 1.1.1 + ATI 6.6.3 worked fine. Upgrading to Xserver 1.3-rc and ATI 6.6.191 makes X not start anymore. Note that the bug was initially reported against Xserver 1.2 and an pre-6.6.191 ATI snapshot (named 6.6.3-5 in Debian).
The submitter has a Xpress 200.

xorg.conf and Xorg.0.log are available at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=413500

Brice
Comment 1 Marcin Juszkiewicz 2007-04-21 13:41:55 UTC
Created attachment 9677 [details]
Xorg.0.log from ati 6.6.191 (not working)

ii  xserver-xorg            7.2-2                   the X.Org X server
ii  xserver-xorg-core       1.3.0.0.dfsg-1          X.Org X server -- core server
ii  xserver-xorg-video-ati  6.6.3-2                 X.Org X server -- ATI display driver

This combo works here with xorg.conf which I will attach in a moment. 

Upgrading xserver-xorg-video-ati to 6.6.191 break work. My LCD panel starts to switch from DVI (here card is connected) to VGA (nothing connected) and back.
Comment 2 Marcin Juszkiewicz 2007-04-21 13:42:25 UTC
Created attachment 9678 [details]
working xorg.conf

working xorg.conf
Comment 3 Marcin Juszkiewicz 2007-04-22 02:40:42 UTC
Created attachment 9684 [details]
Xorg.0.log from ati 6.6.3-2 (working)

Xorg.0.log from working combination of X and driver
Comment 4 Marcin Juszkiewicz 2007-05-27 03:07:16 UTC
Created attachment 10098 [details]
Xorg.0.log from ati 6.6.192 (not working)

driver built from GIT tree:

commit 975da595f032c145ad74079ff8edeaead779dc7b
Author: Michel Dänzer <michel@tungstengraphics.com>
Date:   Tue May 22 10:56:47 2007 +0200


Next time I will avoid ATI cards.
Comment 5 Alex Deucher 2007-05-27 21:43:05 UTC
This is due to the bios connector table being bogus.  It used to work in the older version of the driver since we restored just about all the output regs unconditionally; however in the newer driver we have finer grained control over what outputs are are used and how they are routed so if the tables are bogus things are more likely to break.  Also, the XPRESS chips are completely undocumented and as such we are not sure what all components they have or how they are wired up.  Some have reported that DVI is provided by an external TMDS chip; as such it's possible that XPRESS chips don't actually have the built-in TMDS.

We probably need to bring in something like the "ConnectorTable" option in the randr-1.2 branch so that we can override all aspects of the connectors (DDC line, tmds type, DAC, etc.).
Comment 6 Marcin Juszkiewicz 2007-07-09 06:43:53 UTC
In meantime I bought NVidia 6600GT card and do not use ATI on-board any more. If testing will be needed I can try new code.
Comment 7 kowalski marcin 2007-08-24 01:51:08 UTC
i had a similar issue recently, albeit with a bit different ati x300se card. it's fixed now in git (after randr1.2 merge) and the driver works for me. 

maybe you should try again with newest git. ( my bug was #11850 , for reference ).
Comment 8 Alex Deucher 2007-08-24 06:59:34 UTC
This should work with latest git.
Comment 9 Alex Deucher 2007-08-31 08:26:44 UTC
closing.  reopen if you are still having issues with the latest code from git.

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.