Cyrus A wrote: > Mark Paulus wrote: > >> Hans Verkuil wrote: >> >>> Hi all, >>> >>> I've just released ivtv-0.10.3. The main change is that PIO memory >>> copies >>> are no longer done inside the interrupt handler: this led to a host of >>> subtle issues like clock drift, missing IR key presses, wrong >>> reporting of >>> CPU usage and probably other issues as well. It is recommended to >>> upgrade >>> to 0.10.3. This driver is for kernels 2.6.18, .19, .20 and .21. >>> >>> Enjoy, >>> >>> Hans >>> >>> - Models 30012 to 30039 are for a low profile PVR250, not a PVR150. >>> - Move PIO memory copies from the interrupt handler to the work handler. >>> This fixes problems with the timer ticks and IR remotes. >>> >>> >> Was this release supposed to address the >> ivtv0: All encoder MPEG stream buffers are full. Dropping data. >> ivtv0: Cause: the application is not reading fast enough. >> >> issue? I have been running the 10.3 svn branch for a few days, >> and I still seeing this occassionally, even though I have the following >> in /etc/modprobe.d/ivtv: >> $ cat /etc/modprobe.d/ivtv >> # options ivtv tuner=50 mpg_buffers=16 >> options ivtv enc_vbi_buffers=16 enc_yuv_buffers=16 enc_mpg_buffers=16 >> >> ivtv: ==================== START INIT IVTV ==================== >> ivtv: version 0.10.3 (tagged release) loading >> ivtv: Linux version: 2.6.18-4-k7 SMP mod_unload K7 REGPARM gcc-4.1 >> 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:02:07.0[A] -> Link [APC4] -> GSI 19 (level, >> low) -> IRQ 209 >> ivtv0: Unreasonably low latency timer, setting to 64 (was 32) >> logips2pp: Detected unknown logitech mouse model 77 >> ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21 >> ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 21 (level, >> high) -> IRQ 185 >> PCI: Setting latency timer of device 0000:00:06.0 to 64 >> intel8x0_measure_ac97_clock: measured 54695 usecs >> intel8x0: clocking to 46881 >> input: ImExPS/2 Logitech Explorer Mouse as /class/input/input2 >> ts: Compaq touchscreen protocol output >> ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes) >> ivtv0: Encoder revision: 0x02060039 >> tveeprom 2-0050: Hauppauge model 32032, rev B310, serial# 7045282 >> tveeprom 2-0050: tuner model is Philips FI1236 MK2 (idx 10, type 2) >> tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) >> tveeprom 2-0050: audio processor is MSP4448 (idx 27) >> tveeprom 2-0050: decoder processor is SAA7115 (idx 19) >> tveeprom 2-0050: has no radio, has IR remote >> ivtv0: Autodetected Hauppauge WinTV PVR-250 >> tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) >> saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) >> msp3400 2-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0) >> msp3400 2-0040: MSP4448G-A2 supports radio, mode is autodetect and >> autoselect >> ivtv0: Registered device video0 for encoder MPEG (16 MB) >> ivtv0: Registered device video32 for encoder YUV (16 MB) >> ivtv0: Registered device vbi0 for encoder VBI (16 MB) >> ivtv0: Registered device video24 for encoder PCM audio (1 MB) >> tuner 2-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and >> compatibles)) >> ivtv0: Initialized Hauppauge WinTV PVR-250, card #0 >> ivtv: ====================== NEXT CARD ====================== >> ivtv1: Autodetected Hauppauge card (cx23416 based) >> ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [APC2] -> GSI 17 (level, >> low) -> IRQ 201 >> ivtv1: Unreasonably low latency timer, setting to 64 (was 32) >> ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes) >> ivtv1: Encoder revision: 0x02060039 >> tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1) >> tveeprom 3-0050: Hauppauge model 26582, rev F0B2, serial# 9709741 >> tveeprom 3-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) >> tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) >> tveeprom 3-0050: audio processor is CX25843 (idx 37) >> tveeprom 3-0050: decoder processor is CX25843 (idx 30) >> tveeprom 3-0050: has no radio, has no IR remote >> ivtv1: Autodetected Hauppauge WinTV PVR-150 >> cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1) >> cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes) >> wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1) >> ivtv1: Registered device video1 for encoder MPEG (16 MB) >> ivtv1: Registered device video33 for encoder YUV (16 MB) >> ivtv1: Registered device vbi1 for encoder VBI (16 MB) >> ivtv1: Registered device video33 for encoder YUV (16 MB) >> ivtv1: Registered device vbi1 for encoder VBI (16 MB) >> ivtv1: Registered device video25 for encoder PCM audio (1 MB) >> tuner 3-0061: type set to 50 (TCL 2002N) >> ivtv1: Initialized Hauppauge WinTV PVR-150, card #1 >> ivtv: ==================== END INIT IVTV ==================== >> >> Like others, I have both these cards in a box that has an AMD x2 3800+ >> w/1GB of RAM. Now, I do have lots of disks in there >> and I run [EMAIL PROTECTED], but FAH is running at nice 19 priority, so >> that shouldn't be the problem. >> Any thoughts on what else could be tweaked? >> >> _______________________________________________ >> ivtv-devel mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-devel >> > > Mark, > > This is probably a "duh" question, but can you post your ivtv alias > line? I have just been loading mine on the command line with modprobe. > > Is it just "alias char-major-81ivtv"? > > I've also been having issues with "the application is not reading fast > enough" doing simultaneous recordings at 1500kbps each using ffmpeg to > encode on the fly (AMD x2 3800 with 2GB ram). I'm really hoping 0.10.3 > has fixed that issue, as well as some closed captioning uncleanliness. > > Cyrus > > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > > ivtv guys and especially Hans,
Ignore my comments earlier about garbled closed captioning due to processing/multiple-recording issues. It turns out the station I was using had just switched to digital and their analog captions were messed up. Not an ivtv problem. Sorry. Cyrus _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
