First try ivtv version 0.4.0 instead of the not-yet-final 0.4.1. If it
still fails with pretty much the same errors then I recommend testing
on a Windows system if you can do that. It smells like a hardware
problem. The driver cannot find certain chips that really should be
there.
Hans
On Sunday 27 November 2005 20:12, Chris MacDonald wrote:
> I'm new to this mailing list stuff so you'll have to excuse any
> blatant faux-pas... apologies in advance.
>
> I've been tinkering with this new pvr 500 for a day or two now and
> I'm no further along than when I started. I've bene following the
> from-source howto on the ivtv wiki. I'm running FC4 with a 2.6.14
> kernel and version 0.4.1 of the ivtv driver.
>
> Currently I get black video from /dev/video0, and nothing at all from
> /dev/video1 (cat /dev/video1 > test.mpeg results in a 0-length file).
> I've been looking at the dmesg output from other users here with the
> pvr 500 and it's clear there's something wrong but I'm at a loss as
> to what the problem is...
>
> The output from lspci -v:
>
> 02:08.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Hauppauge computer works Inc.: Unknown device e807
> Flags: bus master, medium devsel, latency 64, IRQ 5
> Memory at d8000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [44] Power Management version 2
>
> 02:09.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Hauppauge computer works Inc.: Unknown device e817
> Flags: bus master, medium devsel, latency 64, IRQ 10
> Memory at d4000000 (32-bit, prefetchable) [size=64M]
> Capabilities: [44] Power Management version 2
>
> To me this looks just fine... now for dmesg:
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.4.1 (development snapshot compiled on Sun 27 Nov
> 2005 07:15:00 AM EST) loading
> ivtv: Linux version: 2.6.14-1.1637_FC4 686 REGPARM 4KSTACKS gcc-4.0
> 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 150 card (cx23416 based)
> ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKC] -> GSI 5 (level,
> low) -> IRQ 5
> tveeprom: Second (radio) tuner idx 101
> tveeprom: ivtv version
> tveeprom: Hauppauge: model = 23552, rev = D592, serial# = 8221138
> tveeprom: tuner = Philips FQ1236A MK4 (idx = 92, type = 57)
> tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
> tveeprom: audio processor = CX25843 (type = 25)
> tveeprom: decoder processor = CX25843 (type = 1e)
> ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
> ivtv0: This is the first unit of a PVR500
> cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
> cx25840 1-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
> ivtv0: i2c attach to card #0 ok [client=cx25840, addr=44]
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> ivtv0: i2c attach to card #0 ok [client=wm8775, addr=1b]
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv0: Encoder revision: 0x02050032
> 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 warning: i2c client addr: 0x00 not found for command
> 0x40045403! ivtv0 warning: i2c client addr: 0x00 not found for
> command 0x40085618! ivtv0 warning: i2c client addr: 0x00 not found
> for command 0x402c5639! ivtv0: Initialized WinTV PVR 500 (unit #1),
> card #0
> ivtv: ====================== NEXT CARD ======================
> ivtv1: Autodetected WinTV PVR 150 card (cx23416 based)
> ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
> ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKD] -> GSI 10 (level,
> low) -> IRQ 10
> tveeprom: Encountered bad packet header [ff]. Corrupt or not a
> Hauppauge eeprom.
> ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50]
> cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
> cx25840 2-0044: loaded v4l-cx25840.fw firmware (14264 bytes)
> ivtv1: i2c attach to card #1 ok [client=cx25840, addr=44]
> wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
> ivtv1: i2c attach to card #1 ok [client=wm8775, addr=1b]
> ivtv1: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> ivtv1: Encoder revision: 0x02050032
> ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB
> total) ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers
> (2048KB total) ivtv1: Allocate DMA encoder VBI stream: 120 x 17472
> buffers (2048KB total) ivtv1: Allocate DMA encoder PCM audio stream:
> 455 x 4608 buffers (2048KB total)
> ivtv1 warning: i2c client addr: 0x00 not found for command
> 0x40045403! ivtv1 warning: i2c client addr: 0x00 not found for
> command 0x40085618! ivtv1 warning: i2c client addr: 0x00 not found
> for command 0x402c5639! ivtv1: Initialized WinTV PVR 150, card #1
> ivtv: ==================== END INIT IVTV ====================
>
> The ivtv0/1 warnings worry me, as does that eeprom error. Firmware
> versions are listed in that output, and they're ones from the
> firmware versions portion of the wiki as the ones linked directly
> from the firmware howto produced a warning message that they may not
> be stable. Little good it did as the warnings and the eeprom error
> have remained.
>
> There are other interesting bits from ivtv-detect...
>
> [EMAIL PROTECTED] ~]# ivtv-detect
> driver: ivtv-0.4.1 (development snapshot compiled on Sun 27 Nov
> 2005 07:15:00 AM EST)
> card: WinTV PVR 500 (unit #1), bus info 0000:02:08.0, ivtv card
> #0 hardware: cx25840 wm8775 tveeprom
> /dev/video0: MPG encoding (links: /dev/video)
> /dev/vbi0: VBI encoding (links: /dev/vbi)
> /dev/video24: PCM encoding
> /dev/video32: YUV encoding
>
> driver: ivtv-0.4.1 (development snapshot compiled on Sun 27 Nov
> 2005 07:15:00 AM EST)
> card: WinTV PVR 150, bus info 0000:02:09.0, ivtv card #1
> hardware: cx25840 wm8775 tveeprom
> /dev/video1: MPG encoding
> /dev/vbi1: VBI encoding
> /dev/video25: PCM encoding
> /dev/video33: YUV encoding
>
> Seems the second card isn't getting picked up quite properly... not
> being recognised as part of the pvr 500? Again, the only rason I say
> this is because the output looks different than that of others with
> the same card. This might be why I get nothing from video1, but still
> doesn't explain the black video0.
>
> It would appear as though I might have two distinct problems here,
> but any insight as to why this might not be 'working' would be
> wonderful.
>
> Toodles,
> Chris MacDonald
>
>
> _______________________________________________
> 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
