I now get the following errors in my log and the firewire_tester -R can't reset the bus properly even if it states it's successful. Please any help would be much appreciated; I just need to get this working. It's like a full time job.
<br><br> ./firewire_tester -v -R -n 0<br>raw1394: Allocating handle, port 0.<br>Action: Resetting the firewire bus<br>Bus reset succeeded<br>raw1394: Releasing handle.<br>[root@Pvr bin]# ./firewire_tester -v -p -n 0<br>raw1394: Allocating handle, port 0.
<br>Action: Test P2P connection 1 times, node 0, channel 0<br>P2P: Creating, node 0, channel 0<br>P2P: Testing...Failed<br>P2P: Disconnecting.<br>raw1394: Releasing handle.<br><br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer
<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer
<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer
<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer
<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:01 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer<br>Nov 23 12:25:01 Pvr kernel:<br>Nov 23 12:25:02 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer
<br>Nov 23 12:25:02 Pvr kernel:<br>Nov 23 12:25:02 Pvr kernel: ohci1394: fw-host0: IR DMA error - packet too long for buffer<br><br><br><br><div><span class="gmail_quote">On 11/22/06, <b class="gmail_sendername">Jim Westfall
</b> <<a href="mailto:jwestfall@surrealistic.net">jwestfall@surrealistic.net</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;">
Eric Smith <<a href="mailto:erictsmith@gmail.com">erictsmith@gmail.com</a>> wrote [11.22.06]:<br>> On a side note, on the firewire_tester front, I did some more testing<br>> last night outside of myth to try to get a better understanding of
<br>> what was going on. It seems there is something "different" about my<br>> TNT HD channel 1460 that allows the firewire port to reenable (there<br>> may be other channels as well, but i focused on testing this theory
<br>> against that one).<br>><br>> To test i would purposefully hit a few channels that i knew would<br>> disable the firewire, then would try to run the sure_change script to<br>> an available HD channel. Sure_change would fail with no firewire data
<br>> received about 75% of the time. However, if i used 1460, i had a 100%<br>> success rate with the channel change.<br><br>I would try adding firewire_tester -R right after the sure_change script<br>runs the channel changer. I forget when I added the -R option so you may
<br>need to grab an updated version from svn.<br><br>><br>> What was even more interesting was that if i changed to channel 1460<br>> (successful) and then changed to channel 1700 (HBO HD with 5c no way i<br>> should be receiving this channel) firewire_tester would still report
<br>> an immediate success, but trying to run a test capture immediately<br>> afterwards gave me a 0 byte file. Is it possible that firewire_test<br>> is tesing "too quickly" before the channel change actually occurs?
<br><br>firewire_tester considers the connection to be in a working state if it<br>sees 25 or more mpeg packets. You can run multiple test with -r <number>,<br>it will exit 0 if all tests were successful.<br><br>$ firewire_tester -p -n 0 -r 10
<br>Action: Test P2P connection 10 times, node 0, channel 0<br>P2P: Testing...Success, 83 packets received<br>P2P: Testing...Success, 57 packets received<br>P2P: Testing...Success, 39 packets received<br>P2P: Testing...Success, 70 packets received
<br>P2P: Testing...Success, 59 packets received<br>P2P: Testing...Success, 51 packets received<br>P2P: Testing...Success, 69 packets received<br>P2P: Testing...Success, 59 packets received<br>P2P: Testing...Success, 55 packets received
<br>P2P: Testing...Success, 57 packets received<br><br>jim<br><br><br>><br>> On 11/22/06, Eric Smith <<a href="mailto:erictsmith@gmail.com">erictsmith@gmail.com</a>> wrote:<br>> > I'm using the s-video input on my pvr-500. Just create another input
<br>> > device in mythtv-setup (you can use the firewire channel change script<br>> > for this input as well). However, this does not provide any<br>> > understanding that "source firewire" and "source s-video" are actually
<br>> > coming from the same cable box and therefore can not be scheduled at<br>> > the same time. If anyone knows if there is a way to do this I would<br>> > love to know. As of right now, i just make it my own responsibility
<br>> > to make sure i'm not scheduling recordings on both sources at the same<br>> > time.<br>> ><br>> > On 11/22/06, nik gibson <<a href="mailto:nik.gibson@gmail.com">nik.gibson@gmail.com</a>> wrote:
<br>> > > How do you change between firewire and S-video? I would love to<br>> > > differentiate between the two and be able to get the channels that I can't<br>> > > receive over firewire all through the same box.
<br>> > ><br>> > > Thanks<br>> > ><br>> > ><br>> > > On 11/21/06, Eric Smith <<a href="mailto:erictsmith@gmail.com">erictsmith@gmail.com</a>> wrote:<br>> > > > I did a little bit of testing with this last night and had moderate,
<br>> > > > but not complete success. As far as i can tell, at the moment I have<br>> > > > no choice but to try to implement something like this on channel<br>> > > > change. Why are you hesitant of doing this Jim? I have not
<br>> > > > experimented much with broadcast, but what i did seemed to be<br>> > > > consistent failures... and even if it worked that would not impact the<br>> > > > issue below would it?
<br>> > > ><br>> > > > I am running a single SA3250HD and using both the firewire out for the<br>> > > > available HD channels and the s-video out for some non-HD digital<br>> > > > channels. Quite often when switching from one of the channels being
<br>> > > > fed from s-video back to firewire the firewire stream is lost. The<br>> > > > channel is changed correctly almost everytime, but the STB will not<br>> > > > enable streaming (as if the new channel is 5C) In the past it seemed
<br>> > > > the only way to resume the connection was to unplug and replug the<br>> > > > firewire cable from the cable box. What i noticed last night was that<br>> > > > some but not all of my available HD channels would work as the first
<br>> > > > HD channel when using the sure_change script. For example....<br>> > > ><br>> > > > 301 - HBO non HD fed over s-video<br>> > > > 1421 - ABC HD over firewire<br>
> > > > 1460 - TNT HD over firewire<br>> > > ><br>> > > > Start on 301 -> Change to 1421 (Stream is lost)<br>> > > > Start on 301 -> Change to 1460 (Works)<br>> > > > Start on 301 -> Change to 1460 (Works) -> Change to 1421 (Works)
<br>> > > ><br>> > > > I have no idea what would be causing this behavior. Any thoughts? Or<br>> > > > things I can try? My only other thought was to add into the channel<br>> > > > change script to change to 1460 automatically if the stream is not
<br>> > > > successful, retest, and then if 1460 is working change back to the<br>> > > > intended channel. Obviously this is not an ideal situation, but i<br>> > > > figure i can at least give it a try to determine if the behavior i was
<br>> > > > seeing last night is actually consistent.<br>> > > ><br>> > > ><br>> > > ><br>> > > > On 11/20/06, Yeechang Lee <<a href="mailto:ylee@pobox.com">ylee@pobox.com
</a>> wrote:<br>> > > > > Jim Westfall <<a href="mailto:jwestfall@surrealistic.net">jwestfall@surrealistic.net</a>> says:<br>> > > > > > I will say I have always been suspect of people using these scripts on
<br>> > > > > > channel change, especially on 6200 devices.<br>> > > > ><br>> > > > > Me too. I outline in<br>> > > > ><br>> > > <URL:<a href="http://www.gossamer-threads.com/lists/mythtv/users/233570#233570">
http://www.gossamer-threads.com/lists/mythtv/users/233570#233570</a>><br>> > > > > how to simply and easily prime FireWire using firewire_tester at<br>> > > > > bootup with no further pre channel-changing priming needed for 100%
<br>> > > > > reliable recordings. (I should have also said, though, in that<br>> > > > > message, that one needs to switch to Broadcast in mythtv-setup.)<br>> > > > ><br>> > > > > This has nothing to do with the accuracy of channel changes, however;
<br>> > > > > I still face the issue of how every 20-30 recordings a FireWire-based<br>> > > > > channel change will not go through right<br>> > > > > (<URL:<br>> > >
<a href="http://www.gossamer-threads.com/lists/mythtv/users/236728#236728">http://www.gossamer-threads.com/lists/mythtv/users/236728#236728</a>>),<br>> > > > > typically keeping the box set to the previous channel. FireWire always
<br>> > > > > records fine, but not necessarily the right channel.<br>> > > > ><br>> > > > > --<br>> > > > > Yeechang Lee <<a href="mailto:ylee@pobox.com">ylee@pobox.com
</a>> | +1 650 776 7763 | San Francisco CA US<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>> > > > ><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>> > > ><br>> > ><br>> > ><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>> > ><br>> > ><br>> > ><br>> ><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>_______________________________________________<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>