<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 12/09/2011 05:10, Craig Huff wrote:
<blockquote
cite="mid:CAO0hLGoO7q=DKsR0C1NSp4W2TH4EhoXP945U3a_BBk8+9tRWmg@mail.gmail.com"
type="cite">
<pre wrap="">On Sun, Sep 11, 2011 at 2:04 PM, Craig Huff <a class="moz-txt-link-rfc2396E" href="mailto:huffcslists@gmail.com"><huffcslists@gmail.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">After more creative googling, it appears that my problem might be
curable, but I need advice on the best way to get this fixed.
First, here's my configuration:
Combined FE/BE based on Asus A8N-SLI Premium (socket 939)
motherboard recently upgraded to Athlon 64 X2 3800+ CPU; O/S on an IDE
drive and video recordings on three SATA-II drives; video capture via
a pair of PVR-500s hooked up to Comcast DTAs.
I also have a couple of remote FEs, which only enter into the
picture in that I need to keep them in sync version-wise.
Programming updates from Schedules Direct.
All systems are running the initial release without updates of
MythBuntu 10.04:
$ mythbackend --version
Please include all output in bug reports.
MythTV Version : 24158
MythTV Branch : branches/release-0-23-fixes
Network Protocol : 56
Library API : 0.23.20100314-1
QT Version : 4.6.2
Up until I upgraded from a single-core Athlon CPU to the dual-core
one, I had no problems with dma timeouts, but since then they've been
popping up at random times with no discernible pattern.
According to this thread,
<a class="moz-txt-link-freetext" href="http://www.gossamer-threads.com/lists/ivtv/users/41409?search_string=dma%20timeout;#41409">http://www.gossamer-threads.com/lists/ivtv/users/41409?search_string=dma%20timeout;#41409</a>,
I need to update my kernel, which is currently 2.6.32-21-generic, to
something newer, like 2.6.37.4.
If I am correctly reading the information on the MythBuntu web pages,
such as <a class="moz-txt-link-freetext" href="http://www.mythbuntu.org/node/349">http://www.mythbuntu.org/node/349</a>, and
<a class="moz-txt-link-freetext" href="http://www.mythbuntu.org/repos">http://www.mythbuntu.org/repos</a>, enabling these updates (which I
haven't done up till now), won't fix this problem because they only
update MythTV and/or MythBuntu-specific software.
In short, what is the least painful way to resolve the immediate
problem with dma timeouts, given that MythTV 0.25 / MythBuntu 11.10
will be out in just another couple of months and the next LTS release
is due out next Spring. Can I upgrade the kernel while staying with
MythTV 0.23? Can I upgrade to MythTV 0.24 without consuming a weekend
fixing and tweaking (maintain high WAF)? Can I get to MythTV 0.24
using the MythBuntu update repos? Note: all previous updating of my
MythTV system (starting with a FC6 build based on Jarrod's excellent
HOWTO and my eventual migration to MythBuntu 10.04) has been done by
building a completely new system on an extra disk and then migrating
the mysql database from the old one once I had fixed all the quirks
that almost inevitably popped up, so I have never "simply" updated a
running MythTV system.
Anything pertinent I left out?
Any advice welcome.
Craig.
</pre>
</blockquote>
<pre wrap="">
Oh, yeah, I use MythWelcome / MythShutdown on all my systems and would
not want to give it up or kill the WAF because of on-going problems
with it. Haven't been keeping up with the threads on the subject, so
not sure if MythWelcome / MythShutdown have gotten problems introduced
in updates since MythTV 0.23 or it is down to problems people have
figuring out how to configure it.
Craig.
_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a>
</pre>
</blockquote>
<br>
I am running Mythbuntu 10.04 LTS and MythTV 0.24/fixes using the
Mythbuntu Repos. From memory the upgrade from 0.23 was painless. I
cant remember any major issues, the only issue I remember was with
my MBE which runs Ubuntu 10.04 Server and no X11, I had to install
mythfrontend in order to set the Language options, before being able
to get into mythtv-setup.<br>
I have recently update the kernel on my machines to 2.6.38-10
using;<br>
<br>
<span class="Apple-style-span" style="color: rgb(70, 70, 70);
font-family: verdana, Arial, Helvetica, sans-serif; font-size:
12px; font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: 21px; orphans: 2;
text-align: left; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); ">
<pre style="font: normal normal normal 1.1em/normal 'Courier New', Courier, Fixed; overflow-x: auto; overflow-y: auto; margin-top: 0px; margin-right: 0px; margin-bottom: 18px; margin-left: 0px; padding-top: 4px; padding-right: 4px; padding-bottom: 4px; padding-left: 4px; border-top-width: 1px; border-right-width: 1px; border-bottom-width: 1px; border-left-width: 1px; border-top-style: dashed; border-right-style: dashed; border-bottom-style: dashed; border-left-style: dashed; border-top-color: rgb(204, 204, 204); border-right-color: rgb(204, 204, 204); border-bottom-color: rgb(204, 204, 204); border-left-color: rgb(204, 204, 204); font-family: Courier, Monaco, monospace; ">sudo add-apt-repository ppa:kernel-ppa/ppa
sudo apt-get update
sudo apt-get install linux-headers-generic-lts-backport-natty linux-image-generic-lts-backport-natty</pre>
</span> I was unable to get the nvidia drivers to function with
the new kernel on 10.04 though. On the machines that run nVidia
cards, I reverted back to the 2.6.32-34 kernel. I did not spend
much time trying to get the nVidia driver operating though.<br>
I run MythWelcome / MythShutdown on the FE, the only Issue i
have is that the SBE/FE will not shutdown until the entire system is
idle, not just the individual system. <br>
<br>
Michael.<br>
<br>
<br>
</body>
</html>