Red Hat Bugzilla – Bug 150269
DVI panel loses sync when anaconda starts X with unknown monitor type
Last modified: 2007-11-30 17:11:01 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12
Description of problem:
Basically I am using an Apple 17" LCD display with a Radeon 9000 on an older dual proc P3 box. The Radeon 9000 is detected, but the monitor type is set as "unknown", and as soon as it attempts to start X, it shuts down the DVI output from the card and lights the analog one. I tested it by connecting an analog display after it kills the DVI display and it is sending signal to the analog vga output of the card after that. This is a real problem if, like me, you have a DVI-only monitor. I had to hook up the VGA input from my rear projector to confirm this problem, and then had to do the install from the ascii installer.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Connect a DVI-only flat panel of a type unknown to FC3 to a Radeon 9000.
2. Boot from install CD, select graphical installation
3. On start of X, DVI panel will lose sync and analog VGA output on card will light.
Expected Results: There should at least be an installer switch allowing this to be overridden. It should be smart enough to detect that the unknown monitor it probed is connected to the DVI output of the card. It should have a configuration profile for detecting Apple displays.
Note that I am using an Apple display that has the proprietary ADC connector on it, so I am using a separate device to do power injection through ADC. ADC is just DVI with extra pins for power and USB, so all the device does is inject the necessary power and give you a USB and DVI cable on the ends. No signal processing occurs in the device, and windows sees the display as a plain jane 17" digital flat panel.
This bug report scrolls off the right side of the monitor 4 lengths.
Please file a new bug report, with right margin at 72 column or so for
Also, attach your X server config file and log file to the report.
Thanks in advance.
*** This bug has been marked as a duplicate of 151474 ***