<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 05/22/2013 12:13 AM, Willem van
Asperen wrote:<br>
</div>
<blockquote cite="mid:519BF19B.6010505@van.asperen.org" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 05/21/2013 11:17 PM, Harry de Boer
wrote:<br>
</div>
<blockquote cite="mid:519BE479.4070806@ijscoboer.nl" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
After applying the patch by Xavier the latest git works for me.<br>
<br>
Willem, looking at your xorg.0.log, from the following messages
looks like your xorg.conf isn't set up properly anymore:<br>
<pre>[ 344.257] (**) CHROME(0): Option "TVType" "576P"
[ 344.257] (**) CHROME(0): Option "TVOutput" "S-Video"
[ 344.257] (**) CHROME(0): Option "TVPort" "DVP0"</pre>
You should probably set TVType to PAL. But aside from that,
vt1625DACSense should detect a cable anyway after the patch is
applied, are you sure it was connected when you last tried and
the patch was applied correctly?<br>
<br>
- Harry<br>
<br>
<br>
<div class="moz-cite-prefix">On 21-05-13 01:02, <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>
wrote:<br>
</div>
<blockquote
cite="mid:bug-63857-26284-jMbvSIPZwu@http.bugs.freedesktop.org%2F"
type="cite"> <base href="https://bugs.freedesktop.org/">
<p> </p>
<div> <b><a moz-do-not-send="true" class="bz_bug_link
bz_status_ASSIGNED " title="ASSIGNED --- - version 0.3.2
failing on VIA VT3324 (CX700). Card-Ids (1106|3157)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63857#c22">Comment
# 22</a> on <a moz-do-not-send="true"
class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED
--- - version 0.3.2 failing on VIA VT3324 (CX700).
Card-Ids (1106|3157)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63857">bug
63857</a> from <span class="vcard"><a
moz-do-not-send="true" class="email"
href="mailto:willem@van.asperen.org"
title="willem@van.asperen.org">willem@van.asperen.org</a>
</span></b>
<pre>On 05/21/2013 12:25 AM, <a moz-do-not-send="true" href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a> wrote:
>
<span class="quote">> *<a moz-do-not-send="true" href="show_bug.cgi?id=63857#c21">Comment # 21</a> <<a moz-do-not-send="true" class="bz_bug_link
bz_status_ASSIGNED " title="ASSIGNED --- - version 0.3.2 failing on VIA VT3324 (CX700). Card-Ids (1106|3157)" href="show_bug.cgi?id=63857#c21">https://bugs.freedesktop.org/show_bug.cgi?id=63857#c21</a>>
> on <a moz-do-not-send="true" class="bz_bug_link
bz_status_ASSIGNED " title="ASSIGNED --- - version 0.3.2 failing on VIA VT3324 (CX700). Card-Ids (1106|3157)" href="show_bug.cgi?id=63857">bug 63857</a> <<a moz-do-not-send="true" class="bz_bug_link
bz_status_ASSIGNED " title="ASSIGNED --- - version 0.3.2 failing on VIA VT3324 (CX700). Card-Ids (1106|3157)" href="show_bug.cgi?id=63857">https://bugs.freedesktop.org/show_bug.cgi?id=63857</a>> from
> James Simmons <<a moz-do-not-send="true" href="mailto:jsimmons@infradead.org">mailto:jsimmons@infradead.org</a>> *
> Do you know how to use git ? We need to bisect to see where the problem is.
> ------------------------------------------------------------------------
> You are receiving this mail because:</span>
>
<span class="quote">> * You are on the CC list for the bug.
> * You reported the bug.</span>
>
I think I do... I just cloned the latest one, then applied the patch
provided by Xavier, recompiled, re-installed.
Do you want me to try the latest git?</pre>
</div>
<hr> <span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openchrome-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Openchrome-devel@lists.freedesktop.org">Openchrome-devel@lists.freedesktop.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/openchrome-devel">http://lists.freedesktop.org/mailman/listinfo/openchrome-devel</a>
</pre>
</blockquote>
<br>
</blockquote>
I'll give it another go tomorrow.<br>
Could there be an issue with the BIOS settings? I have selected
option DVI+TV, layout COMPOSITE+S-VIDEO, switched on the Composite
and S-Video output ports.<br>
<br>
I'll report back.<br>
<br>
W<br>
</blockquote>
Hi All,<br>
<br>
I've given it another try.<br>
<br>
1. fresh clone from git<br>
2. applied patch - ok<br>
3. make; make install<br>
4. reboot<br>
<br>
At this point there is no TV connected. I can see from the Xorg log
file that it detects that there is no TV connected. There is an DVI
panel connected, though, so I would assume we get an image there.
No. Xorg fails.<br>
<br>
I changed via_output to force detection of the TV, as follows:<br>
<br>
<code>static xf86OutputStatus</code><code><br>
</code><code>via_tv_detect(xf86OutputPtr output)</code><code><br>
</code><code>{</code><code><br>
</code><code> xf86OutputStatus status =
XF86OutputStatusDisconnected;</code><code><br>
</code><code> ScrnInfoPtr pScrn = output->scrn;</code><code><br>
</code><code><br>
</code><code> </code><code><b> /*if (ViaTVDACSense(pScrn))*/</b></code><code><br>
</code><code> status = XF86OutputStatusConnected;</code><code><br>
</code><code> return status;</code><code><br>
</code><code>}</code><br>
<br>
retry: make; make install<br>
reboot<br>
<br>
As soon as we start up X, the box completely freezes. No response to
Ctl-Alt-Del, no ping, no display, nothing...<br>
<br>
Reset the BIOS to default. Reboot. Same thing.<br>
<br>
Moved /usr/lib/xorg/modules/drivers/openchrome_drv.* away.<br>
Changed /etc/X11/xorg.conf.d/10-monitor.conf to have Driver "vesa"
instead of Driver "openchrome". Reboot.<br>
We have a picture!<br>
<br>
The other day, when I tried the patched driver when the box was
connected to a TV set, I had the same freeze. So I conclude:<br>
<br>
a) the detection if there is a TV connected works.<br>
b) there is something else in the TV code that makes the box freeze.<br>
c) with only an DVI device connected, that state is not recognized.<br>
<br>
Freezes like this are hard to debug, I figure, as there is no log to
check.<br>
<br>
Any clues from the community?<br>
<br>
Regards,<br>
Willem<br>
</body>
</html>