From Bugzilla Helper:
User-Agent: Opera/7.54 (X11; Linux i686; U) [en]
Description of problem:
I have an Eizo Flexscan L885 1600x1200 pixel TFT display
connected to an ASUS Radeon 9200 SE/TD 128 AGP display card:
The graphics card sits on a dual 500 MHz PIII ASUS P2B-DS motherboard
with 256 MB RAM.
The radeon driver gives me a X11-display over the DVI-connection in
1400x1050, 1280x1024, 1024x768, 800x600 and 640x480, but NOT in the
1600x1200 mode which is the native mode of my TFT display. According
to the monitor no signal is present on the DVI input when I switch to
1600x1200 pixels. Over the analog VGA connection I get a viewable
1600x1200 mode with fH 75,0 kHz and fV 60,0 Hz.
I have tried with 16 bit, no DRI but this does not give me a
1600x1200 DVI output.
Initially I could not get any DVI-output when running system-config-
display. By adding
Option "MonitorLayout" "TMDS, CRT"
to xorg.conf by hand and editing the refresh rates to be compatible
with my monitor in digital mode, I could get to the situation
The Eizo Flexscan L885 seems also to be missing from the monitor list
used by system-config-display.
Best regards, Tomas Linden
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.add Option "MonitorLayout" "TMDS, CRT" to xorg.conf
3.try to use the DVI connection in the 1600x1200 mode
Actual Results: The monitor says that no signal is detected on the
Expected Results: A 1600x1200 pixel display on the DVI-input.
Created attachment 109185 [details]
My xorg.conf file.
Created attachment 109186 [details]
The Xserver log file.
The Xserver log-file corresponding to my xorg.conf file.
I added the following option to the device section of xorg.conf
Option "PanelSize" "1600x1200"
This finally gives me a signal over the DVI-connection also for the
1600x1200 mode. Unfortunately this has severe side effects, because
the screen blanks for one to three times for a short moment with
random intervals. This happens sometimes so often that the mode is
not usable, unfortunately. Without the PanelSize option the DVI-
output did not blank for the sizes less than 1600x1200.
Another side effect is that changing the resolution on the fly with
xrandr gives strange striped borders on the left and right side of
the display in 1400x1050. Switching to 1280x1024 and 800x600 the
right part of the desktop is actually shown on the left edge of the
display. Switching to 1024x768 and 640x480 works as expected.
This problem was also not present without the PanelSize option.
I upgraded X11 to the latest version found from the Fedora devel
to the version shown below, but I still have the random blanks of the
1600x1200 DVI signal. The same problem with xrandr and the DVI modes
as before is still present with this new X11 version.
X Window System Version 22.214.171.1242 (6.8.2 RC 2)
Release Date: 12 January 2005
X Protocol Version 11, Revision 0, Release 126.96.36.1992
Build Operating System: Linux 2.4.21-27.ELsmp i686 [ELF]
Current Operating System: Linux pc27b.hip.helsinki.fi 2.6.10-1.
741_FC3smp #1 SMP
Thu Jan 13 16:53:16 EST 2005 i686
Build Date: 14 January 2005
Build Host: decompose.build.redhat.com
Please upgrade to the xorg-x11-6.8.2 release in fc3-testing, and indicate
if the problem still exists. If the problem persists, please file a bug
report in X.Org bugzilla at http://bugs.freedesktop.org with full details
as well, and attach your X server log and config file to the X.Org bug
Once you've filed your report in X.Org bugzilla, please paste the bug URL
here and we will track the issue there as well, and review any patches that
become available for consideration in future builds.
Thanks in advance.
Setting status to "NEEDINFO", awaiting testing status update and bug URL.
Bug #142932 might be related.
I upgraded to
X Window System Version 6.8.2
from the Fedora Core 3 test RPMS, but unfortunately the problems still remain,
so I have now filed a bug at X.org
*** Bug 142932 has been marked as a duplicate of this bug. ***
This seems to be a generic bug in the Radeon driver, unable to detect
DFP's properly. We're now tracking this in the X.Org bugzilla. Thanks
for reporting it upstream.
When a fix becomes available, we will review it for consideration in