On Sunday 03 August 2008 19:58:09 Peter Michael Jensen wrote:
> Have upgraded to 2.6.26-1 but the same story.
> Really no ideas?
> I hope I do not have to try out som Windows media-software in order
> to get it to work ;-)

To be honest I haven't come across something like this before. When cat 
stops, do you mean that it hangs or that it just returns and you got 
the shell prompt? If you run 'cat' again, does it actually continue 
capturing? Does the same thing happen if MythTV is not running at all? 
(just to make sure there is no interference between MythTV and cat)

Also try to turn on debugging in ivtv (make sure that MythTV isn't 
running): 'ivtv-ctl -D0x413'. You will get a lot of messages in your 
kernel log, but when cat stops then mail me the last 200 lines of the 
ivtv debugging in the kernel log. That should hopefully give some 
information on what's happening.

Regards,

        Hans

>
> /Peter
>
> 2008/8/3 Peter Michael Jensen <[EMAIL PROTECTED]>
>
> > I have also disabled hypertreading in grub.
> > I am running debian unstable
> > --
> > Linux slim 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686
> > GNU/Linux --
> > slim:~# modinfo ivtv
> > filename:
> > /lib/modules/2.6.25-2-686/kernel/drivers/media/video/ivtv/ivtv.ko
> > version:        1.2.0
> > --
> > slim:~# dmesg | grep ivtv
> > [    4.402172] ivtv:  Start initialization, version 1.2.0
> > [    4.442561] ivtv0: Initializing card #0
> > [    4.442566] ivtv0: Autodetected Hauppauge card (cx23415 based)
> > [    4.443302] ivtv0: Unreasonably low latency timer, setting to 64
> > (was 32)
> > [    4.496003] ivtv0: Autodetected Hauppauge WinTV PVR-350
> > [    4.709433] saa7115 0-0021: saa7115 found (1f7115d0e100000) @
> > 0x42 (ivtv i2c driver #0)
> > [    4.869575] saa7127 0-0044: saa7127 found @ 0x88 (ivtv i2c
> > driver #0) [    4.878002] msp3400 0-0040: MSP4418G-A2 found @ 0x80
> > (ivtv i2c driver #0)
> > [    4.879424] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > [    4.893298] ivtv0: Registered device video0 for encoder MPG
> > (32768 kB) [    4.893320] ivtv0: Registered device video32 for
> > encoder YUV (16384 kB) [    4.893340] ivtv0: Registered device vbi0
> > for encoder VBI (16384 kB) [    4.893359] ivtv0: Registered device
> > video24 for encoder PCM (1024 kB) [    4.893378] ivtv0: Registered
> > device radio0 for encoder radio [    4.893401] ivtv0: Registered
> > device video16 for decoder MPG (1024 kB) [    4.893420] ivtv0:
> > Registered device vbi8 for decoder VBI (64 kB) [    4.893440]
> > ivtv0: Registered device vbi16 for decoder VOUT [    4.893461]
> > ivtv0: Registered device video48 for decoder YUV (1024 kB) [   
> > 4.893464] ivtv0: Initialized card #0: Hauppauge WinTV PVR-350 [   
> > 4.893488] ivtv:  End initialization
> > [    5.029859] ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836
> > bytes) [    5.055573] ivtv0: Loaded v4l-cx2341x-dec.fw firmware
> > (262144 bytes) [    5.072328] ivtv0: Encoder revision: 0x02060039
> > [    5.072328] ivtv0: Decoder revision: 0x02020023
> > [    5.744048] ivtv0: Loaded v4l-cx2341x-init.mpg firmware (155648
> > bytes) [    5.832524] ivtvfb0: Framebuffer at 0xe9510000, mapped to
> > 0xf9890000, size 1665k
> > [    5.932850] ivtvfb0: Framebuffer registered on ivtv card id 0
> >
> > 2008/8/3 Peter Michael Jensen <[EMAIL PROTECTED]>
> >
> > Hi all
> >
> >> Really hope you can help with this issue.
> >>
> >> When I make a "cat /dev/video0 > /mnt/media/video/test.mpg"
> >> everything seems fine but when it runs for a long time it
> >> suddently stops caturing video (sometimes 30 minutes sometimes 1,5
> >> hours, etc.). I just stops without any dmesg, etc.
> >>
> >> I have tried "everything" - including:
> >> - totally new hardware - including new pvr350 (!)
> >> - adjust ivtv parameters (increasing all buffers)
> >> - logging etc.
> >>
> >> I think the above stopping of capturing results in a mythtv-system
> >> halt. Because when I activate mythtv and records a show everything
> >> is fine until somewhat the same time that the cat stops capturing.
> >> Can there be a connection?
> >>
> >> Any good ideas for debugging this issue?
> >>
> >> Thanks in advance
> >> Peter Michael



_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to