[Openchrome-users] issue on VIA EPIA EX10000EG using openchrome

Willem van Asperen willem at van.asperen.org
Wed Nov 21 14:55:36 PST 2012


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.
I have set the BIOS to TV only and only enabled the S-Video output.
Blank black screen with these lines in the Xorg.0.log:
|
||...||||||
||[    46.863] (II) CHROME(0): ViaOutputsDetect||
||[    46.863] (==) CHROME(0): LVDS-0 : Digital output bus width is 12
bits.||
||[    46.863] (==) CHROME(0): LVDS-0 : DVI Center is disabled.||
||[    46.863] (==) CHROME(0): LVDS Panel will not be forced.||
||[    46.863] (==) CHROME(0): Panel size is not selected from config
file.||
||[    46.863] (II) CHROME(0): Output VGA-1 using monitor section Monitor0||
||[    46.864] (II) CHROME(0): ViaVT162xDetect||
||[    46.864] (II) CHROME(0): I2C device "I2C bus 2:VT162x" registered
at address 0x40.||
||[    46.865] (--) CHROME(0): Detected VIA Technologies VT1625 TV Encoder||
||[    46.865] (II) CHROME(0): ViaVT162xInit||
||[    46.865] (II) CHROME(0): Output TV-1 has no monitor section||
||[    46.865] (II) CHROME(0): VT162xSave||
||[    46.965] (II) CHROME(0): I2C device "I2C bus 1:ddc2" registered at
address 0xA0.||
||[    46.969] (II) CHROME(0): ViaDisplayDisableCRT||
||[    46.969] (II) CHROME(0): EDID for output VGA-1||
||[    46.969] (II) CHROME(0): VT1625DACSense||
||[    46.974] (WW) CHROME(0): VT1625: Unknown cable combination: 0x03D.||
||[    46.974] (II) CHROME(0): EDID for output TV-1||
||[    46.974] (II) CHROME(0): Output VGA-1 disconnected||
||[    46.974] (II) CHROME(0): Output TV-1 disconnected||
||[    46.974] (WW) CHROME(0): No outputs definitely connected, trying
again...||
||[    46.974] (II) CHROME(0): Output VGA-1 disconnected||
||[    46.974] (II) CHROME(0): Output TV-1 disconnected||
||[    46.974] (WW) CHROME(0): Unable to find connected outputs -
setting 1024x768 initial framebuffer||
||[    46.974] (II) CHROME(0): Using default gamma of (1.0, 1.0, 1.0)
unless otherwise stated.||
||...|

There is nothing else connected but the TV on the S-Video port.
This board used to work with release 0.2.906.

>> 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.
Clear. So that is not an option.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openchrome-users/attachments/20121121/bee4e68d/attachment-0001.html>


More information about the Openchrome-users mailing list