Hans, Thanks for the quick reply! Below is my init ivtv messages from dmesg.
Linux video capture interface: v2.00 ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.9.0 (tagged release) loading ivtv: Linux version: 2.6.19 SMP mod_unload PENTIUM4 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected Hauppauge card (cx23416 based) ACPI: PCI Interrupt 0000:05:02.0[A] -> GSI 18 (level, low) -> IRQ 18 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1411 usbcore: registered new interface driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) tveeprom 0-0050: Hauppauge model 26032, rev C199, serial# 2978102 tveeprom 0-0050: tuner model is TCL 2002N 5H (idx 99, type 50) tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 0-0050: audio processor is CX25841 (idx 35) tveeprom 0-0050: decoder processor is CX25841 (idx 28) tveeprom 0-0050: has no radio, has IR remote ivtv0: Autodetected Hauppauge WinTV PVR-150 ivtv0: reopen i2c bus for IR-blaster support tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) cx25840 0-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0) cx25840 0-0044: loaded v4l-cx25840.fw firmware (16382 bytes) wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0) ivtv0: Encoder revision: 0x02050032 ivtv0: Registered device video0 for encoder MPEG ivtv0: Registered device video32 for encoder YUV ivtv0: Registered device vbi0 for encoder VBI ivtv0: Registered device video24 for encoder PCM audio tuner 0-0061: type set to 50 (TCL 2002N) ivtv0: Initialized Hauppauge WinTV PVR-150, card #0 ivtv: ==================== END INIT IVTV ==================== Also, I just saw (for the first time ever, since investigating this): ivtv0 warning: ENC: (0) DMA Error 0x0000000b 00020005 ivtv0 warning: offset 0 -> 128 ivtv0 warning: offset 128 -> 0 ivtv0: All encoder MPEG stream buffers are full. Dropping data. ivtv0: Cause: the application is not reading fast enough. ivtv0: All encoder MPEG stream buffers are full. Dropping data. ivtv0: Cause: the application is not reading fast enough. ivtv0 warning: ENC: (0) DMA Error 0x0000000b 00020001 ivtv0 warning: offset 0 -> 128 ivtv0 warning: offset 128 -> 52 ivtv0 warning: ENC: (0) DMA Error 0x0000000b 08000005 ivtv0 warning: offset 52 -> 128 ivtv0 warning: offset 128 -> 68 ivtv0 warning: ENC: (0) DMA Error 0x0000000b 00020001 ivtv0 warning: offset 68 -> 128 ivtv0 warning: ENC: REG_DMAXFER 2 wait failed ivtv0 warning: ENC: (0) DMA Error 0x00000001 00000001 ivtv0 warning: ENC: REG_DMAXFER 2 wait failed ivtv0 warning: ENC: (1) DMA Error 0x00000001 00000005 ivtv0 warning: ENC: REG_DMAXFER 2 wait failed ivtv0 warning: ENC: (2) DMA Error 0x00000001 00000001 ivtv0 warning: ENC: REG_DMAXFER 2 wait failed ivtv0 warning: ENC: (3) DMA Error 0x00000001 00000005 ivtv0 warning: ENC: REDO DMA took too many tries. ivtv0 warning: Error Encoder DMA I see that this may be similar to the problem Preet Khalsa is having, and I saw your response about upgrading mythtv. I'm using the Gentoo "package" at version 0.20_p11626. Would the above error cause a permanent lock-up? Thanks, Erik G. Burrows > On Wednesday 13 December 2006 03:18, Erik G. Burrows wrote: > > I'd appreciate any help I can get diagnosing a strange problem I've > > been having with my PVR-150 card using the ivtv driver. > > > > 1. It worked just fine under my last system incarnation, using the > > same card, but different MB/CPU/Linux distro > > 2. Some time passed... > > 3. Now, the system works, and I get TV through the card using either > > the "cat /dev/video0" method, or through mythtv, for a while... > > 4. After a few (to several) hours of working just fine, it stops. No > > more video from mythtv, and the "cat /dev/video0 > cap.mpeg" just > > generates a zero-length file, no matter how long I let it go. > > 5. There is no, zero, not any output to the console, syslog in dmesg > > at the time of the failure or on subsequent attempts to use it. 6. > > Unloading and reloading the ivtv and all other (video related) > > drivers does not cure the problem. > > 7. A warm reboot fixes it, for a while > > 8. A cold reboot fixes it, for a while > > 9. A very, very cold (plug out overnight) reboot fixes it, for a > > while. > > > > I've tried the last three stable ivtv driver versions with their > > required kernel versions. Exact same behavior. > > > > I'm open to the problem possibly being in the card, but it seems more > > likely in the software. > > > > Any ideas? > > 1) Please post the INIT IVTV messages. > 2) Could it be overheating of the card? > 3) Another known possible cause is a powersupply that is too weak. > > Regards, > > Hans > > _______________________________________________ > 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
