You could try running the sa3250_fixer script after the change channel script inside of another script. I think that worked for me before my previous sa3250 box died on me. My current one doesn't need this step though.
<br><br><div><span class="gmail_quote">On 8/16/07, <b class="gmail_sendername">Gregg</b> <<a href="mailto:3gemail@gmail.com">3gemail@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>>> I tried firewire_tester while watching tv and it failed.<br>>>> As soon as I exited watching, it worked.<br>>>><br>>>>So does that mean that mythbackend should not lock the firewire port
<br>>>>when mythtv is not using it??<br><br>>I would say so<br><br>>>And if so could it be a bug in the<br>>>version I installed from atrpms?<br><br>>works for me<br><br>>Are you sure the mythtv-setup matches the working mode (p2p/broadcast)?
<br><br>>>Or is there a setting to tell it not<br>>>to use the port when it is not recording like DVB has?<br><br>>haven't seen it<br><br>Strange. After I unloaded the 1394 drivers and reloaded them I get
<br>success when mythbackend is running. Now I found that the recording<br>only fails when Mythtv has to change the channel to record. I<br>verified it is set to p2p in mythtvsetup. Any suggestions?<br><br>-Gregg<br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br>