Red Hat Bugzilla – Bug 107073
EDID Monitor data produces incorrect Xserver display
Last modified: 2007-11-30 17:06:58 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux ia64; en-US; rv:1.4) Gecko/20030922
Description of problem:
This problem was observed on an HP Crestone Peak (ZX4000) IA64 system. It is
unknown at this point if this problem is architecture specific or not.
When the X server comes up only a column of the leftmost (approx) 30 pixels is
visible. It was observed this problem did not manifest itself if during Xserver
initialization the monitor (an HP 2025 Flat Panel) was NOT attached (FYI, this
can be a common occurance when using KVM's). A copy of the XFree86 log file was
captured for both the success and failure cases (attached). It was observed that
only significant difference in the log files was in the failure case EDID
monitor data was read from the monitor. Note, the monitor data cannot be read
from the monitor when the monitor is not attached as would be the case when a
KVM is in use and switched to another system.
The preferred configuration initialization is for the Xserver to "auto"
configure by reading device data reported by the device, therefore the EDID data
should be used, but it appears the EDID data is causing the problem, this makes
this a serious issue because auto configuration produces a non-working system.
Initial analysis of the log files does not reveal how the EDID data is creating
a problem. In both instances the same Horizontal and Vertical frequencies are
being used, there is a difference in the pixel clock, but it looks within range.
Just filing this bug so I can come back to it analyze more fully later.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: missing 95% of display
Expected Results: 100% of display visible
Created attachment 95173 [details]
log file when only leftmost pixels are visible
Created attachment 95174 [details]
log file without monitor attached during init, correct display
Created attachment 95175 [details]
diff between bad and good log files
Just adding this here for easy reference when bug scanning..
(--) RADEON(0): Chipset: "ATI FireGL Z1/X1 AG (AGP)" (ChipID = 0x4147)
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to Red
Hat Enterprise Linux 4.
Setting status to "CURRENTRELEASE".