Hi
Have you tried ivtv 0.4.6 . This is the newest version for you kernel and fix some issue the ivtv 0.4.5 had with changing channels. And do you use the correct firmware. This is important. Look here
http://ivtvdriver.org/index.php/Firmware. Every time you try a new firmware you must shut down your computer and take out the power for 30 sec. If this don't help you must post the dmesg message
Try dmesg | grep ivtv
Harald
On 7/7/06, Michael Zanetti <[EMAIL PROTECTED]> wrote:
I have a PVR 150 and a PVR 350 in the same machine. Both cards are
working but after some time they produce buggy videos. I can see some
artefacts and occasionally some previous frames that were skipped
before. At this point it takes at maximum 10 minutes and the driver/
card crashes. The errors are the following:
When playing the files I see this messages:
...
[mpeg2video @ 0x2aaaabf43d70]ac-tex damaged at 44 4
[mpeg2video @ 0x2aaaabf43d70]end mismatch left=14
[mpeg2video @ 0x2aaaabf43d70]invalid cbp at 1 34
[mpeg2video @ 0x2aaaabf43d70]invalid cbp at 38 35
[mpeg2video @ 0x2aaaabf43d70]ac-tex damaged at 38 29
[mpeg2video @ 0x2aaaabf43d70]end mismatch left=99
[mpeg2video @ 0x2aaaabf43d70]ac-tex damaged at 33 6
[mpeg2video @ 0x2aaaabf43d70]mb incr damaged
[mpeg2video @ 0x2aaaabf43d70]slice mismatch
[mpeg2video @ 0x2aaaabf43d70]ac-tex damaged at 34 35
[mpeg2video @ 0x2aaaabf43d70]ac-tex damaged at 38 35
[mpeg2video @ 0x2aaaabf43d70]00 motion_type at 38 35
[mpeg2video @ 0x2aaaabf43d70]skipped MB in I frame at 33 35
[mpeg2video @ 0x2aaaabf43d70]invalid mb type in P Frame at 34 28
...
After the crash mythtv reports this:
Seek timeout: ivtv driver has stopped responding
All later recordings in Myth have a size of 0 Bytes
cat /dev/video0 > test.mpg also produces 0Byte files. Same with /dev/
video1
ivtv-tune doesn't throw any errors but also doesn't says "Signal
detected" as usually.
After a reboot both cards work again. Sometimes for a half an hour
and sometimes for about 2 days.
I tried every 0.4.x version of ivtv. I can't try 0.6.x or 0.7.x
because of the lack of dmraid support in the new kernels.
The best results I get with 0.4.0-r3 and 0.4.4. With this two
versions the average uptime is about 1 day. All other versions work
just for about 5 minutes.
I also tried different firmwares. The one thats actually in the
gentoo portage and the newest one downloaded from ivtvdriver.org. I
don't know the version numbers.
I had both cards working before in another PC with kernel 2.6.14 and
ivtv 0.4.0-r3.
Now its an ASUS A8V mainboard with an amd64 architecture with kernel
2.6.14.
I have searched a lot for this error but I couldn't find any solution
for this specific problem.
Any suggestions what I could try next?
I really don't know what to do and I NEED my MythTV.
Please help me!!!
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
