On 11/17/2012 11:13 PM, Willem van Asperen wrote:
I have now git cloned from
git://anongit.freedesktop.org/openchrome/xf86-video-openchrome and
compiled / installed.
This version still does not see my TV being connected:
|...||
||[ 3808.281] (II) CHROME(0): Output VGA-1 using monitor section Monitor0||
||[ 3808.281] (II) CHROME(0): ViaVT162xDetect||
||[ 3808.281] (II) CHROME(0): I2C device "I2C bus 2:VT162x" registered
at address 0x40.||
||[ 3808.282] (--) CHROME(0): Detected VIA Technologies VT1625 TV Encoder||
||[ 3808.282] (II) CHROME(0): ViaVT162xInit||
||[ 3808.283] (II) CHROME(0): Output TV-1 has no monitor section||
||[ 3808.283] (II) CHROME(0): VT162xSave||
||[ 3808.383] (II) CHROME(0): I2C device "I2C bus 1:ddc2" registered at
address 0xA0.||
||[ 3808.390] (--) CHROME(0): Test for CRT with VSYNC||
||[ 3808.390] (II) CHROME(0): EDID for output VGA-1||
||[ 3808.390] (II) CHROME(0): VT1625DACSense||
||[ 3808.395] (WW) CHROME(0): VT1625: Unknown cable combination: 0x03D.||
The line above is the issue.
How is your TV connected to the board ? Composite ? S-video ? RGB ?
YCbCr ? Also, what is configured in the bios for the TV output ? Does
that match ?
There's still something weird here, but it might be a difference between
VT1625 and VT1625S.
When applying the patch, the driver "sees" my TV-1 being connected, but
still just makes X quit:
This is not expected to work. I suggested to force the VGA port
detection because there is a known problem with DVI-A, which can be
worked around with such a hack. The TV port is a different story.
Regards,
Xavier
_______________________________________________
Openchrome-users mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/openchrome-users
Main page: http://www.openchrome.org
Wiki: http://www.openchrome.org/trac/wiki/TOC
