[Bug 16441] Display is washed out on 2nd monitor - ATI ES1000 chipset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 11 03:20:12 PDT 2008
http://bugs.freedesktop.org/show_bug.cgi?id=16441
--- Comment #31 from Alex Deucher <agd5f at yahoo.com> 2008-09-09 22:52:41 PST ---
(II) RADEON(0): Output VGA-1 connected
(II) RADEON(0): Output VGA-0 disconnected
(II) RADEON(0): Output VGA-1 using initial mode 1024x768
The driver is not able to detect a monitor attached to the second output so it
does not turn the output on. You can use xrandr to force the output on:
xrandr --addmode VGA-0 1024x768
xrandr --output VGA-0 --mode 1024x768
--- Comment #32 from Geoff N <geoff at linuxsolve.co.uk> 2008-09-11 03:20:11 PST ---
Tried the xrandr commands and both returned:
"Can't open display".
Tried xhost + (in case it was an X security issue) and it returned:
unable to open display ""
VGA-0 is being picked up correctly if there is a monitor connected (without the
bleaching - so the driver path in combination with the BIOS upgrade have
worked!)
If there is no monitor connected, then the following message (as you found) is
in the Xorg.0.log =>
(II) RADEON(0): Output VGA-0 disconnected.
Connecting the monitor does not resolve the issue. Stays blank.
VGA-1 which is the other VGA output for the ES1000 does not have a monitor
connected but it always is connected in the X server start.
Can we force VGA-0 in xorg.conf to do similar?
At this point, we almost have a working system. We just have to ensure that the
monitor is powered on and connected when the blade with the ATI ES1000 boots.
Non-ideal but workable :(
Also, could this be a vendor issue as the EDID / I2C info is not being detected
for VGA-0 but it is for VGA-1 (even when both monitors disconnected)? (See
previous Xorg.0.log)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the xorg-driver-ati
mailing list