This looks like the firmware misbehaving.
Have you performed a full hardware power-cycle since the upgrade? If
not, I suggest you shutdown, pull the power, leave for a couple
minutes and then power back up again.
If that doesn't help, try switching the firmware back to the version
you were using with 0.2.0 and do another full power-cycle.
Cheers,
Wilf.
On 16/03/06, Shawn Flynn <[EMAIL PROTECTED]> wrote:
> Hello everyone,
>
> I have recently upgraded my system (FC3, PVR250) from ivtv version 0.2.0 to
> 0.4.3 and seem to have broken what was previously running flawlessly. When I
> attempt to capture video it will run for a period of time, then ivtv will
> stop with an encoder error. The length of time that it takes to hit the
> error can be anywhere from a few minutes to several hours. Once it has
> received an error, it will not capture video again until I reload ivtv
> (fails sometimes) or reboot. Has anyone else had a similar failure with
> 0.4.3 or have any pointers for me to try out while troubleshooting this. I
> should also note that I have a PVR-150 in another similar system (both built
> with the latest offerings from ATrpms) and it is working perfectly.
>
> Here are a couple of snippets of my logs showing my ivtv configuration and
> the errors happening. I'd be happy to supply any other data needed to track
> down this issue.
>
>
> Linux video capture interface: v1.00
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.4.3 (tagged release) loading
> ivtv: Linux version: 2.6.12-1.1381_FC3 686 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 WinTV PVR 250 card (cx23415 based)
> ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
> PCI: setting IRQ 10 as level-triggered
> ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 10 (level, low) ->
> IRQ 10
> tveeprom: ivtv version
> tveeprom: Hauppauge: model = 48432, rev = I110, serial# = 6517044
> tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2)
> tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> tveeprom: audio processor = MSP4448 (type = 1b)
> tveeprom: decoder processor = SAA7115 (type = 13)
> ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tuner (ivtv):
> chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
> ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
> saa7115 0-0021: ivtv driver
> saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
> msp3400 0-0040: ivtv driver
> msp3400 0-0040: chip=MSP4448G-A2 +nicam +simple +simpler +radio mode=simpler
> ivtv0: i2c attach to card #0 ok [client=MSP4448G-A2, addr=40]
> msp3400 0-0040: msp34xxg daemon started
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
> ivtv0: Encoder revision: 0x02050032
> ivtv0: Decoder revision: 0x02020023
> ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
> ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
> ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
> ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB
> total)
> tuner: type set to 2 (Philips NTSC (FI1236,FM1236 and compatibles)) by ivtv
> i2c driver #0
> ivtv0: Initialized WinTV PVR 250, card #0
> ivtv: ==================== END INIT IVTV ====================
>
> .....
>
> ivtv0 warning: Failed api call 0x00000082 with result 0xfffffff0
> ivtv0 warning: ENC: Failed stopping capture -16
> ivtv0 warning: Failed api call 0x00000082 with result 0xfffffff0
> ivtv0 warning: ENC: Failed stopping capture -16
> ivtv0 warning: Failed api call 0x000000d5 with result 0xfffffff0
> ivtv0 warning: ENC: Failed to stop VIMevent notification -16
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000c8 with result 0xfffffff0
> ivtv0 warning: init error 21. Code -16
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000b7 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x000000d5 with result 0xfffffff0
> ivtv0 warning: Failed api call 0x00000081 with result 0xfffffff0
> ivtv0 warning: Error starting capture!
> ivtv0 warning: VBI capture start failed
>
> .....
>
> [root at mythbe1 mythtv]# cat /etc/modprobe.conf
> alias eth0 3c59x
> alias snd-card-0 snd-emu10k1
> options snd-card-0 index=0
> install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 &&
> /usr/sbin/alsactl restore >/dev/null 2>&1 || :
> remove snd-emu10k1 { /usr/sbin/alsactl store >/dev/null 2>&1 || : ; };
> /sbin/modprobe -r --ignore-remove snd-emu10k1
> alias usb-controller uhci-hcd
> # ivtv modules setup
> alias char-major-81 ivtv
> alias char-major-81-0 ivtv
>
> .....
>
>
>
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
--
[EMAIL PROTECTED] | MythTV blog: http://mezzanines.blogspot.com/
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
