Looking at this problem again, I found this information: http://www.morph3ous.net/2006/08/26/ivt ... om-author/
There are two diff files linked there from an ivtv dev that claim to fix the problem but they're dead links now. It appears this patch may be included in ivtv versions from 0.7.1 and beyond. Is it possible to update ivtv in R5E50 without too much trouble?

R5E50 already includes the latest ivtv driver available for the 2.6.18 kernel used.

So I think we are S.O.L. until the ivtv guys figure these DMA problems out. Seems like it is going downhill though as these problems have only been in the later versions of ivtv, my PVR-150 has been solid for years and now this, blah...

_________________
MythTV box: Opty 170, MSI K8NGM2-FID, 1.5 GB PC2700, Seagate 7200.10 400GB, Lite-On Combo drive. PVR-150, HDHomeRun. Antec Sonata, Freezer 64 Pro. Oh so quiet.

what version do we have? Forgive my ignorance if I'm mistaken but the last version listed in the KM changelog is 0.7.0 and according to the ivtv page, the 2.6.18 kernel supports 0.8.2

You can always ask the system itself...

ahh, thank you. I had no idea how to check that myself.

There's even a "Version" button donw on the KnoppMyth menu in the GUI...

Ok, lets not rub it in. I didn't realize that button gave the ivtv version also.

Ok, I think I'd like to try recompiling ivtv to use PIO mode instead of DMA, and see if that helps. I have no idea how to go about this or what other problems it might cause. Can someone comment on how to do it and possible implications? If you point me in the right direction I can probably figure it out if you don't want to post a whole tutorial Thanks!!

_________________
MythTV box: Opty 170, MSI K8NGM2-FID, 1.5 GB PC2700, Seagate 7200.10 400GB, Lite-On Combo drive. PVR-150, HDHomeRun. Antec Sonata, Freezer 64 Pro. Oh so quiet.