[mythtv-users] 0.26 and Fedora 18 crash-n-burn?

[Rich West]

On 4/13/2013 3:50 PM, HP-mini wrote:
> On Sat, 2013-04-13 at 13:01 -0400, Rich West wrote:
>> Well, I was wrong about the permissions, kernel drivers, kernel rev, and,
>> well, pretty much all of the little issues.  So far, I've gone down several
>> different rabbit holes, and in every situation, 0.26 blows up because of one
>> reason or another.  I'm wondering if it is the RPMfusion build vs the ATrpms
>> built, but now I am grasping at straws.
>>
>> My latest incarnation is a fresh install of Fedora18, installing 0.26 from
>> RPMfusion via RPMS, copying over my mythtv database, deleting all of the
>> tuners via mythtv-setup, adding them all back in, and attempting to run.
>>
>> Now, I get new errors.  Egads!  Mythtv complains that the PVR-150 tuners are
>> generating an error (nothing more about the error) and when I check the
>> card, it's hung.  Further tests showed that the card would hang only if
>> mythtv were to touch it.  Running "cat /dev/video0 > test.mpg" for a minute
>> or so generated an mpg file that mplayer would happily play.  Once I fired
>> up mythbackend and it attempted to record, it would generate that error and
>> the card was now hung.
> This pops up..
> http://www.mythtv.org/pipermail/mythtv-users/2013-January/345762.html
> The advice was:
>>>> There was a significant fix for PVR-XXX cards that went into master
>>>> and 0.26-fixes and 0.25-fixes on or about 29 November last year
>>>> [2012].  Anyone with one of these cards should ensure they are 
>>>> running reasonable current code.

Thanks!  Reading that post sounds exactly like what I am going through, so
there might be hope yet...

All I can think of, though, is "Oh, great.." :(

I'm running 0.26 via RPMfusion RPMS which are supposedly from April of this
year.  I looked at going back to atrpms, but I'm only seeing 0.25.3 built
back in October over there.  Gahh.. the though of having to go back to
0.25.3 after having upgraded *everything* in the house (that's four clients)
and the database..

ugh.. this.. is.. terrible... doesn't look like I have a lot of options..
downloading the 0.26.0 fixes branch and rolling my own RPM is probably the
better method but equally as painful.