[Bug 16441] Display is washed out on 2nd monitor - ATI ES1000 chipset

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=16441





--- Comment #33 from Alex Deucher <agd5f at yahoo.com>  2008-09-12 00:53:17 PST ---
(In reply to comment #32)
> 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 ""

If you are tryign to use xrandr remotely (via ssh for example), you'll need to
either set the DISPLAY env var or specify the display to connect to on the
xrandr command line (see xrandr --help).  Most xinit scripts should take care
of this.  Try running xrandr from xterm or gnome-terminal or whatever X
terminal app you are using.

> 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!)

Great!

> 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.

Right.  If there is nothing attached to an output the driver doesn't turn it on
by default to save power and because it doesn't know what resolutions/refresh
rates may or may not be safe to enable on whatever potential monitor could
attached.   You also have cases like DVI-I where you don't know whether the
attached monitor is digital or analog and hence which encoder to driver the
connector with.

> Connecting the monitor does not resolve the issue. Stays blank.

Right.  You'll need to tell the driver (via xrandr) to re-detect the outputs. 
Either run 'xrandr --auto' to redetect the attached monitors or force the
output on as per comment #13.

> 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?

The driver attempts to pick a default output if nothing is connected.  See this
page for forcing static configurations in your xorg.conf (it's also a good
general info page about xrandr):
http://wiki.debian.org/XStrikeForce/HowToRandR12

> 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 :(

You can either force a static config in your xorg.conf or run 'xrandr --auto'
to redetect attached monitors at run time.

> 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)

I'm not sure I follow you.  In the log you attached in comment #30, the driver
is able to get an EDID from VGA-1.  So either you didn't have a monitor
attached when you started X, or the driver isn't able to get an EDID from
VGA-0.  In the log Adalbert attached in comment #18 the driver is able to
properly get an EDID from both monitors.  Also you mentioned that VGA-0 works
if a monitor is connected in comment #32 so presumably it's able to get an EDID
in that case, so DDC seems to be working on both ports.  The EDID comes from
the monitor so if there is no monitor connected, the driver will not able to
get one for that port.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.