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

Willem van Asperen willem at van.asperen.org
Tue Nov 20 15:41:12 PST 2012


Installing the Arch package for the "old" driver 0.2.906 fails because
it expects an older version of X.
So I downloaded the source to compile it myself. Alas.
There is a file 'via_accel.c' that expects xaalocal.h, but that file is
not there in the X development files.
I figure this has to do with dropping XAA?
Any clue as to how to work around this error?
Thanks,
Willem

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.||
> ||[  3808.395] (II) CHROME(0): EDID for output TV-1||
> ||[  3808.395] (II) CHROME(0): Output VGA-1 disconnected||
> ||[  3808.395] (II) CHROME(0): Output TV-1 disconnected||
> ||[  3808.395] (WW) CHROME(0): No outputs definitely connected, trying
> again...||
> ||[  3808.395] (II) CHROME(0): Output VGA-1 disconnected||
> ||[  3808.395] (II) CHROME(0): Output TV-1 disconnected||
> ||[  3808.395] (WW) CHROME(0): Unable to find connected outputs -
> setting 1024x768 initial framebuffer||
> ||[  3808.395] (II) CHROME(0): Using default gamma of (1.0, 1.0, 1.0)
> unless otherwise stated.||
> ||...|
>
> When applying the patch, the driver "sees" my TV-1 being connected,
> but still just makes X quit:
>
> |...||
> ||[  4036.653] (II) CHROME(0): Output VGA-1 using monitor section
> Monitor0||
> ||[  4036.654] (II) CHROME(0): ViaVT162xDetect||
> ||[  4036.654] (II) CHROME(0): I2C device "I2C bus 2:VT162x"
> registered at address 0x40.||
> ||[  4036.655] (--) CHROME(0): Detected VIA Technologies VT1625 TV
> Encoder||
> ||[  4036.655] (II) CHROME(0): ViaVT162xInit||
> ||[  4036.655] (II) CHROME(0): Output TV-1 has no monitor section||
> ||[  4036.655] (II) CHROME(0): VT162xSave||
> ||[  4036.755] (II) CHROME(0): I2C device "I2C bus 1:ddc2" registered
> at address 0xA0.||
> ||[  4036.762] (--) CHROME(0): Test for CRT with VSYNC||
> ||[  4036.763] (II) CHROME(0): EDID for output VGA-1||
> ||[  4036.763] (II) CHROME(0): Printing probed modes for output TV-1||
> ||[  4036.763] (II) CHROME(0): Modeline "640x480"x63.8   30.00  640
> 688 744 784  480 488 495 600 -hsync -vsync (38.3 kHz d)||
> ||[  4036.763] (II) CHROME(0): Output VGA-1 disconnected||
> ||[  4036.763] (II) CHROME(0): Output TV-1 connected||<<-- result of
> the HACK
> ||[  4036.763] (II) CHROME(0): Using exact sizes for initial modes||
> ||[  4036.763] (II) CHROME(0): Output TV-1 using initial mode 640x480||
> ||[  4036.763] (II) CHROME(0): VIAFreeScreen||
> ||[  4036.763] (II) CHROME(0): VIAUnmapMem||
> ||[  4036.766] (II) CHROME(0): VIAFreeRec||
> ||[  4036.766] (II) CHROME(0): I2C device "I2C bus 2:VT1625" removed.|
>
> This is the tail of my Xorg.0.log file.
>
> Any ideas what I could test further? Happy to be of help.
>
> Regards,
> Willem
>
> On 11/15/2012 11:35 PM, Willem van Asperen wrote:
>> Hi All,
>>
>> Based on the patch supplied by Xavier I have created the following
>> patch on via_output.c:
>>
>> |343c343,344||
>> ||<     if (ViaTVDACSense(pScrn))||
>> ||---||
>> ||>     // HACK: force TV connected to cater for EPIA board||
>> ||>     //if (ViaTVDACSense(pScrn))||
>> |
>> This makes my TV-1 being seen as "connected", so that's the good news!
>>
>> Xorg.0.log:
>> |...||
>> ||[  4170.999] (II) CHROME(0): Printing probed modes for output TV-1||
>> ||[  4170.999] (II) CHROME(0): Modeline "640x480"x63.8   30.00  640
>> 688 744 784  480 488 495 600 -hsync -vsync (38.3 kHz d)||
>> ||[  4170.999] (II) CHROME(0): Output VGA-1 disconnected||
>> ||[  4170.999] (II) CHROME(0): Output TV-1 connected||<<--- Result!
>> ||[  4170.999] (II) CHROME(0): Using exact sizes for initial modes||
>> ||[  4170.999] (II) CHROME(0): Output TV-1 using initial mode 640x480||
>> ||[  4170.999] (II) CHROME(0): VIAFreeScreen||
>> ||[  4170.999] (II) CHROME(0): VIAUnmapMem||
>> ||[  4171.003] (II) CHROME(0): VIAFreeRec||
>> ||[  4171.003] (II) CHROME(0): I2C device "I2C bus 2:VT1625" removed.||
>> |
>> The bad news is that it makes X go ploof... The above is actually the
>> tail of Xorg.0.log. After this, X just disappears.
>>
>> So there must be more to it.
>>
>> Any thoughts?
>>
>> Regards,
>> Willem
>>
>> On 11/11/2012 11:14 PM, Xavier Bachelot wrote:
>>> Hi Willem,
>>>
>>> On 11/10/2012 01:56 PM, Willem van Asperen wrote:
>>>> I have been running Arch Linux on a VIA EPIA EX10000EG with success
>>>> using version openchrome 0.2.906, until the upgrade of openchrome to
>>>> 0.3.0. Since then my screen just comes up blank black.
>>> I'm using the attached patch with an Epia EX. However, in my case, the
>>> display is connected throught DVI-A using a DVI-to-VGA dongle. I'm not
>>> sure how your board is connected, so that may or may not help.
>>>
>>> Regards,
>>> Xavier
>>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openchrome-users/attachments/20121121/574c2fa1/attachment-0002.html>


More information about the Openchrome-users mailing list