Bug 10694

Summary:

[965 DDC] DDC failure with Samsung 173s

Product:

xorg

Reporter:

Artur Flinta <aflinta>

Component:

Driver/intel

Assignee:

Artur Flinta <aflinta>

Status:

RESOLVED INVALID

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

CC:

michael.fu

Version:

unspecified

Keywords:

NEEDINFO

Hardware:

x86 (IA32)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Bug Depends on:

Bug Blocks:

13027

Attachments:

Description	Flags
test patch	none

Description Artur Flinta 2007-04-20 14:22:59 UTC

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.

Tested also with xserver 1.3.0.0 and Intel driver 2.0.0 - still without success.

Comment 1 Jesse Barnes 2007-10-31 13:30:47 UTC

Any luck with the latest server & driver bits?  There have been lots of changes since 1.9.94.

Comment 2 Artur Flinta 2007-11-03 15:07:24 UTC

Nope, I'm using now Ubuntu 7.10 and Intel driver version 2.1.1 - still the same effect.

Comment 3 Hong Liu 2008-01-21 18:36:22 UTC

Created attachment 13848 [details] [review]
test patch

Sorry for the long latency...

It seems the i2c client device doesn't respond to driver's request when driver sends out the client slave address.

Would you please have a try on this patch?

If it still fails, please change the line
#define I2C_DEBUG 0 to #define I2C_DEBUG 1 in xf86-video-intel/src/i830_i2c.c file and attach the log.

Thanks,
Hong

Comment 4 Hong Liu 2008-01-21 18:38:08 UTC

one more question: could you please try with other monitors to see if problem exists?

Comment 5 Michael Fu 2008-01-28 19:14:33 UTC

it seems we lose connection with the reporter. reject this bug.. please reopen with rspones to comment# 3 and 4.

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.