Bug 1376

Summary:	DDC Version 1.0 monitors won't auto configure
Product:	xorg	Reporter:	neil macphail <neil.macphail>
Component:	Server/General	Assignee:	Xorg Project Team <xorg-team>
Status:	RESOLVED WORKSFORME	QA Contact:	Xorg Project Team <xorg-team>
Severity:	minor
Priority:	high	CC:	erik.andren, libv
Version:	unspecified
Hardware:	x86 (IA32)
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description neil macphail 2004-09-14 09:14:13 UTC

Monitor KTX Bridge BGA00 not configured correctly. KTX DDC is Version 1.0 EIDE
and only returns Supplier and Model Number and DDC version number with week and
year of manufacture. Xorg assumes 0 strings in 128 byte block read from monitor
are clock settings and refuses xorg.conf settings as out of the range read.
Windows uses monitor.inf files to look up clock settings using DDC V1.0 supplier
and Model number data as this cannot be read from the monitor. Suggest check
version number and then copy windows method or set "NoDDC" The problem was
definitely in grope and configuration as if I initialised using a Belinea
monitor I could replug to the KTX and all modes worked. Workaround was to set
"NoDDC" a parameter missing in the documentation.

Comment 1 Erik Andren 2006-04-16 20:55:52 UTC

Are you still having the same issue with a current version of xorg?

Comment 2 Luc Verhaegen 2006-04-16 21:32:11 UTC

When EDID 1.0 doesn't get implemented, then this should get ignored completely,
as i'm not sure that that is the current behaviour, from the bug.

This is indeed where a monitor DB is the only solution, when it does get
implemented.

Comment 3 Luc Verhaegen 2006-04-16 21:42:27 UTC

Anyway, do please provide a log of a run with the older monitor attached.

Comment 4 Erik Andren 2006-04-28 19:51:27 UTC

Ping to the bug submitter!

Comment 5 neil macphail 2006-05-02 04:41:21 UTC

Sorry, I now have an LCD at this late date, so I can't provide any more data.
Cheers N

Comment 6 Luc Verhaegen 2006-05-02 05:26:51 UTC

This is one of those things where the problem clearly persists, even if the
reporter no longer has the hardware to test it. Shoving it under the rug will
mean that it'll pop up anyway at a later time.

I'm seriously dropping severity, but should remain open until either DDC 1.0
gets ignored properly, or until this gets handled by a monitor database.

Comment 7 Daniel Stone 2007-02-27 01:24:07 UTC

Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.

Comment 8 Adam Jackson 2010-05-06 13:09:02 UTC

I've run X on EDID 1.0 monitors.  It works fine.  We'd need to see the actual EDID block to know if there's a real issue here.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.