Adam Bodnar wrote: > I can't say for sure mine is happening randomly, but it appears more likely that it is > happening at the beginning. As I used to have the commercial detection occurr right when > a recording started. > > The thing is I haven't upgrade ivtv or mythtv. I'm still sitting at MythTV .18.1 and > ivtv 2.0. So I'm starting to wonder if maybe a different package I updated has caused > this issue. And I haven't upgrade my kernel either > > From looking at my log, I'm seeing that the errors seem to happening on cardid 2 which > I believe is the PVR250MCE that I bought after I had already bought a PVR250. But like > I said, both cards ran flawlessly for quite some time till recently. > > Which makes me still feel like this is occuring due to an upgrade some other package.
Adam, I would have to agree that a package update is causing the issue. It's just a matter of "which package?" It was rather apparent on my system as the PVR250MCE (4801) was my primary card and recorded ~5 hours per day without so much as a hiccough before I did a 'smart update && smart upgrade' to bring it to the latest MythTV/IvTV builds. After that point, I'm lucky to get 10 minutes of recording out of it. Unfortunately, my update involved so many different packages, and included a kernel update that I don't think I'd be able to determine exactly what changed on my system. I also failed to create a snapshot of the system before I updated it so there is no going back for me. You might be in a better position to troubleshoot this though. >From looking at your original message, I can see that your PVR250MCE (4801) card is showing up as ivtv card #1, which is likely device /dev/video1, and if you configured MythTV in order of the cards it would be MythTV cardid 2. Can you verify that it is only your MythTV cardid 2 card that is showing the firmware hang? The easiest way for me to cause the fault is to start live tv, switch to my card id 2 and start changing channels (watching for about 10 seconds between channel changes). This will hang my card within a few minutes. If we can narrow the problem to just this model of card, then it may give the dev's an idea of what to ask us for troubleshooting information. Did you do any package updates or installations prior to you noticing that the card wasn't working correctly anymore? If you can remember what may have changed you can try rolling back to a previous version, and I can see if I have the same installed and try rolling it back as well. If I can find some time over the next week, I will try installing my card in a new machine with a minimal FC4 installation on it and see at what point the captures stop working. If I find any new information, I'll keep you informed. Shawn Flynn _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
