Mike,
Okay, thanks. I deleted the options when I load the modules and now I see:
ivtv: i2c client addr: 0x44 not found!
as well as the "Decoder firmware dead!" messages I saw earlier.
I'll install a newer kernel so I can use the tuner patch, but in the meantime
I should be able to use composite, right?
Jim
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.3.2 (a) loading
ivtv: Linux version: 2.4.26
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 150 card
ivtv: Found an iTVC16 based chip
ivtv: VIA PCI device: 0x3099 vendor: 0x1106
tuner: chip found @ 0xc2
ivtv: i2c attach [client=(tuner unset),ok]
i2c-core.o: client [(tuner unset)] registered to adapter [ivtv i2c driver
#0](pos. 0).
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
wm8775: starting probe for adapter ivtv i2c driver #0 (0x10005)
wm8775: detecting client on address 0x36
wm8775: writing init values
ivtv: i2c attach [client=wm8775[0],ok]
i2c-core.o: client [wm8775[0]] registered to adapter [ivtv i2c driver #0](pos.
1).
i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
ivtv: Encoder revision: 0x02050032
ivtv: Encoder Firmware may be buggy, use version 0x02040011
ivtv: Configuring WinTV PVR 150 card with 4 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: ivtv_enc_thread: pid = 6991, itv = 0xc8a4fec0
ivtv: Could not detect tuner standard, defaulting to NTSC.
tuner: tuner type not set
ivtv: i2c client addr: 0x44 not found!
ivtv: Switching standard to NTSC.
tuner: tuner type not set
ivtv: i2c client addr: 0x44 not found!
ivtv: Initialized WinTV PVR 150, card #0
ivtv: ==================== END INIT IVTV ====================
ivtv: i2c client addr: 0x44 not found!
----- Original Message -----
From: "Michael T. Dean" <[EMAIL PROTECTED]>
To: [email protected]
Subject: Re: [ivtv-devel] pvr-150 installation problems
Date: Tue, 28 Dec 2004 03:09:56 -0500
>
> On 12/28/04 00:25, Jim Hammack wrote:
>
> > I'm trying to install a pvr-150 on an AMD Athlon system running
> > Slackware 10.0 with kernel 2.4.26. I'm using ivtv-0.3.2a
> > (earlier versions locked up when I tried "modprobe ivtv".
> > Modules seem to load okay
> > ...
> > Here's the rest of dmesg output (prior to the firmware reload):
> > ...
> > tveeprom: tuner = TCL 2002N 6A (idx = 85, type = 50)
> > ...
> > tuner(bttv): type forced to 2 (Philips NTSC (FI1236,FM1236 and
> > compatibles)) [insmod]
> >
> >
> a) Do *NOT* specify any options for your card. The driver
> correctly detects your tuner type (50), but your module options
> force it to use the wrong type (2).
> b) Do *NOT* use insmod to load the modules. All modules will be
> automatically loaded by the driver if you specify "modprobe ivtv"
> (which it sounds like you're doing). Therefore, clean up your
> modules.conf (and any other files used by your distro's module
> loading scripts) to prevent loading of the modules used by ivtv
> (i.e. tuner, tveeprom, msp3400, saa7115, saa7127 (if you also have
> a PVR-350), etc.).
> c) You have a TCL 2002N (type 50) tuner. Support for the TCL 2002N
> was added to the tuner module distributed with Linux 2.6.10. Based
> on the information you've provided--because of the module option
> forcing the tuner type to 2--I can't tell if you have a patched
> tuner module that supports your tuner. If not, you'll get snow
> until you patch the module as described at
> http://ivtv.no-ip.com/new_tuners/
>
> None of these points address the specific problem you're having,
> but it's quite possible that the problem is caused by the module
> options that are being specified. Therefore, please correct your
> configuration, and if the problem still exists, send another
> message showing the new output from ivtv initialization.
>
> HTH.
>
> Mike
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading
> now. http://productguide.itmanagersjournal.com/
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
Jim Hammack
[EMAIL PROTECTED]
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
