<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#330099">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
Hi Jean-Yves,<br>
<blockquote
cite="mid:%3Ccb44e8370906010244g64bac856n8f9250bab01d3700@mail.gmail.com%3E"
type="cite">
<pre wrap="">Hi
2009/6/1 Robert (MythTV) <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E" href="mailto:mythtv@isolutions.co.nz"><mythtv@isolutions.co.nz></a>:
</pre>
<blockquote type="cite">
<pre wrap="">I can also confirm this exact same issues on my MythTV Boxes as well. (JYA
testing repo)
Running 64 bit (not 32 bit)
A). 2Gb RAM, 200Gb system disk, 400Gb dedicated recording disk.
B). 8Gb RAM, 400Gb system disk, 400Gb dedicated recording disk.
Test environments
* Ubuntu 9.04 64 bit (GNOME with Compiz/Composite enabled)
* nVidia VDPAU 185.19
* mythtv - 0.21.0+fixes-svn20649-jya-debug-0ubuntu0
* mythtv - 0.21.0+fixes-20649-openglvdpau-debug-0ubuntu2
</pre>
</blockquote>
<pre wrap=""><!---->
Well, you have a problem here ...
ubuntu2 is an Ubuntu 8.10 package.
</pre>
</blockquote>
Oops my typo! Should be a 0. That's what is reported in Synaptic, also
double-checked the /etc/apt/sources.list with corresp. GPG Key:<br>
deb <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.avenard.org/files/ubuntu-repos">http://www.avenard.org/files/ubuntu-repos</a>
jaunty testing
#<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.avenard.org/">http://www.avenard.org/</a> (MythTV)<br>
<br>
Forgot to add, using an 8600GT 1Gb and a 9600GT 1Gb in the machines for
VDPAU.<br>
<br>
Recently performed the updates to your latest testing build, but
haven't checked it out yet - will hopefully have some time to do so
tonight. If needed I could roll back to a previous version for
comparison.<br>
<br>
Installed:<br>
0.21.0+fixes-20654-openglvdpau-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes-svn20651-jya-debug-0ubuntu0 (jaunty)<br>
<br>
Available:<br>
0.21.0+fixes-20654-openglvdpau-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes-20651-openglvdpau-debug-0ubuntu3 (jaunty)<br>
0.21.0+fixes-20651-openglvdpau-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes-20649-openglvdpau-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes-20550-openglvdpau-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes-20521-openglvdpau-debug-0ubuntu3 (jaunty)<br>
0.21.0+fixes-20521-openglvdpau-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes19961-0ubuntu8 (jaunty)<br>
<br>
Available:<br>
0.21.0+fixes-svn20651-jya-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes-svn20649-jya-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes-svn20550-jya-debug-0ubuntu0 (jaunty)<br>
0.21.0+fixes19556-0ubuntu8 (jaunty)<br>
<br>
<blockquote
cite="mid:%3Ccb44e8370906010244g64bac856n8f9250bab01d3700@mail.gmail.com%3E"
type="cite">
<pre wrap="">So I'm surprised you could run it on a 9.04 system ; and if you did,
no wonder it's not stable...
</pre>
</blockquote>
My error - definitely using Jaunty packages on both machines.<br>
<br>
<blockquote
cite="mid:%3Ccb44e8370906010244g64bac856n8f9250bab01d3700@mail.gmail.com%3E"
type="cite">
<blockquote type="cite">
<pre wrap="">RE: 1). Quick channel changes on my Nova-T 500 DVB-T cause the front end to
crash. [snip]
Additionally, changing channels on the Winfast can now lead to a full system
lockup, [snip]
</pre>
</blockquote>
<pre wrap=""><!---->
Did you enable realtime priority thread ? I've seen lockup with compiz
and realitme priority threa enabled: lock the frontend completely for
30s+ at a time
</pre>
</blockquote>
The frontend doesn't ever recover. S/PDIF output is stuck in a 1 second
"sound loop", no X interface, no terminal windows (CTRL-ALT-F2 / SSH /
etc.), full lockup.<br>
<br>
Realtime priority is enabled, so I'll try it disabled tonight and
report.<br>
<br>
<blockquote
cite="mid:%3Ccb44e8370906010244g64bac856n8f9250bab01d3700@mail.gmail.com%3E"
type="cite">
<blockquote type="cite">
<pre wrap="">RE: 2). I can confirm this happening as well. Speed of channel change is not
an issue for me. I could have been watching a channel (Live TV) for a while,
then change channel, and it fails. After this is appears that the card is
still 'in use' and entirely unavailable. Restarting mythbackend,
mythfrontend, or anything else I've tried does not free up the card again.
Rebooting the machine (power off) appears to be the only solution - which
makes me think it could be a firmware loading issue, or something in the
Nova-T driver itself.
</pre>
</blockquote>
<pre wrap=""><!---->
Sounds more like a driver issue than a myth issue
</pre>
</blockquote>
My thoughts as well - but I'm not certain - this was absolutely stable
in previous versions of MythTV with the same firmware (1.20) for the
Nova-T. A power-off appears to be the only solution, as a "warm state"
Nova-T still doesn't operate properly.<br>
<br>
My boxes exhibit the same issues which Steven is encountering. I'm not
sure if he is able to recover Live TV after the "Error was encountered
while displaying video", but I am entirely unable to restart any Live
TV after this error. Frontend in other aspects still works and
operates fine. No crash/segfaults after this failure.<br>
<br>
Cheers,<br>
Robert.<br>
<br>
</body>
</html>