On Tue, 2010-06-08 at 14:33 +1200, Michael Cree wrote: > On 8/06/2010, at 1:26 PM, Dale Pontius wrote: > > With the audio problem, my wife noticed the silent show, and I tracked > > it back approximately to that morning's boot. > > Actually, when I think about it, I have just had that happen with my > PVR350 card a week or so ago. I was very surprised on viewing a > programme recorded earlier that day that there was no audio! I had > just rebooted the server with the PVR card. Once I discovered the > problem I kicked out the ivtv module (i.e. rmmod ivtv) and then > reinstalled it (modprobe ivtv) and then sound worked again. I think > it has happened twice over the last two or so weeks--the first time I > have ever noticed such a problem in a number of years of using the > card. I am running the latest kernel 2.6.34 (and prior to that I was > sometimes running 2.6.34-rcXes since I was testing some new > features). Maybe a problem in the kernel drivers?
The PVR-350 uses different audio decoding chips/cores than the one used by the HVR-1600, PVR-150, and PVR-500 (which all use a CX25843 or equivalent). Improper functioning of an I2C connected audio decoder could be explained by a hypothetical problem introduced in recent changes in the linux i2c-* modules. I don't know though. When the problem happens, the output of v4l2-ctl --log-status for the PVR-350 should show you the state of the chips on the PVR-350. It may be worht comparing that to when things are operating normally. You may also want ot turn on i2c debugging with the ivtv debug module option, and also turn on the debugging in the msp3400 module (the sound processing chip on the PVR-350) Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
