[mythtv-users] Upgrade from 0.26 to 0.27 broke firewire

[Jean-Yves Avenard]

On 26 June 2014 13:01, DaveD <mythtv at guiplot.com> wrote:
> I have a master BE/FE system that's never missed a show in several years
> until I upgraded my system.  I went from Fedora 17 to Fedora 20, which
> upgraded Myth from 0.26 to 0.27.  The firewire of F17 was already the newer
> "juju"  drivers, reference at http://www.mythtv.org/wiki/FireWire, but it's
> hard to say what else might have "upgraded".
>
> It works for quite some time before crapping out (log starts filling with
> "LinuxController recorders/linuxfirewiredevice.cpp:646 (run) -
> LFireDev(0023A3FFFE4EDD2A): No Input in 50 msec..."
> then 100 msec, then 150 msec, etc, until "ResetBus" then it starts over at
> 50 msec).  Today it recorded a one-hour show, then a half-hour show, then
> crapped out 10 minutes into the second half-hour show.  This is typical.
> Some times it craps out early in the first show.  Once it even got all three
> one day, then crapped out the next day.  Once it craps out, I have to
> restart the backend.  Whatever that does, it makes it work again for a
> while. I've watched hours of "Live" TV over the firewire and it never
> crapped.  Only on scheduled shows, usually near the beginning of a show.
>
> Why can't Myth "reset" the connection the way restarting the backend does?
> (that's a bit rhetorical, since it shouldn't need to if it worked like 0.26
> did, but still...)
>

there's been ZERO change on anything related to firewire between 0.27 and 0.27

> I'm looking for advice (other than "get a cable card").  Something has
> changed, and not for the better.

if something has changed, it's not in myth.

I'm not saying there's no problem in myth, all your upgrade may have
revealed a corner case that cause myth to now fail.

But if it fails with 0.27, it would also fail with 0.26