<html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 11/22/2012 02:28 PM, Xavier Bachelot wrote: </div> <blockquote cite="mid:50AE2865.1020001@bachelot.org" type="cite"> <pre wrap="">Hi Harry, On 11/22/2012 02:01 PM, Harry de Boer wrote: </pre> <blockquote type="cite"> <pre wrap="">Hi, I recently upgraded my Via machine to the latest Ubuntu and I couldn't get my tv-output to work again. Last night I decided to dive into the code a bit. The first thing I noticed was that vt1625 output sensing seemed broken. Attached is a patch that should fix that. I haven't got it working again yet so there's more to be done. If there is anything I should know before continuing or have any tips please let me know. </pre> </blockquote> <pre wrap="">Thanks for the patch. There's someone with issue with the TV out on an EX board on the -users mailing list and he has trouble with probing the TV out too, so it comes right to the point ;-)</pre> </blockquote> I've applied Harry's patch and it now correctly senses the TV-Out, so good work Harry! The Xorg.0.log looks like: <code> </code><code>...</code><code> </code><code>[ 88186.913] (II) CHROME(0): ViaOutputsDetect</code><code> </code><code>[ 88186.913] (==) CHROME(0): LVDS-0 : Digital output bus width is 12 bits.</code><code> </code><code>[ 88186.913] (==) CHROME(0): LVDS-0 : DVI Center is disabled.</code><code> </code><code>[ 88186.913] (==) CHROME(0): LVDS Panel will not be forced.</code><code> </code><code>[ 88186.913] (==) CHROME(0): Panel size is not selected from config file.</code><code> </code><code>[ 88186.913] (II) CHROME(0): Output VGA-1 using monitor section Monitor0</code><code> </code><code>[ 88186.914] (II) CHROME(0): ViaVT162xDetect</code><code> </code><code>[ 88186.914] (II) CHROME(0): I2C device "I2C bus 2:VT162x" registered at address 0x40.</code><code> </code><code>[ 88186.915] (--) CHROME(0): Detected VIA Technologies VT1625 TV Encoder</code><code> <---- do we have a VT1625? </code><code>[ 88186.915] (II) CHROME(0): ViaVT162xInit</code><code> </code><code>[ 88186.915] (II) CHROME(0): Output TV-1 has no monitor section</code><code> </code><code>[ 88186.915] (II) CHROME(0): VT162xSave</code><code> </code><code>[ 88187.015] (II) CHROME(0): I2C device "I2C bus 1:ddc2" registered at address 0xA0.</code><code> </code><code>[ 88187.022] (--) CHROME(0): Test for CRT with VSYNC</code><code> </code><code>[ 88187.023] (II) CHROME(0): EDID for output VGA-1</code><code> </code><code>[ 88187.023] (II) CHROME(0): Printing probed modes for output TV-1</code><code> </code><code>[ 88187.023] (II) CHROME(0): Modeline "640x480"x63.8 30.00 640 688 744 784 480 488 495 600 -hsync -vsync (38.3 kHz UdP)</code><code> </code><code>[ 88187.023] (II) CHROME(0): Output VGA-1 disconnected</code><code> </code><code>[ 88187.023] (II) CHROME(0): Output TV-1 connected </code><code><---- RESULT!</code><code> </code><code>[ 88187.023] (II) CHROME(0): Using user preference for initial modes</code><code> </code><code>[ 88187.023] (II) CHROME(0): Output TV-1 using initial mode 640x480</code><code> </code><code>[ 88187.023] (II) CHROME(0): VIAFreeScreen</code><code> </code><code>[ 88187.023] (II) CHROME(0): VIAUnmapMem</code><code> </code><code>[ 88187.026] (II) CHROME(0): VIAFreeRec</code><code> </code><code>[ 88187.026] (II) CHROME(0): I2C device "I2C bus 2:VT1625" removed.</code> But, alike my (feeble) attempt when I just forced the TV-Out to state connected, this is where the log ends and X just disappears. <blockquote cite="mid:50AE2865.1020001@bachelot.org" type="cite"> <pre wrap=""> There are 2 variant of the VT1625 (VT1625 and VT1625S) out in the wild and it seems there are subtle differences between them. One of the difference is one has 4 DACs and the other has 6. They are sharing the same idea so I don't know of a good way to tell one from the other. Fortunately, there are datasheets available for both, it might help you get the TV out working. See <a class="moz-txt-link-freetext" href="http://www.openchrome.org/trac/wiki/Development#TVencoders">http://www.openchrome.org/trac/wiki/Development#TVencoders</a> Out of curiosity, I do have an EX board too (for testing purpose) and mine is using a VT1625S. What's the flavor on yours ?</pre> </blockquote> From the log I tend to think mine is a VT1625, no "S". But I might be mistaken? One more thing I noticed in the log: <code>...</code><code> </code><code>[ 88186.912] (**) CHROME(0): TV Type is PAL.</code><code> </code><code>[ 88186.912] (**) CHROME(0): TV Output Signal is S-Video.</code><code> </code><code>[ 88186.912] (==) CHROME(0): No default TV output port is set.</code><code> <--- so? </code><code>...</code> Could this be an issue? And if so, how to fix this? I have set the BIOS to use TV only and only enabled the S-Video output. Finally, my xorg conf says: <code> </code><code>Section "Monitor"</code><code> </code><code> Identifier "Monitor0"</code><code> </code><code> HorizSync 30 - 50</code><code> </code><code> VertRefresh 50.0 - 50.0</code><code> </code><code>EndSection</code><code> </code><code> </code><code>Section "Device"</code><code> </code><code> Identifier "Device0"</code><code> </code><code> Driver "openchrome"</code><code> </code><code> Option "ActiveDevice" "TV"</code><code> </code><code> Option "TVType" "PAL"</code><code> </code><code> Option "TVOutput" "S-Video"</code><code> </code><code>EndSection</code><code> </code><code> </code><code>Section "Screen"</code><code> </code><code> Identifier "Screen0"</code><code> </code><code> Device "Device0"</code><code> </code><code> Monitor "Monitor0"</code><code> </code><code> SubSection "Display"</code><code> </code><code> Viewport 0 0</code><code> </code><code> Modes "720x576" "720x576Noscale"</code><code> </code><code> EndSubSection</code><code> </code><code>EndSection</code> Yet, the X log, as you can see above, says: <code> </code><code>[ 88186.915] (II) CHROME(0): Output TV-1 has no monitor section</code><code> </code> But it does... And: <code>[ 88994.747] (II) CHROME(0): Output TV-1 using initial mode 640x480</code> Which should be 720x576, the PAL mode, as indicated in the conf. Hope this helps. If there is anything more I can test, please let me know! Regards, Willem </body> </html>