Jim C. wrote: >> ivtv: ==================== START INIT IVTV ==================== >> ivtv: version 0.7.0 (tagged release) loading >> ivtv: Linux version: 2.6.17-1.2157_FC5 SMP mod_unload 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. >> eth0: forcedeth.c: subsystem: 0cb84:10de bound to 0000:00:0a.0 >> ACPI: PCI Interrupt Link [APCL] enabled at IRQ 20 >> GSI 19 sharing vector 0x32 and IRQ 19 >> ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [APCL] -> GSI 20 (level, low) -> >> IRQ 50 >> PCI: Setting latency timer of device 0000:00:02.1 to 64 >> ehci_hcd 0000:00:02.1: EHCI Host Controller >> ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1 >> ehci_hcd 0000:00:02.1: debug port 1 >> PCI: cache line size of 64 is not supported by device 0000:00:02.1 >> ehci_hcd 0000:00:02.1: irq 50, io mem 0xfeb00000 >> ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 >> usb usb1: configuration #1 chosen from 1 choice >> hub 1-0:1.0: USB hub found >> hub 1-0:1.0: 10 ports detected >> ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 23 >> ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 23 (level, low) -> >> IRQ 217 >> PCI: Setting latency timer of device 0000:00:04.0 to 64 >> intel8x0_measure_ac97_clock: measured 58610 usecs >> intel8x0: clocking to 47019 >> ivtv0: Autodetected Hauppauge WinTV PVR-350 card (cx23415 based) >> ACPI: PCI Interrupt Link [APCF] enabled at IRQ 22 >> ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [APCF] -> GSI 22 (level, low) -> >> IRQ 225 >> PCI: Setting latency timer of device 0000:00:02.0 to 64 >> ohci_hcd 0000:00:02.0: OHCI Host Controller >> ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2 >> ohci_hcd 0000:00:02.0: irq 225, io mem 0xfebff000 >> ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 >> GSI 20 sharing vector 0x3A and IRQ 20 >> ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> >> IRQ 58 >> ivtv0: Unreasonably low latency timer, setting to 64 (was 32) >> tveeprom 2-0050: Hauppauge model 48132, rev K268, serial# 8083237 >> tveeprom 2-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47) >> tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) >> tveeprom 2-0050: audio processor is MSP4448 (idx 27) >> tveeprom 2-0050: decoder processor is SAA7115 (idx 19) >> tveeprom 2-0050: has radio, has IR remote >> usb usb2: configuration #1 chosen from 1 choice >> hub 2-0:1.0: USB hub found >> hub 2-0:1.0: 10 ports detected >> tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) >> tda9887 2-0043: chip found @ 0x86 (ivtv i2c driver #0) >> saa7115 2-0021: saa7115 found @ 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) >> msp3400 2-0040: MSP4448G-A2 supports radio, mode is autodetect and autoselect >> 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) >> ivtv0: Create encoder radio stream >> ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) >> ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) >> ivtv0: Create decoder VOUT stream >> ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) >> ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes) >> tuner 2-0061: type set to 47 (LG NTSC (TAPE series)) >> ivtv0: Initialized Hauppauge WinTV PVR-350, card #0 >> ivtv: ==================== END INIT IVTV ====================
It looks to me like your card is up and running. The firmware(s) got loaded, and your messages look remarkably similar to mine. In fact, we seem to have the same card model and rev (your serial# is higher than mine tho). I suppose the next thing to look at would be to dump the card status to the log file. What does "ivtvctl --log-status" show? -- Kevin J. Cummings [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Registered Linux User #1232 (http://counter.li.org) _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
