Bug 19802

Summary: [4850HD] Output DVI-I_2/analog enabled but has no modes
Product: xorg Reporter: Bryce Harrington <bryce>
Component: Driver/radeonhdAssignee: xf86-video-ati maintainers <xorg-driver-ati>
Status: RESOLVED WONTFIX QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: high CC: hugh
Version: 7.3 (2007.09)   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Xorg.0.log none

Description Bryce Harrington 2009-01-29 00:13:54 UTC 
Created attachment 22338 [details] [review]
Xorg.0.log

Forwarding this bug from a Ubuntu reporter:
https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/319930

[Original Report]
I encounter the error "Radeon (0): Output DVI-0 enabled but has no modes" when trying to boot into Jaunty using either the ati or Radeonhd drivers.

I also encountered a similar error when trying to use the livecd. After unsuccessfully trying to load up, I am sent to the terminal with an error code "Output DVI-I_2/analog enabled but has no modes" The only way of viewing the livecd or a proper installation was to go into low graphics mode (vesa)

If I go into display settings, it comes up with "Monitor: Unknown" and a refresh rate of 0.

I am running Jaunty Alpha 3 AMD64, using a Ati Radeon 4850HD card with a HP Ultra VGA 1280 monitor attached to the video card with a vga to dvi adapter

I have not encountered this problem with either Hardy or Intrepid installations in the past

[lspci]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV770 [Radeon HD 4850] [1002:9442]
Comment 1 Bryce Harrington 2009-02-26 14:23:39 UTC 
Reporter indicates in the downstream bug that the issue has gone away with the latest driver.
Comment 2 Leszek Matok 2009-03-15 03:17:56 UTC 
Not true - he reported it working with the vesa driver. I'd reopen it if I were you.
Comment 3 D. Hugh Redelmeier 2009-05-24 19:09:10 UTC 
There is a chance that this is related to https://bugzilla.redhat.com/show_bug.cgi?id=487285

(I'm reopening because the original poster's problem is not solved, not because my problem might be related.)
Comment 4 Alex Deucher 2009-11-11 10:50:21 UTC 
Looks like he's actually using radeonhd.
Comment 5 Matthias Hopf 2009-11-13 05:08:23 UTC 
Version 1.2.4 is too old, please retry with newer 1.3.0.
Also, the config seem to have a configured monitor. Retry with out the
  Monitor "Monitor[0]"
or equivalent line in the Screen section.
Comment 6 Jeremy Huddleston Sequoia 2011-10-16 15:57:27 UTC 
Does this issue occur with the preferred ati driver (xf86-vide-ati)?  If so, please move this to the Driver/Radeon component.  

Development of radeonhd has pretty much halted and development focus is on the ati driver.  Please see http://www.x.org/wiki/radeonhd

If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Comment 7 Jeremy Huddleston Sequoia 2011-11-07 15:26:16 UTC 
Closing due to lack of response.  Please reopen and move to the Driver/Radeon 
component if this issue persists with xf86-video-ati

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.