<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c298">Comment # 298</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a> from <a class="email" href="mailto:huangran@iscas.ac.cn" title="HuangRan <huangran@iscas.ac.cn>"> HuangRan</a> <pre>Hi Kevin, With my experiment with drm-openchrome kernel(KMS enabled if using this kernel) just now, I found DVI-D from DVI-I interface on V90LE is working for latest DDX(xf86-video-openchrome) code. That is good! The failure case I mentioned before is using non drm-openchrome kernel. At least, right now, we found a working way to make V90LE worked with DVI-D port. Furthermore, on V90LE, VT1632 chip is used. So I think current code for VT1632 takes effect although I am not doing debugging to verify this point. But for VGA port on V90LE, the case is still same. No EDID is probed out. As you wrote below, it seems I2C bus didn't probe EDID for current VGA port from DVI-I interface. Thanks, Frank (In reply to Kevin Brace from <a href="show_bug.cgi?id=91966#c297">comment #297</a>) > > > 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>