On Mon, 2008-09-22 at 19:12 -0600, [EMAIL PROTECTED] wrote: > >Mandriva 2008.1 IVTV No Worky > >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.> > > > >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? > > >$ /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.)
> Here is what happens when playing the mpg file with mplayer > > [EMAIL PROTECTED] mythtv]# mplayer foo.mpg > MPlayer 1.0-1.rc2.10.3plf2008.1-4.2.3 (C) 2000-2007 MPlayer Team > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+ (Family: 15, Model: > 75, Step > ping: 2) > CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1 > Compiled for x86 CPU with extensions: MMX MMX2 3DNow 3DNowEx SSE SSE2 > mplayer: could not open config files /root/.lircrc and /etc/lircrc > mplayer: No such file or directory > Failed to read LIRC config file ~/.lircrc. > > Playing foo.mpg. > MPEG-PS file format detected. > > Too many video packets in the buffer: (4096 in 7975968 bytes). > Maybe you are playing a non-interleaved stream/file or the codec failed? > For AVI files, try to force non-interleaved mode with the -ni option. > MPEG: No audio stream found -> no sound. > VIDEO: MPEG2 720x480 (aspect 2) 29.970 fps 8000.0 kbps (1000.0 kbyte/s) > xscreensaver_disable: Could not find XScreenSaver window. > ========================================================================== > Opening video decoder: [mpegpes] MPEG 1/2 Video passthrough > VDec: vo config request - 720 x 480 (preferred colorspace: Mpeg PES) > Could not find matching colorspace - retrying with -vf scale... > Opening video filter: [scale] > The selected video_out device is incompatible with this codec. > Try appending the scale filter to your filter list, > e.g. -vf spp,scale instead of -vf spp. > VDecoder init failed :( > Opening video decoder: [libmpeg2] MPEG 1/2 Video decoder libmpeg2-v0.4.0b > Selected video codec: [mpeg12] vfm: libmpeg2 (MPEG-1 or 2 (libmpeg2)) > ========================================================================== > Audio: no sound > Starting playback... > VDec: vo config request - 720 x 480 (preferred colorspace: Planar YV12) > VDec: using Planar YV12 as output csp (no 0) > Movie-Aspect is 1.33:1 - prescaling to correct movie aspect. > VO: [xv] 720x480 => 720x540 Planar YV12 [zoom] > V: 6.6 189/189 12% 0% 0.0% 0 0 > Exiting... (Quit) 6.6 seconds of video with no audio. I know with CX25843 chips and cores, running the audio clock PLL's outside of specifications can cause them not work provide audio samples (this was a bug for 32 kbps audio in the cx18 driver). However, I'm not very familiar with the MSP34xx and SAA71xx chips, so I can't comment except to *guess* one of them is supposed to provide audio to the MPEG encoder and may not be. > > Here is the output of modinfo ivtv > > > [EMAIL PROTECTED] mythtv]# modinfo ivtv > filename: > parm: debug:Debug level (bitmask). Default: 0 > 1/0x0001: warning > 2/0x0002: info > 4/0x0004: mailbox > 8/0x0008: ioctl > 16/0x0010: file > 32/0x0020: dma > 64/0x0040: irq > 128/0x0080: decoder > 256/0x0100: yuv > 512/0x0200: i2c > 1024/0x0400: high volume > (int) > parm: enc_mpg_buffers:Encoder MPG Buffers (in MB) > Default: 4 (int) > parm: newi2c:Use new I2C implementation > -1 is autodetect, 0 is off, 1 is on > Default is autodetect (int) The above parameters are the ones I care about for debugging. As root, do something like: # modprobe -r ivtv # modprobe ivtv debug=639 enc_mpg_buffers=6 To give yourself more buffers and to turn on some verbose debugging. Verbose debugging may give hints to the problems when you try to run captures. You can add 1024 to the debug value above to get a whole lot of noise in the logs. > > >Which begs some questions: > > >What application are you using? > > I am trying to debug using mplayer right now, but ultimately I'll be using > mythtv OK. keep debugging with mplayer and cat. MythTV throws too many unknowns into the mix. > >Do you get the message when you simply do: > > >$ cat /dev/video1 > foo.mpg > > I get no error messages when encoding using cat And what messages do you get (/var/log/messages or dmesg) with verbose debugging turned on > >Do you also get the message when using /dev/video0 with your preferred > >application? > > I've posted the output of mplayer above OK. > >What does the output look like in your preferred application? > > I get a black screen with no snow. > > >Does the output look OK when playing back the foo.mpg file captured with > >cat? > > Nope. Does /cat/proc interrupts show interrupts having accumulated for the ivtv board after a capture compared to before the capture starting? > Any theories? None yet. Need verbose debugging output from the driver. Regards, Andy > thx > Scott _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
