I have already posted this question once but since there were no replies I'll give it another try. It's not my meaning to spam the list but I really would love to solve this problem and believe that others could be interested in any possible answers. Here goes nothing...
As soon as I start to capture TV-signals with my Hauppauge PVR-500 the computer crashes. I have tried a number of distros (Ubuntu Breezy, OpenSuse 10 and Fedora Core4) but the problem remains in all of them.
At initiation of the IVTV driver my log says "Unreasonably low latency timer, setting to 64 (was 32)". The thing is that I'm unable to capture any tv (or radio) with my PVR-500 if the latency timer is higer than 32. I have found this out by playing around with the PCI Latency Tool ( http://downloads.guru3d.com/download.php?det=951) in Windows XP. If the latency timer is > 32 the computer freezes as soon I start the capturing.
This is my system setup:
ABIT AV8-3rd Eye (VIA K8T800 Pro/VT8237)
AMD Athlon 64 3500+
Hauppauge PVR-500 MCE
Inno3d, NVIDIA GeForce 6200, 128 MB
Gail 2*512 MB
I'm starting to think that the crashes has to do with the combination of the PVR-500 card and my ABIT AV8-3rd eye motherboard. Apperently there is a known problem with PVR-500 + ASUS A8V-Deluxe and just like my motherboard the ASUS board is based on the VIA K8T800 Pro chipset.
Is there any way to tell IVTV not to change the latency timer (preferably without manipulating source code)? Will the driver not work with latency timer < 64?
Why does IVTV want to change the latency timer? Could you give a explanation to what a higher latency timer improves?
Is there perhaps some other way to solve my capturing problems without lowering the latency timer?
All sugestions are warmly welcome, I'm getting desperate here!
//Pontus
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
