On Sat, 2008-09-20 at 15:36 -0600, [EMAIL PROTECTED] wrote: > I have recently upgraded from Mandriva 2008 to 2008.1 and now can't get > IVTV working. My kernel is: > > 2.6.24.7-tmb-desktop-3mdv > > Here's the output of dmesg > > ivtv: Start initialization, version 1.2.0 > ivtv0: Initializing card #0 > ivtv0: Autodetected Hauppauge card (cx23415 based) > ivtv0: Unreasonably low latency timer, setting to 64 (was 32) > ivtv0: Autodetected Hauppauge WinTV PVR-350 > saa7115 2-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #0) > saa7127 2-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) > msp3400 2-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0) > tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0) > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) > ivtv0: Registered device video0 for encoder MPG (4096 kB) > ivtv0: Registered device video32 for encoder YUV (2048 kB) > ivtv0: Registered device vbi0 for encoder VBI (1024 kB) > ivtv0: Registered device video24 for encoder PCM (320 kB) > ivtv0: Registered device radio0 for encoder radio > ivtv0: Registered device video16 for decoder MPG (1024 kB) > ivtv0: Registered device vbi8 for decoder VBI (64 kB) > ivtv0: Registered device vbi16 for decoder VOUT > ivtv0: Registered device video48 for decoder YUV (1024 kB) > ivtv0: Initialized card #0: Hauppauge WinTV PVR-350 > ivtv1: Initializing card #1 > ivtv1: Autodetected Hauppauge card (cx23415 based) > ivtv1: Unreasonably low latency timer, setting to 64 (was 32) > ivtv1: Autodetected Hauppauge WinTV PVR-350 > saa7115 3-0021: saa7115 found (1f7115d0e100000) @ 0x42 (ivtv i2c driver #1) > saa7127 3-0044: saa7129 found @ 0x88 (ivtv i2c driver #1) > msp3400 3-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #1) > tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #1) > tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1) > ivtv1: Registered device video1 for encoder MPG (4096 kB) > ivtv1: Registered device video33 for encoder YUV (2048 kB) > ivtv1: Registered device vbi1 for encoder VBI (1024 kB) > ivtv1: Registered device video25 for encoder PCM (320 kB) > ivtv1: Registered device radio1 for encoder radio > ivtv1: Registered device video17 for decoder MPG (1024 kB) > ivtv1: Registered device vbi9 for decoder VBI (64 kB) > ivtv1: Registered device vbi17 for decoder VOUT > ivtv1: Registered device video49 for decoder YUV (1024 kB) > ivtv1: Initialized card #1: Hauppauge WinTV PVR-350 > ivtv: End initialization > ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > ivtv0: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes) > ivtv0: Encoder revision: 0x02060039 > ivtv0: Decoder revision: 0x02020023 > ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes) > ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > ivtv1: Loaded v4l-cx2341x-dec.fw firmware (262144 bytes) > ivtv1: Encoder revision: 0x02060039 > ivtv1: Decoder revision: 0x02020023 > ivtv1: Loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
> ivtv1: All encoder MPG stream buffers are full. Dropping data. > ivtv1: Cause: the application is not reading fast enough. > > Note that I have several instances of the error on the last lines. Which begs some questions: What application are you using? Do you get the message when you simply do: $ cat /dev/video1 > foo.mpg Do you also get the message when using /dev/video0 with your preferred application? What does the output look like in your preferred application? Does the output look OK when playing back the foo.mpg file captured with cat? > I have tried compiling from scratch and have placed the latest drivers > into the appropriate firmware directory /lib/firmware. > > Any pointers? Do a $ /sbin/modinfo ivtv to see all the module options available. You may wish to modprobe ivtv with the debug parameter set to log warning, info, and file operations and maybe at high volume. Try to see if the application is reading things off at a reasonable rate. If the application can't read off data fast enough, there's not too much to be done with the driver. (Maybe allocating more than the default 4 MB of buffers for the MPEG encoder via the enc_mpg_buffers module options might help.) Just an idea. Regards, Andy > thx > Scott _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
