[mythtv-users] ivtv driver went nuts...

[James Pifer]

On Sun, 2006-10-15 at 20:35 -0400, Thom Paine wrote:
> I am running this....
> [root at mythmbe ~]# rpm -qa | grep ivtv
> ivtv-firmware-1.8a-10.at
> perl-Video-ivtv-0.13-8.fc4.at
> ivtv-kmdl-2.6.17-1.2142_FC4smp-0.7.1-118.fc4.at
> ivtv-0.7.1-118.fc4.at
> ivtv-kmdl-2.6.17-1.2142_FC4-0.7.1-118.fc4.at
> kernel-smp-2.6.17-1.2142_FC4
> 
> in my box and I can't even get video o play from my card. I think I'm
> going to try going back to a previous ivtv that was working before I
> upgraded to .20.

I'm going to hold off a final verdict for a little while, but I've been
up since Friday and have been through about a dozen successful
recordings. I have not had any ivtv time outs and the only negative
looking thing I've seen is a couple of these:
[mpeg2video @ 0x2e7da24]ac-tex damaged at 2 3
[mpeg2video @ 0x2e7da24]Warning MVs not available

Here's how I got to this point. I played around trying to figure out if
it was a single PVR or something else causing my problem. I made all
three of my recorders (1/2/3-50's) record at the same time. Two worked,
one failed. Based on the ivtv startup I determined (but not %100) that
the card that failed was me PVR250. I still had a free slot in the
system so I thought I would move it and try again. 

Unfortunately my free slot was one of the PCI-X slots and neither my 250
or 350 are universal PCI, so they had to stay in the slots they were in.
BUT, I did switch them, which essentially is just re-seating them as far
as I can tell. 

I did also drop the kernel to smp-2.6.17-1.2174_FC5 and matching ivtv,
lirc, and nvidia kmdl's. So far things are running well again. I'll try
to post back near the end of the week with another update, or sooner if
all goes south.

James