[mythtv-users] Firewire issues w/ 0.21 in Mythbuntu 8.10

Jason spuppet at comcast.net
Wed Nov 26 14:30:33 UTC 2008


>>> OK, so I just setup my firewire connection between my Motorola DCT-3412
>>> STB and my Myth box (Mythbuntu 8.10, obviously).  I have the card setup,
>>> the lineups setup, and can tune the channels.  Everything seems to look
>>> OK via plugreport too.  But when I just tried to start a recording on an
>>> HD channel only available via Firewire, and I get the following errors
>>> in my backend log:
>>>
>>> 2008-11-24 21:00:17.491 LFireDev(00159AFFFE163F4A): 
>>> SignalReset(173->174)
>>> 2008-11-24 21:00:17.506 LFireDev(00159AFFFE163F4A):
>>> SignalReset(173->174): Updating device list -- begin
>>> 2008-11-24 21:00:17.807 LFireDev(00159AFFFE163F4A):
>>> SignalReset(173->174): Updating device list -- end
>>> 2008-11-24 21:00:17.859 LFireDev(00159AFFFE163F4A), Warning: No Input in
>>> ...
>
> I just looked at that post and, while it describes my problem almost
> exactly, it says that a kernel higher that 2.6.23 has it fixed.  Well,
> my Mythbuntu 8.10 is 2.6.27 so I'm not sure why I'm still having the
> issue.  Could there be some old 1394 modules or something causing some
> issues?
>
> Also, if I can't get this working, would adding an HDHomeRun help?  I
> was thinking about adding one anyway, but some shows that I record are
> on channels like Sci-Fi HD and USA HD, and to the best of my knowledge,
> those are only available through the firewire due to the 5C encryption.
> Looks like I'm at Comcast's mercy, huh?  ;-)

I still see these errors in the logs after having moved forward one or two 
kernel releases since the original posts.  The stability improved greatly 
after those original posts, though.

The problems I do see come in two flavors:

1)  Firewire unable to get input on the firewire device.  This is sometimes 
caused by encryption being present on a channel.  (My favorite part is the 
DOS it tries on the system by attempting to fill my disk because it never 
stops trying to lock the signal.)

2)  The node for the DCT-34xx changes over time.  I'm not sure what causes 
this, but it appears that it just switches nodes (0 -> 1 or 1 -> 0).  Myth 
doesn't pick this up and starts failing recordings.  I wrote a script to 
email me when recordings fail (on any of my tuners) and I just usually 
restart everything.

Jason 



More information about the mythtv-users mailing list