<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#c234">Comment # 234</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:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>Hi Justin, Thank you very much for trying out the patch. It appears that I2C bus 3 is not showing anything. _____________________________________________________________________ . . . (II) CHROME(0): Entered via_dvi_init. (--) CHROME(0): VT1632A found on I2C Bus 3. (II) CHROME(0): I2C device "I2C Bus 3:VT1632A" registered at address 0x10. (II) CHROME(0): Entered via_vt1632_probe. (II) CHROME(0): Vendor ID: 0x0000 (II) CHROME(0): Device ID: 0x0000 (--) CHROME(0): VT1632A DVI transmitter not detected. (II) CHROME(0): Exiting via_vt1632_probe. (II) CHROME(0): I2C device "I2C Bus 3:VT1632A" removed. (II) CHROME(0): Exiting via_dvi_init. . . . _____________________________________________________________________ If VT1632A were found, it will display Vendor ID of 0x1106 and Device ID of 0x3192. Instead, you got 0x0000 back for both. If I were to speculate, what this can mean is that I2C bus 3 is not functioning in HP T5550, or is not present. It appears that something is connected to I2C bus 1, so maybe if I2C bus 1 is used for dealing with VT1632A and DVI-D. I will try to get a patch in the next few days that will utilize I2C bus 1 for VT1632A detection.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>