On 7/10/06, Raghuram Rajah <[EMAIL PROTECTED]> wrote:
BTW, here's my dmesg,
ivtv: no version for "struct_module" found: kernel tainted.
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.7.0 (tagged release) loading
ivtv: Linux version: 2.6.17-1.2145_FC5smp SMP mod_unload 686 REGPARM 4KSTACKS 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.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
ivtv0: This is the first unit of a PVR500
tuner 1-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tda9887 1-0043: chip found @ 0x86 (ivtv i2c driver #0)
cx25840 1-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
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: Create encoder radio stream
ivtv0: Initialized WinTV PVR 500 (unit #1), card #0
ivtv: ====================== NEXT CARD ======================
ivtv1: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
tda9887 2-0043: chip found @ 0x86 (ivtv i2c driver #1)
cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
ivtv1: This is the second unit of a PVR500
ivtv1: Correcting tveeprom data: no radio present on second unit
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: Initialized WinTV PVR 500 (unit #2), card #1
ivtv: ==================== END INIT IVTV ====================
----------------------------------------
> From: [EMAIL PROTECTED]
> To: [email protected]
> Subject: RE: Re: [ivtv-users] Trouble with upgrading Hauppage PVR-500 MCE from 0.4 to 0.7
> Date: Mon, 10 Jul 2006 17:24:54 -0400
>
> I am using kernel version 2.6.17 and ivtv 0.7. Can you give me some pointers as to where I can start looking to diagnose my issue?
>
> Thanks,
> Raghu.
>
>
>
>
> ----------------------------------------
> > To: [email protected]
> > Date: Mon, 10 Jul 2006 21:25:34 +0200
> > From: [EMAIL PROTECTED]
> > Subject: Re: [ivtv-users] Trouble with upgrading Hauppage PVR-500 MCE from 0.4 to 0.7
> >
> > On Mon, 2006-07-10 at 14:48 -0400, Raghuram Rajah wrote:
> > > I had a PVR-500MCE setup and working under ivtv 0.4 on Fedora 4.
> > > Recently, I attempted an upgrade to 0.7 along with a kernel upgrade to
> > > 2.6..2115, I don't see either video or audio anymore.
> >
> > Which kernel version do you have? But see below for which ivtv version
> > goes with which kernel.
> >
> > Kernel <= 2.6.15 use 0.4 series
> > Kernel = 2.6.16 use 0.6 series
> > Kernel = 2.6.17 use 0.7 series
> > Kernel = 2.6.18 use 0.8 series
> >
> > And hopefully it wil be in mainline by the time 2.6.19 is out.
> >
> > Correct me if i'm wrong hre :)
> >
> > So you need a 2.6.17 kernel to use 0.7 but I would not reccommend using
> > it for a "production" system. People have many issues with it. I would
> > stay with 0.6 (kernel 2.6.16) or the 0.4 (kernel <= 2.6.15) series.
> >
> > <snip>
> >
> > > With a input selection of 0 (using ivtvctl -p), I get noise for my
> > > video. Other inputs (1-4) results on a blank black screen. I checked
> > > my input coax multiple times to ensure a good fit. I tried all the
> > > options in the troubleshooting and documentation sections of
> > > ivtvdriver.org and Jared Wilson's HOWTO. Both tuners don't work.
> >
> > The input naming has changed. For example tuner0 is not tuner1. Same
> > should apply to the others but I never use those.
> >
> > >
> > > I have no idea as to where I can start to debug the issue. Any help
> > > will be much appreciated.
> > >
> > > Thanks,
> > > Raghu.
> >
> > Greets
> > Sander
> >
> >
> > _______________________________________________
> > ivtv-users mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
> _________________________________________________________________
> Express yourself: design your homepage the way you want it with Live.com.
> http://www.live.com/getstarted
_________________________________________________________________
Express yourself: design your homepage the way you want it with Live.com.
http://www.live.com/getstarted
_______________________________________________
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
