Hi List, I've been using ivtv since 0.4.2-or so on a PVR-250, and have always been very happy with it. I recently upgraded my current system (Athlon64 on Asus A8N-SLI Deluxe (NForce4 SLI) with CentOS4-i386 (2.6.9-xx kernels)) with an X2 CPU, and changed to the SMP kernel. Due to non-ivtv-issues I was unable to use the default kernel, and upgraded to 2.6.17.6, and therefore to ivtv-0.7.0. After a little work, I managed to figure out which modules now were in the kernel rather than ivtv, and got things working.
...except for the DMA errors. I've /never/ had them with the UP kernels (ie 2.6.9 something and ivtv 0.4.6), but with the SMP kernel I got them fairly quickly. I'm grabbing about an hour of TV a day, and I'm getting errors every few days (often grouped together The symptom is as noted elsewhere; ivtv0 warning: ENC: (0) DMA Error 0x0000000b (followed by persistent mpeg artifacts and semi-garbled sound) I've applied the PIO-patch (from one of the messages in "http://ivtvdriver.org/trac/ticket/48";), and am seeing the increase in CPU usage (~50% on my Athlon64 running at 1000MHz), and have so far (1 day) not seen any new errors. Except for the increased CPU use, ivtv seems happy; ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.7.0 (tagged release) loading ivtv: Linux version: 2.6.17.6-2 SMP mod_unload K8 REGPARM 4KSTACKS gcc-3.4 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 WinTV PVR-250 card (cx23416 based) ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17 ACPI: PCI Interrupt 0000:05:07.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 20 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) tveeprom 2-0050: Hauppauge model 32034, rev B148, serial# 6960470 tveeprom 2-0050: tuner model is LG TP18PSB11D (idx 48, type 29) tveeprom 2-0050: TV standards PAL(B/G) (eeprom 0x04) tveeprom 2-0050: audio processor is MSP3415 (idx 6) tveeprom 2-0050: decoder processor is SAA7115 (idx 19) tveeprom 2-0050: has no radio, has IR remote tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) msp3400 2-0040: MSP3415G-B8 found @ 0x80 (ivtv i2c driver #0) msp3400 2-0040: MSP3415G-B8 supports nicam and radio, mode is autodetect and aut oselect ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: Encoder revision: 0x02050032 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 161 x 12960 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 80 x 26208 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) tuner 2-0061: type set to 29 (LG PAL_BG (TPI8PSB11D)) ivtv0: Initialized Hauppauge WinTV PVR-250, card #0 ivtv: ==================== END INIT IVTV ==================== Still - is there any progress on finding the source of this error? I see both Bugs #48 and #49 (http://ivtvdriver.org/trac/ticket/48 and http://ivtvdriver.org/trac/ticket/49) referring to or something like it this. Again, this is with an NForce4 chipset, and the problem did not appear before I enabled SMP mode and/or upgraded the kernel and ivtv. In my view the SMP-upgrade is the most significant of these changes. Yours, -S -- Simen Thoresen, Dolphin ICS Systems Administration and Wulfkit Support _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
