DDC, Intel driver and Samsung 173s problems once again.

[Artur Flinta]

Hi!

Having some time, I've back to DDC problems with Intel driver (1.9.94)
on DG965WH MB and Samsung 173s LCD monitor (only analog input). Cause
Xserver during start up doesn't retrieve any useful information via DDC,
I've changed according to Keith suggestions xserver and driver sources:
> If you are up for it, there's a pile of I2C tracing code available in
> both the driver (i830_i2c.c) and the core I2C code
> hw/xfree86/i2c/xf86i2c.c; changing the I2C_TRACE and I2C_TIMEOUT
> macros from /*(x)*/ to (x) will dump piles of debug output to the
> log; perhaps we can sift out why your monitor is failing from that.
( http://lists.freedesktop.org/archives/xorg/2007-March/022606.html )

After starting X I have this in output log:
[...]
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"(II) Module alread ybuilt-in(II) Loading sub
module "i2c"
(II) LoadModule: "i2c"(II) Module alread ybuilt-in(**) intel(0): Option
"PreferredMode" "1280x1024"
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B"
registered at address 0x70.
[I2CRaiseSCL(<SDVOCTRL_E for SDVOB>, 0, 550) timeout](II) intel(0): No
SDVO device found on SDVOB
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C"
registered at address 0x72.
[I2CRaiseSCL(<SDVOCTRL_E for SDVOC>, 0, 550) timeout](II) intel(0): No
SDVO device found on SDVOC
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.

i2c: <[I2CPutByte(<CRTDDC_A>, 0xa0, 40, 2200, 40) timeout]Wa0- >

i2c: <[I2CPutByte(<CRTDDC_A>, 0xa0, 40, 2200, 40) timeout]Wa0- >

i2c: <[I2CPutByte(<CRTDDC_A>, 0xa0, 40, 2200, 40) timeout]Wa0- >

i2c: <[I2CPutByte(<CRTDDC_A>, 0xa0, 40, 2200, 40) timeout]Wa0- >
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
(II) intel(0): EDID for output VGA
(II) intel(0): Not using default mode "640x350" (vrefresh out of range)
(II) intel(0): Not using default mode "640x400" (vrefresh out of range)
(II) intel(0): Not using default mode "720x400" (vrefresh out of range)
[...]
I'm not sure how it can be helpful to solve my problems with DDC info.
Please remember that this monitor was working great (full DDC info) when
using nvidia binary driver with nvidia GF6150 based MB.

Regards
	Artur