On Sun, 2011-01-02 at 19:38 -0600, Bob Karschnia wrote: > Per your recommendation, I modprobed the ivtv and cx25840 drivers in > debug mode, below is the result. > > Based on this, it looks like the problem is still occurring even if I > do it manually when the PCI bus isn't busy. It does not show the > correct device id as your directions said. > [14489.808510] cx25840 0-0044: detecting cx25840 client on address 0x88 > [14489.810650] cx25840 0-0044: device_id = 0x0000 > [14489.810653] cx25840 0-0044: cx25 0-21 found @ 0x88 (ivtv i2c driver #0) > > > Any other thoughts on what to do from here?
> > The most likely cause is the CX25843 chip on your PVR-150 is no longer > > working. The CX25843 chip on your PVR-150 is most likely dead. All analog video and audio processing goes through the CX25843 chip. If the CX25843 is dead, then your PVR-150 is useless. The list below had all my suggestions. If none of them result in the PVR-150 working, then it is time to throw your broken PVR-150 in the trash can. > > You can try a few things to see if the PVR-150 card will work again: > > > > 1. Don't load proprietary drivers like the fglrx module listed in your > > output above. If they accidentially corrupt the window into CX23416 > > memory space or register space, or corrupt ivtv internal data > > structures, then things won't work. > > > > or > > > > 2. Pull out *all* your PCI cards, blow the dust out of *all* the slots, > > reinsert the cards, and test again. > > > > or > > > > 3. Blacklist the ivtv module in /etc/modporbe.conf.d/, and modprobe the > > ivtv module later after the boot sequence is complete. The PCI bus > > register accesses for the I2C bus transactions may not be reliable on > > that motherboard when the PCI bus is very busy. > > > > or > > > > 4. Test with a Windows install on the machine. > > > > or > > > > 5. Test the PVR-150 in another machine. Regards, Andy _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
