[Bug 16441] Display is washed out on 2nd monitor - ATI ES1000 chipset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 18 03:29:58 PDT 2008
http://bugs.freedesktop.org/show_bug.cgi?id=16441
--- Comment #39 from Geoff N <geoff at linuxsolve.co.uk> 2008-09-18 03:29:55 PST ---
And down the rabbit hole we go.
The TVDACLoadDetect option appeared to work perfectly.
I have been using a KVM for my tests. When I restart X, the trick that rendered
the screen blank previously was to switch to another monitor. The EDID/I2C
would fail and the VGA-0 screen would be disconnected.
After adding the option for TVDACLoadDetect to xorg.conf, switching back to the
screen after X had restarted showed a working screen. Xorg.0.log informed that
the monitor was detected as a Colour CRT and it looked like I had a solution.
However, restarting X without anything connected to VGA-0 didn't detect a
default Colour CRT like the primary DAC. The screen was blank again and VGA-0
disconnected in the log. Seems like the KVM was providing some signalling that
the Driver was picking up even when it wasn't the monitor in focus. After a bit
of hunting around, it appears the KVM connects pins 4 and 11 to ground when the
focus is off that monitor, so that graphics drivers are fooled into thinking a
Colour CRT @ 1024 x 768 is connected.
Turns out our customer may be using a KVM style connection for our blades, so
the problem may well be moot. Would be nice though to force the same behaviour
as the primary DAC in the absence of a connected monitor via this xorg.conf
Device Option.
Thanks again for your help. I might need that patch still (unless you know of
another Device parameter) if the customer's KVM doesn't offer the signalling
mentioned above.
Query - when would you expect the git repo changes you made to xorg-x11-drv-ati
to make their way into the Fedora community updates?
--
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