Bug 2755 - DVI monitor not detected
Summary: DVI monitor not detected
Status: CLOSED DUPLICATE of bug 1559
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 6.8.2
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-17 06:01 UTC by Peter Metzler
Modified: 2005-10-04 02:20 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
xorg.log created with Xorg -verbose 5 (42.18 KB, text/plain)
2005-03-18 15:58 UTC, Peter Metzler
no flags Details
xorg.conf (4.01 KB, text/plain)
2005-03-18 16:00 UTC, Peter Metzler
no flags Details
working xorg.conf (5.32 KB, text/plain)
2005-03-23 13:17 UTC, Peter Metzler
no flags Details

Description Peter Metzler 2005-03-17 06:01:15 UTC
I am using Gentoo and all xorg versions greater 6.7 i.e. 6.8.0 - 6.8.2 failing
in detecting my lcd display.
I have a ati firegl8700 card and a nec multisync lcd 2080ux+ display, native
resolution 1600x1200, 
connected via DVI port.

xorg.conf was generated by Xorg -configure.
From the log it seems that the driver doesn't detect the dvi port at all.

.....
(II) RADEON(0): Primary:
 Monitor   -- NONE
 Connector -- VGA
 DAC Type  -- Primary
 TMDS Type -- NONE
 DDC Type  -- VGA_DDC
(II) RADEON(0): Secondary:
 Monitor   -- NONE
 Connector -- None
 DAC Type  -- Unknown
 TMDS Type -- NONE
 DDC Type  -- NONE
.....

Setting MonitorLayout to "TMDS,CRT" or "CRT,TMDS" and specifying VertRefresh and
HorizSync does not solve the problem.
It seems that this bug is related to bug 1559, but I am not sure.

xorg 6.7 works "out of the box".
Comment 1 Peter Metzler 2005-03-18 15:54:55 UTC
Now, I have installed xorg-6.8.2 CVS.
If I set MonitorLayout to "TMDS,CRT" (this is the only setting which detects the
DVI connector) i get:
..........
(II) RADEON(0): Primary:
 Monitor   -- TMDS
 Connector -- DVI-D
 DAC Type  -- TVDAC/ExtDAC
 TMDS Type -- NONE
 DDC Type  -- NONE
(II) RADEON(0): Secondary:
 Monitor   -- CRT
 Connector -- VGA
 DAC Type  -- Primary
 TMDS Type -- NONE
 DDC Type  -- VGA_DDC
..........
and xorg starts with a 640x480 screen.

If I set PanelSize to 1600x1200 disable DDC and set VertRefresh and HorizSync
accordingly I get a horrible looking screen
with a lot of "noise", hard to describe.
Comment 2 Peter Metzler 2005-03-18 15:58:27 UTC
Created attachment 2145 [details]
xorg.log created with Xorg -verbose 5
Comment 3 Peter Metzler 2005-03-18 16:00:12 UTC
Created attachment 2146 [details]
xorg.conf
Comment 4 Alex Deucher 2005-03-21 07:55:01 UTC
try adding some modes to the display sub-sections of your screen section.  eg:
        Subsection "Display"
                Depth       16
                Modes       "1600x1200" "1024x768" "800x600" "640x480"
        EndSubsection
        Subsection "Display"
                Depth       24
                Modes       "1600x1200" "1024x768" "800x600" "640x480"
        EndSubsection
Comment 5 Peter Metzler 2005-03-23 13:13:50 UTC
Thanks for the hint. This has solved the problem.

I have added a few Modes, commented out PanelSize and got a much better looking
screen but not perfect because the top of the displayed screen was in the middle
of the monitor screen.
I have then added a few modelines from an old xorg-6.7 log and now it works
perfectly.

I will add my working xorg.conf to this report, so other guys with the same
problem can have a look into it.
Comment 6 Peter Metzler 2005-03-23 13:17:32 UTC
Created attachment 2198 [details]
working xorg.conf
Comment 7 T. Hood 2005-09-23 09:00:28 UTC
Does it still work if you don't add the Modelines?  (I.e., you add the Modes
options in the "Screen" section but not the Modelines options in the "Monitor"
section.)
Comment 8 T. Hood 2005-09-25 03:50:01 UTC

*** This bug has been marked as a duplicate of 1559 ***
Comment 9 Shawn Starr 2005-10-04 19:20:30 UTC
This is not a duplicate the problem was resolved. 


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.