On 12/02/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi guys.  Thanks so much for providing support on IVTV.   I'm hoping
> that you will be able to help me out with my current project.
>
> I'm building a PVR using a VIA Epia 800 with a Hauppauge PVR-350 card.
> In order to simplify things, I decided to use Fedora Core 4, MythTv,
> and follow Mr. Wilson's excellent tutorial.  I would have been dead in
> the water without it.
>

It hasn't been updated in a while and there are big changes afoot with
both ivtv and DVB support in the kernel.

> At any rate, here is my current situation.  I can get the PVR to output
> the test pattern.  However, when I do the test capture, all I get is
> static.  I've played around with ivtv-tune and nothing but static.  I
> could be using the wrong settings, but I set my input to 4 (tuner) and
> used the us-cable channels, which I think is correct for my setup.
>

Seems OK

> Worth noting it that # cat /var/log/messages |grep "iTVC15 TV out"
> returns no hits.  However, cat /var/log/messages |grep "TV out"
> returns:
> Feb 12 11:56:52 mythtv kernel: ivtv0-osd: fb1: cx23415 TV out frame
> buffer device
> I think perhaps Hauppauge has made some changes to this card?

More likely due to changes in the ivtv drivers.

> I can load up ivtv without any visible errors, but /var/log/messages
> indicates the some errors (using script from wilsonnet.com), see below.
>
> Any ideas guys?  Thanks in advance, S Price.  Details follow
>
> Feb 12 11:56:49 mythtv kernel: ivtv:  ==================== START INIT
> IVTV ====================
> Feb 12 11:56:49 mythtv kernel: ivtv:  version 0.4.2 (tagged release)
> loading
> Feb 12 11:56:49 mythtv kernel: ivtv:  Linux version: 2.6.15-1.1831_FC4
> 586 REGPARM 4KSTACKS gcc-4.0
> Feb 12 11:56:50 mythtv kernel: ivtv:  In case of problems please include
> the debug info between
> Feb 12 11:56:50 mythtv kernel: ivtv:  the START INIT IVTV and END INIT
> IVTV lines, along with
> Feb 12 11:56:50 mythtv kernel: ivtv:  any module options, when mailing
> the ivtv-users mailinglist.
> Feb 12 11:56:50 mythtv kernel: ivtv0: Autodetected WinTV PVR 350 card
> (cx23415 based)
> Feb 12 11:56:50 mythtv kernel: ACPI: PCI Interrupt Link [LNKB] enabled
> at IRQ 10
> Feb 12 11:56:50 mythtv kernel: PCI: setting IRQ 10 as level-triggered
> Feb 12 11:56:50 mythtv kernel: ACPI: PCI Interrupt 0000:00:14.0[A] ->
> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
> Feb 12 11:56:50 mythtv kernel: ivtv0: Unreasonably low latency timer,
> setting to 64 (was 32)
> Feb 12 11:56:50 mythtv kernel: ivtv0: Failed to load module tveeprom
> Feb 12 11:56:50 mythtv kernel: ivtv0 warning: i2c client addr: 0x50 not
> found for command 0x0!


> Feb 12 11:56:50 mythtv kernel: ivtv0: Error -19 reading Hauppauge
> eeprom.
> Feb 12 11:56:50 mythtv kernel: ivtv0: Possible causes: the tveeprom
> module was not loaded, or
> Feb 12 11:56:50 mythtv kernel: ivtv0: the eeprom kernel module was
> loaded before the tveeprom module.
> Feb 12 11:56:50 mythtv kernel: ivtv0: Failed to load module tuner

These errors are the cause of your troubles. It is highly likely the
ivtv modules are conflicting with the kernel-provided modules.

> Feb 12 11:56:50 mythtv kernel: ivtv0: Failed to load module msp3400
> Feb 12 11:56:50 mythtv kernel: ivtv0: Failed to load module tda9887
> Feb 12 11:56:50 mythtv kernel: ivtv0: Could not detect tuner standard,
> defaulting to NTSC.

And more of the same ...

> Also, because I know this would be my next question, here's what my
> modprobe.conf looks like:
>
> alias eth0 via-rhine
> alias char-major-61 lirc_i2c
> alias snd-card-0 snd-via82xx
> options snd-card-0 index=0
> options snd-via82xx index=0
> remove snd-via82xx { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; };
> /sbin/modprobe -r --ignore-remove snd-via82xx
>
> # ivtv modules setup
> alias char-major-81 ivtv
> alias char-major-81-0 ivtv
> alias tveeprom tveeprom-ivtv
> # added these 02/09/06
> alias tuner tuner-ivtv
> alias tda9887 tda9887-ivtv
> alias msp3400 msp3400-ivtv
> # end new
> install ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe
> ivtv-fb

Have you tried running without the ivtv aliases for tveeprom, tuner,
tda and msp3400? Have you read the ivtv documentation for any
late-breaking information running with a 2.6.15 kernel?

Nick

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

Reply via email to