On Thursday 16 February 2006 18:46, Sean Holohan wrote:
> Hey guys, I installed mythtv on a box running FC4 and I'm having some
> trouble w/ my Hauppauge PVR 250.  I cat the contents of /dev/video0 but get
> nothing.  Here's some info:
>
> Using wilsonet.com's FC4 how-to, everything went fine until I tried
> testing the PVR-250 I have.  (Section 10 of wilson's how-to)
>
> I ran the ivtv install w/ no problem, added the NTSC entry into the
> /etc/modprobe.conf, and ran "depmod -ae" and "modprobe ivtv" w/ no
> errors.

Do you have any 'alias <module> <module>-ivtv' lines in modprobe.conf? If so, 
remove them and try again.


> Here's the ivtv content from /var/log/messages :
>
> Feb 12 23:00:37 localhost kernel: ivtv:  ==================== START INIT
> IVTV ====================
> Feb 12 23:00:37 localhost kernel: ivtv:  version 0.4.2 (tagged release)
> loading
> Feb 12 23:00:37 localhost kernel: ivtv:  Linux version:
> 2.6.15-1.1831_FC4686 REGPARM 4KSTACKS
> gcc-4.0
> Feb 12 23:00:37 localhost kernel: ivtv:  In case of problems please include
> the debug info between
> Feb 12 23:00:37 localhost kernel: ivtv:  the START INIT IVTV and END INIT
> IVTV lines, along with
> Feb 12 23:00:37 localhost kernel: ivtv:  any module options, when mailing
> the ivtv-users mailinglist.
> Feb 12 23:00:37 localhost kernel: ivtv0: Autodetected WinTV PVR 250 card
> (cx23416 based)
> Feb 12 23:00:37 localhost kernel: ACPI: PCI Interrupt Link [LNK4] enabled
> at IRQ 3
> Feb 12 23:00:37 localhost kernel: PCI: setting IRQ 3 as level-triggered
> Feb 12 23:00:37 localhost kernel: ACPI: PCI Interrupt 0000:02:07.0[A] ->
> Link [LNK4] -> GSI 3 (level, low) -> IRQ 3
> Feb 12 23:00:37 localhost kernel: ivtv0: Unreasonably low latency timer,
> setting to 64 (was 32)
> Feb 12 23:00:37 localhost kernel: ivtv0: Failed to load module tveeprom
> Feb 12 23:00:37 localhost kernel: ivtv0 warning: i2c client addr: 0x50 not
> found for command 0x0!
> Feb 12 23:00:38 localhost kernel: ivtv0: Error -19 reading Hauppauge
> eeprom. Feb 12 23:00:38 localhost kernel: ivtv0: Possible causes: the
> tveeprom module was not loaded, or
> Feb 12 23:00:38 localhost kernel: ivtv0: the eeprom kernel module was
> loaded before the tveeprom module.
> Feb 12 23:00:38 localhost kernel: tuner 2-0061: chip found @ 0xc2 (ivtv i2c
> driver #0)
> Feb 12 23:00:38 localhost kernel: ivtv0: i2c attach to card #0 ok
> [client=(tuner unset), addr=61]
> Feb 12 23:00:38 localhost kernel: saa7115 2-0021: saa7115 found @ 0x42
> (ivtv i2c driver #0)
> Feb 12 23:00:38 localhost kernel: ivtv0: i2c attach to card #0 ok
> [client=saa7115, addr=21]
> Feb 12 23:00:38 localhost kernel: ivtv0: Failed to load module msp3400
> Feb 12 23:00:38 localhost kernel: ivtv0: Could not detect tuner standard,
> defaulting to NTSC.
> Feb 12 23:00:38 localhost kernel: ivtv0: loaded v4l-cx2341x-enc.fw firmware
> (262144 bytes)
> Feb 12 23:00:38 localhost kernel: ivtv0: Encoder revision: 0x02040024
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: Encoder Firmware can be
> buggy, use version 0x02040011 or 0x02050032.
> Feb 12 23:00:38 localhost kernel: ivtv0: Allocate DMA encoder MPEG stream:
> 128 x 32768 buffers (4096KB total)
> Feb 12 23:00:38 localhost kernel: ivtv0: Allocate DMA encoder YUV stream:
> 194 x 10800 buffers (2048KB total)
> Feb 12 23:00:38 localhost kernel: ivtv0: Allocate DMA encoder VBI stream:
> 120 x 17472 buffers (2048KB total)
> Feb 12 23:00:38 localhost kernel: ivtv0: Allocate DMA encoder PCM audio
> stream: 455 x 4608 buffers (2048KB total)
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x40086d11!
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x80287610!
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x40287611!
> Feb 12 23:00:38 localhost kernel: tuner 2-0061: tuner type not set
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x40085618!
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x80287610!
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x40287611!
> Feb 12 23:00:38 localhost kernel: tuner 2-0061: tuner type not set
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x402c5639!
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x80287610!
> Feb 12 23:00:38 localhost kernel: ivtv0 warning: i2c client addr: 0x40 not
> found for command 0x40287611!
> Feb 12 23:00:38 localhost kernel: ivtv0: Initialized WinTV PVR 250, card #0
> Feb 12 23:00:38 localhost kernel: ivtv:  ====================  END INIT
> IVTV  ====================
>
>
> lspci -v | grep 250
>
> 02:07.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416)                MPEG-2 Encoder (rev 01)
>         Subsystem: Hauppauge computer works Inc. WinTV PVR 250
>         Flags: bus master, medium devsel, latency 64, IRQ 3
>         Memory at e4000000 (32-bit, prefetchable) [size=64M]
>         Capabilities: [44] Power Management version 2
>
>
> ls -ltr /dev/video*
>
> crw-------  1 mythtv root 81,  0 Feb 13 17:56 /dev/video0
> lrwxrwxrwx  1 root   root      6 Feb 13 17:56 /dev/video -> video0
> crw-------  1 mythtv root 81, 32 Feb 13 17:56 /dev/video32
> crw-------  1 mythtv root 81, 24 Feb 13 17:56 /dev/video24
>
>
> dmesg | grep Initialized
>
> ivtv0: Initialized WinTV PVR 250, card #0
>
>
> /usr/bin/ivtvctl -u 0x3000
> /usr/bin/ivtvctl -p 4
> /usr/bin/ivtvctl -f width=720,height=480
>
>
> mplayer -vo xv /dev/video0
>
> And I get nothing.  I tried different -p options.  0-8 gives me all the
> same result.
>
> I know the cable line isn't the problem (I can see the channels when I
> plug it directly into the TV).  Any ideas. Mucho thanks guys.  Can't wait
> to get the mythtv working!
>
> ~sean

-- 
Jarod Wilson
[EMAIL PROTECTED]

Attachment: pgpmEAJ7WSNei.pgp
Description: PGP signature

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

Reply via email to