Bug 12229 - xrandr: cannot find crtc for output VGA-0
Summary: xrandr: cannot find crtc for output VGA-0
Status: RESOLVED DUPLICATE of bug 12165
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-31 00:48 UTC by Thomas M.
Modified: 2007-09-14 15:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf (5.47 KB, application/octet-stream)
2007-08-31 00:50 UTC, Thomas M.
no flags Details
Xorg.0.log (97.18 KB, text/x-log)
2007-08-31 00:51 UTC, Thomas M.
no flags Details

Description Thomas M. 2007-08-31 00:48:39 UTC
Xorg version : 7.3RC1 (xserver-xorg debian package version 1:7.3~rc1)
Radeon driver version: 6.7.192 (xserver-xorg-video-ati version 1:6.7.192-1)
Xrandr utility version found in debian package x11-xserver-utils version 7.2+3.
I'm using a ATI Radeon "ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]".

I recently upgraded to the randr12-enabled version of the ati/radeon driver.
I have issue with activating an external LCD screen plugged on the VGA output.

I have the following message:

  $ xrandr --output VGA-0 --auto                                                                           
  xrandr: cannot find crtc for output VGA-0

I can sometimes successfully activate this external screen, but quite rarely, and I could'nt find a reproducible way of being successfull.

I'm attaching to this report my xorg.conf and Xorg.0.log
Comment 1 Thomas M. 2007-08-31 00:50:10 UTC
Created attachment 11348 [details]
xorg.conf
Comment 2 Thomas M. 2007-08-31 00:51:51 UTC
Created attachment 11349 [details]
Xorg.0.log
Comment 3 Thomas M. 2007-08-31 03:10:02 UTC
I forgot to add the output of the xrandr command, which will likely be usefull:

% xrandr
Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 2680 x 2680
VGA-0 connected (normal left inverted right x axis y axis)
   1280x1024      60.0 +   75.0     59.9  
   1280x960       59.9  
   1152x864       75.0     74.8     69.8  
   1024x768       75.1     70.1     60.0  
   832x624        74.6  
   800x600        72.2     75.0     60.3     56.2  
   640x480        75.0     72.8     66.7     60.0  
   720x400        70.1  
DVI-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1400x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1400x1050      60.0*+
   1280x800       60.0  
   1280x768       60.0  
   1024x768       60.0  
   800x600        60.3  
   640x480        59.9  
   1280x1024      60.0  
S-video disconnected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
  800x600 (0x4e)   38.2MHz
        h: width   800 start  832 end  912 total 1024 skew    0 clock   37.4KHz
        v: height  600 start  603 end  607 total  624           clock   59.9Hz


Comment 4 Thomas M. 2007-08-31 03:11:52 UTC
I just found a workaround : after doing an "xrandr --output S-video --off", I can sucessfully activate the VGA-0 output.  I obviously have no idea why it helps.

All this might be related to bug #12230.
Comment 5 Thomas M. 2007-08-31 03:13:51 UTC
Note well that I don't use the S-video output, and that nothing is connected to it. The fact that I have turn S-video off while it is marked disconnected, to have VGA-0 working is definitely weird.
Comment 6 Alex Deucher 2007-08-31 06:44:33 UTC
We do load detection on the tvdac for tv-out detection, however, it's not always reliable on all different chips, hence you get false positives on occasion.  There is an alternate tv detection routine that seems to work better on some r3xx chips.  you can try it by commenting out lines 1414-1414 in radeon_output.c

remove these:
     if (IS_R300_VARIANT)
         return r300_detect_tv(pScrn);

We may just have to turn off load detection by default for the tvdac.
Comment 7 Alex Deucher 2007-08-31 06:45:43 UTC
lines 1413-1414 obviously.
Comment 8 Alex Deucher 2007-09-14 15:53:32 UTC

*** This bug has been marked as a duplicate of bug 12165 ***


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.