[mythtv-commits] Ticket #5278: Firewire Uses Bad Port Number and Fails

[MythTV]

#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
 Reporter:  scottadmi at gmail.com  |        Owner:  danielk 
     Type:  defect               |       Status:  assigned
 Priority:  minor                |    Milestone:  unknown 
Component:  mythtv               |      Version:  0.21    
 Severity:  medium               |   Resolution:          
  Mlocked:  0                    |  
---------------------------------+------------------------------------------

Comment(by daver):

 I'm seeing the same problem with a DCH3200 HD cable box using a Firewire
 connection into a Ubuntu Hardy dedicated backend box running the mythtv-
 backend package (0.21.0+fixes16838).

 I have the Firewire Capture Card Setup configured using the built-in
 DCH-3200 settings with a Broadcast connection at 100 Mbps and both signal
 and tuning timeouts set at 4000 ms.

 Similar to what others have reported above, every day or two (5-10
 Firewire recordings, although there doesn't seem to be any consistency in
 this) I get the above LAVCInfo() and TVRec() errors and the Reverting to
 kState_None.  I think this usually follows a long series of "Warning: No
 Input in xxx msec..." warnings from LFireDev and subsequent "ResetBus" and
 "SignalReset" messages.  As has been reported by others above, simply
 stopping and restarting the backend seems to fix the Firewire after it
 fails.

 I also have two pcHDTV cards for unencrypted cable signals that are rock
 solid, so the rest of the system works great.

 Please let me know if there has been any progress on this issue.  Very
 frustrating to miss recordings.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:10>
MythTV <http://www.mythtv.org/>
MythTV