Bug#243575: X configuration should allow to let out monitor frequencies and allow DDC to get them.
On Thu, Nov 11, 2004 at 05:23:19AM -0800, Daniel Stone wrote:
> On Thu, Nov 11, 2004 at 01:24:57PM +0100, Sven Luther wrote:
> > On Thu, Nov 11, 2004 at 03:57:31AM -0800, Daniel Stone wrote:
> > > On Thu, Nov 11, 2004 at 12:50:11PM +0100, Sven Luther wrote:
> > > > I would recomend that the X debconf questions about monitor frequencies allow
> > > > for the entering of an empty string, which would leave out the frequency
> > > > option of the config files, and the text above it be modified to inform the
> > > > user that he can let this entries blank if he has a monitor capable of DDC.
> > >
> > > Yes, and I believe these questions should not even be asked per default.
> > Notice that only x86 has read-edid, so there is hardly a way not to ask these
> > questions. Furthermore, just leaving the frequency lines out breaks horribly
> > for the older monitor with broken or inexistend DDC/EDID support.
> amd64, i386 and powerpc have working DDC probe support (the former two
Nope, powerpc has not, it seems to be only some way of getting the information
from the openfirmware probed data, which will work if the graphic card does
indeed provide it, which is probably only the case on apple with the apple
standard cards. In particular, it fails on my pegasos, and probably also on
all IBM RS6k machines.
> via VESA's VBE, the latter via /proc), and there are very, very, very,
> very, very, very, very few monitors out there that people actually use
> that don't have working DDC/EDID. Trust me, I've been there, and found
He, i have encountered this case at least 5 times this past month. Ranging
from cheap monitors, which altough they claim to do DDC/EDID, they only send
bogus data to the card, one case was even missing the Ranges fields, or
age-old big sun monitors, or even people behind cheap KVM switches, which
don't relay the DDC pins. All those i have encountered.
Now, X clearly knows how to get the DDC info on most plateforms, should it not
be easiest to have some kind of X based tool which probes the DDC info, and
reports back if it worked. Hell i guess running X in -probeonly, and parsing
the XFree86.0.log file should be a cheap way of doing that.