[Openchrome-devel] [Bug 91966] No signal to monitor with X and openchrome using VX855 chipset graphics
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Mar 28 03:28:35 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=91966
--- Comment #297 from Kevin Brace <kevinbrace at gmx.com> ---
Hi Frank,
In your situation with Wyse V90LE, it appears that OpenChrome is not able to
obtain EDID from I2C bus 1 or 2.
__________________________________________________________________________
. . .
[ 49.929] (II) CHROME(0): NativeMode: 640 407
[ 49.929] (II) CHROME(0): Printing probed modes for output LVDS-1
[ 49.929] (II) CHROME(0): Modeline "640x407"x59.7 20.25 640 664 720 800
407 410 420 424 -hsync +vsync (25.3 kHz)
[ 49.929] (--) CHROME(0): Probing for a VGA monitor on I2C Bus 1.
[ 49.929] (II) CHROME(0): I2C device "I2C Bus 1:ddc2" registered at address
0xA0.
[ 49.936] (--) CHROME(0): Did not detect a VGA monitor on I2C Bus 1.
[ 49.936] (--) CHROME(0): Probing for a VGA monitor on I2C Bus 2.
[ 49.936] (II) CHROME(0): I2C device "I2C Bus 2:ddc2" registered at address
0xA0.
[ 49.940] (--) CHROME(0): Did not detect a VGA monitor on I2C Bus 2.
[ 49.940] (--) CHROME(0): Now perform manual detection of a VGA monitor.
[ 49.940] (II) CHROME(0): EDID for output VGA-1
[ 49.943] (II) CHROME(0): Entered via_vt1632_detect.
. . .
__________________________________________________________________________
If OpenChrome is not able to obtain EDID via I2C bus 1 or 2, the chance of VGA
working is very slim (It is possible it can work if the manual detection
succeeds, but I have never seen this actually working.).
I do not know why EDID is not appearing on I2C bus 1 or 2 for Wyse V90LE.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/openchrome-devel/attachments/20160328/5470d34d/attachment.html>
More information about the Openchrome-devel
mailing list