On Saturday 16 December 2006 16:38, Sander Sweers wrote:
> Sdkovacs wrote:
> > Previously I had been running MythTV on Fedora Core 3 and IVTV
> > 0.4.9. without incident. I did a fresh install of Fedora Core 6
> > with the latest IVTV from ATRPMS (0.8.2) and have since been
> > getting daily frontend freezing when using commands such as fast
> > forward, rewind and pause.
> > I am using the PVR350 with the Xdriver enabled.
> >
> > I'm attaching the kernel output from /var/log/messages and the ivtv
> > initialization information. Please let me know if there's anything
> > I can do to fix this behavior. And again, I had not been having
> > this issue with Fedora Core 3 and the IVTV 0.4.x series.
> >
> > Thank you for your time,
> >
> > Steve
> >
> > Dec 15 13:57:48 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 13:57:48 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000003 with result 0xfffffff0
> > Dec 15 13:57:48 localhost kernel: ivtv0 warning: DEC: error
> > changing speed Dec 15 13:57:48 localhost kernel: ivtv0 warning:
> > DEC: error in slow/fast mode Dec 15 13:57:59 localhost kernel:
> > ivtv0 warning: 1000 ms time out waiting for firmware
> > Dec 15 13:57:59 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000015 with result 0xfffffff0
> > Dec 15 13:57:59 localhost kernel: ivtv0 warning: DEC: couldn't read
> > clock Dec 15 13:58:09 localhost kernel: ivtv0 warning: 1000 ms time
> > out waiting for firmware
> > Dec 15 13:58:09 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000019 with result 0xfffffff0
> > Dec 15 13:58:19 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 13:58:19 localhost kernel: ivtv0 warning: Failed api call
> > 0x0000001a with result 0xfffffff0
> > Dec 15 13:58:19 localhost kernel: ivtv0 warning: COULDN'T
> > INITIALIZE DECODER SOURCE -16
> > Dec 15 13:58:29 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 13:58:29 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000001 with result 0xfffffff0
> > Dec 15 13:58:29 localhost kernel: ivtv0 warning: DEC: start_decode,
> > error starting
> > Dec 15 13:58:39 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 13:58:39 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000015 with result 0xfffffff0
> > Dec 15 13:58:39 localhost kernel: ivtv0 warning: DEC: couldn't read
> > clock Dec 15 13:58:49 localhost kernel: ivtv0 warning: 1000 ms time
> > out waiting for firmware
> > Dec 15 13:58:49 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000015 with result 0xfffffff0
> > Dec 15 13:58:49 localhost kernel: ivtv0 warning: DEC: couldn't read
> > clock Dec 15 13:58:59 localhost kernel: ivtv0 warning: 1000 ms time
> > out waiting for firmware
> > Dec 15 13:58:59 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000003 with result 0xfffffff0
> > Dec 15 13:58:59 localhost kernel: ivtv0 warning: DEC: error
> > changing speed Dec 15 13:58:59 localhost kernel: ivtv0 warning:
> > DEC: error in slow/fast mode Dec 15 13:59:09 localhost kernel:
> > ivtv0 warning: 1000 ms time out waiting for firmware
> > Dec 15 13:59:09 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000015 with result 0xfffffff0
> > Dec 15 13:59:09 localhost kernel: ivtv0 warning: DEC: couldn't read
> > clock Dec 15 13:59:20 localhost kernel: ivtv0 warning: 1000 ms time
> > out waiting for firmware
> > Dec 15 13:59:20 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000015 with result 0xfffffff0
> > Dec 15 13:59:20 localhost kernel: ivtv0 warning: DEC: couldn't read
> > clock Dec 15 13:59:30 localhost kernel: ivtv0 warning: 1000 ms time
> > out waiting for firmware
> > Dec 15 13:59:30 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000015 with result 0xfffffff0
> > Dec 15 13:59:30 localhost kernel: ivtv0 warning: DEC: couldn't read
> > clock Dec 15 13:59:40 localhost kernel: ivtv0 warning: 1000 ms time
> > out waiting for firmware
> > Dec 15 13:59:40 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000003 with result 0xfffffff0
> > Dec 15 13:59:40 localhost kernel: ivtv0 warning: DEC: error
> > changing speed Dec 15 13:59:40 localhost kernel: ivtv0 warning:
> > DEC: error in slow/fast mode Dec 15 13:59:50 localhost kernel:
> > ivtv0 warning: 1000 ms time out waiting for firmware
> > Dec 15 13:59:50 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000046 with result 0xfffffff0
> > Dec 15 14:00:00 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 14:00:00 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000044 with result 0xfffffff0
> > Dec 15 14:00:11 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 14:00:11 localhost kernel: ivtv0 warning: Failed api call
> > 0x0000004a with result 0xfffffff0
> > Dec 15 14:00:21 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 14:00:21 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000045 with result 0xfffffff0
> > Dec 15 14:00:31 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 14:00:31 localhost kernel: ivtv0 warning: Failed api call
> > 0x0000004b with result 0xfffffff0
> > Dec 15 14:00:41 localhost kernel: ivtv0 warning: 1000 ms time out
> > waiting for firmware
> > Dec 15 14:00:41 localhost kernel: ivtv0 warning: Failed api call
> > 0x00000050 with result 0xfffffff0
>
> You might want to try and set newi2c to 0 in /etc/modules.conf.
>
> option ivtv newi2c=1
>
> This (ivtv1: reopen i2c bus for IR-blaster support) afaik tells me it
> enables newi2c but Hans might want to correct me on this :-)
This has nothing to do with these problems. These messages you typically
get when the firmware has crashed. Steve, do you also see DMA errors in
the log? FC6 probably has some CPU frequency changer daemon running and
the DMA engine on the card does not handle that well. Make sure it is
not running.
Hans
>
>
> Greets
> Sander
>
> > ivtv: ==================== START INIT IVTV ====================
> > ivtv: version 0.8.2 (tagged release) loading
> > ivtv: Linux version: 2.6.18-1.2849.fc6 SMP mod_unload 686 REGPARM
> > 4KSTACKS 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 (cx23415 based)
> > ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 3
> > PCI: setting IRQ 3 as level-triggered
> > ACPI: PCI Interrupt 0000:02:0a.0[A] -> Link [LNKG] -> GSI 3 (level,
> > low) -> IRQ
> > 3
> > intel_rng: FWH not detected
> > hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
> > Uniform CD-ROM driver Revision: 3.20
> > input: PC Speaker as /class/input/input1
> > Floppy drive(s): fd0 is 1.44M
> > FDC 0 is a post-1991 82077
> > ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> > ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
> > tveeprom 0-0050: Hauppauge model 48132, rev K268, serial# 7614554
> > tveeprom 0-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47)
> > tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
> > tveeprom 0-0050: audio processor is MSP4448 (idx 27)
> > tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
> > tveeprom 0-0050: has radio, has IR remote
> > ivtv0: Autodetected Hauppauge WinTV PVR-350
> > tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
> > tda9887 0-0043: tda988[5/6/7] found @ 0x43 (tuner)
> > tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> > saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> > saa7127 0-0044: saa7129 found @ 0x88 (ivtv i2c driver #0)
> > msp3400 0-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0)
> > msp3400 0-0040: MSP4448G-A2 supports radio, mode is autodetect and
> > autoselect ivtv0: Encoder revision: 0x02050032
> > ivtv0: Decoder revision: 0x02020023
> > ivtv0: Registered device video0 for encoder MPEG
> > ivtv0: Registered device video32 for encoder YUV
> > ivtv0: Registered device vbi0 for encoder VBI
> > ivtv0: Registered device video24 for encoder PCM audio
> > ivtv0: Registered device radio0 for encoder radio
> > ivtv0: Registered device video16 for decoder MPEG
> > ivtv0: Registered device vbi8 for decoder VBI
> > ivtv0: Registered device vbi16 for decoder VOUT
> > ivtv0: Registered device video48 for decoder YUV
> > ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
> > tuner 0-0061: type set to 47 (LG NTSC (TAPE series))
> > spurious 8259A interrupt: IRQ7.
> > ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
> > ivtv: ====================== NEXT CARD ======================
> > ivtv1: Autodetected Hauppauge card (cx23416 based)
> > ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 11
> > ACPI: PCI Interrupt 0000:02:0d.0[A] -> Link [LNKF] -> GSI 11
> > (level, low) -> IRQ
> > 11
> > ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> > tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> > tveeprom 1-0050: Hauppauge model 26032, rev C199, serial# 8297203
> > tveeprom 1-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
> > tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> > tveeprom 1-0050: audio processor is CX25841 (idx 35)
> > tveeprom 1-0050: decoder processor is CX25841 (idx 28)
> > tveeprom 1-0050: has no radio, has IR remote
> > ivtv1: Autodetected Hauppauge WinTV PVR-150
> > ivtv1: reopen i2c bus for IR-blaster support
> > tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> > cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #1)
> > cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> > wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #1)
> > ivtv1: Encoder revision: 0x02050032
> > ivtv1: Registered device video1 for encoder MPEG
> > ivtv1: Registered device video33 for encoder YUV
> > ivtv1: Registered device vbi1 for encoder VBI
> > ivtv1: Registered device video25 for encoder PCM audio
> > tuner 1-0061: type set to 50 (TCL 2002N)
> > ivtv1: Initialized Hauppauge WinTV PVR-150, card #1
> > ivtv: ==================== END INIT IVTV ====================
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
