On Saturday 13 October 2007 15:16:01 J. David Maino wrote:
> Hans,
>
> Thanks for taking a look at this. Below is the dmesg output. I can't
> see anything that jumps out at me, but then again I'm kind of a
> technocripple about some of these things so I'm not sure what exactly
> I should be looking for.
Looks OK to me. When you change channels on the first tuner, do you see
any messages in the kernel log? Do you see the 'static' change as well?
Usually changing channels will cause a change in what the static looks
like. If that doesn't happen then the tuner isn't working.
Regards,
Hans
>
> [ 90.387093] ivtv: ==================== START INIT IVTV
> ====================
> [ 90.387098] ivtv: version 1.0.0 (2.6.22-14-generic SMP mod_unload
> 586 ) loading
> [ 90.387557] ivtv0: Autodetected Hauppauge card (cx23416 based)
> [ 90.387780] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> [ 90.387789] ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [APC1] ->
> GSI 16 (level, high) -> IRQ 21
> [ 90.387801] ivtv0: Unreasonably low latency timer, setting to 64
> (was 32) [ 90.513279] ACPI: PCI Interrupt Link [APCJ] enabled at
> IRQ 20 [ 90.513286] ACPI: PCI Interrupt 0000:00:06.0[A] -> Link
> [APCJ] -> GSI 20 (level, high) -> IRQ 18
> [ 90.513313] PCI: Setting latency timer of device 0000:00:06.0 to
> 64 [ 90.836972] intel8x0_measure_ac97_clock: measured 52836 usecs [
> 90.836976] intel8x0: clocking to 47404
> [ 90.990358] input: ImExPS/2 Generic Explorer Mouse as
> /class/input/input3 [ 90.994284] parport_pc 00:0c: reported by Plug
> and Play ACPI [ 90.994343] parport0: PC-style at 0x378 (0x778), irq
> 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
> [ 91.123239] ivtv0: loaded v4l-cx2341x-enc.fw firmware (3753078952
> bytes) [ 91.336548] ivtv0: Encoder revision: 0x02050032
> [ 91.336552] ivtv0: Recommended firmware version is 0x02060039.
> [ 91.397333] tveeprom 2-0050: Hauppauge model 23552, rev D492,
> serial# 7971869
> [ 91.397338] tveeprom 2-0050: tuner model is Philips FQ1236A MK4
> (idx 92, type 57)
> [ 91.397341] tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
> [ 91.397344] tveeprom 2-0050: second tuner model is Philips
> TEA5768HL FM Radio (idx 101, type 62)
> [ 91.397347] tveeprom 2-0050: audio processor is CX25843 (idx 37)
> [ 91.397349] tveeprom 2-0050: decoder processor is CX25843 (idx 30)
> [ 91.397352] tveeprom 2-0050: has radio, has no IR receiver, has no
> IR transmitter
> [ 91.397355] ivtv0: Autodetected WinTV PVR 500 (unit #1)
> [ 91.425947] tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0)
> [ 91.425998] tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> [ 91.429622] tuner 2-0060: TEA5767 detected.
> [ 91.429625] tuner 2-0060: chip found @ 0xc0 (ivtv i2c driver #0)
> [ 91.429637] tuner 2-0060: type set to 62 (Philips TEA5767HN FM
> Radio) [ 91.429864] tuner 2-0061: chip found @ 0xc2 (ivtv i2c
> driver #0) [ 91.459508] cx25840 2-0044: cx25843-23 found @ 0x88
> (ivtv i2c driver #0) [ 94.665316] cx25840 2-0044: loaded
> v4l-cx25840.fw firmware (16382 bytes) [ 94.765283] wm8775 2-001b:
> chip found @ 0x36 (ivtv i2c driver #0) [ 94.809714] tuner 2-0061:
> type set to 57 (Philips FQ1236A MK4) [ 95.123074] ivtv0: Registered
> device video0 for encoder MPEG (4 MB) [ 95.123346] ivtv0:
> Registered device video32 for encoder YUV (2 MB) [ 95.123640]
> ivtv0: Registered device vbi0 for encoder VBI (1 MB) [ 95.123843]
> ivtv0: Registered device video24 for encoder PCM audio (1 MB) [
> 95.124130] ivtv0: Registered device radio0 for encoder radio [
> 95.147507] ivtv0: Initialized WinTV PVR 500 (unit #1), card #0 [
> 95.147579] ivtv: ====================== NEXT CARD
> ======================
> [ 95.147584] ivtv1: Autodetected Hauppauge card (cx23416 based)
> [ 95.147640] ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [APC2] ->
> GSI 17 (level, high) -> IRQ 19
> [ 95.147653] ivtv1: Unreasonably low latency timer, setting to 64
> (was 32) [ 95.789886] ivtv1: loaded v4l-cx2341x-enc.fw firmware
> (3753080128 bytes) [ 96.004359] ivtv1: Encoder revision: 0x02050032
> [ 96.004361] ivtv1: Recommended firmware version is 0x02060039.
> [ 96.008961] tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #1)
> [ 96.009049] tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner)
> [ 96.012021] tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> [ 96.027301] cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c
> driver #1) [ 99.232771] cx25840 3-0044: loaded v4l-cx25840.fw
> firmware (16382 bytes) [ 99.304342] wm8775 3-001b: chip found @
> 0x36 (ivtv i2c driver #1) [ 99.372120] tveeprom 3-0050: Hauppauge
> model 23552, rev D492, serial# 7971869
> [ 99.372125] tveeprom 3-0050: tuner model is Philips FQ1236A MK4
> (idx 92, type 57)
> [ 99.372128] tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
> [ 99.372131] tveeprom 3-0050: second tuner model is Philips
> TEA5768HL FM Radio (idx 101, type 62)
> [ 99.372134] tveeprom 3-0050: audio processor is CX25843 (idx 37)
> [ 99.372136] tveeprom 3-0050: decoder processor is CX25843 (idx 30)
> [ 99.372139] tveeprom 3-0050: has radio, has no IR receiver, has no
> IR transmitter
> [ 99.372142] ivtv1: Correcting tveeprom data: no radio present on
> second unit
> [ 99.372144] ivtv1: Autodetected WinTV PVR 500 (unit #2)
> [ 99.439442] tuner 3-0061: type set to 57 (Philips FQ1236A MK4)
> [ 99.751008] ivtv1: Registered device video1 for encoder MPEG (4
> MB) [ 99.751305] ivtv1: Registered device video33 for encoder YUV
> (2 MB) [ 99.751631] ivtv1: Registered device vbi1 for encoder VBI
> (1 MB) [ 99.751844] ivtv1: Registered device video25 for encoder
> PCM audio (1 MB) [ 99.774245] ivtv1: Initialized WinTV PVR 500
> (unit #2), card #1 [ 99.777575] ivtv: ==================== END
> INIT IVTV
> ===================
>
> > Message: 7
> > Date: Fri, 12 Oct 2007 19:07:12 +0200
> > From: Hans Verkuil <[EMAIL PROTECTED]>
> > Subject: Re: [ivtv-users] PVR-500 Kernel 2.6.22-12
> > To: User discussion about IVTV <[email protected]>
> > Message-ID: <[EMAIL PROTECTED]>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > On Sunday 07 October 2007 08:51:18 J. David Maino wrote:
> >> Hello all,
> >>
> >> I have a PVR-500 with the Phillips Tuners and recently upgraded my
> >> mythtv backend machine to Ubuntu Gutsy Gibbon, which uses the
> >> 2.6.22-12 kernel. Prior to this I was using the 2.6.17 kernel with
> >> the 0.7 driver installed and configured by hand. With .22, it
> >> recognized the tuner right away, but tuner 1 is all static and you
> >> can't make out a picture, while tuner 2 is clear as day. I've
> >> tried recompiling the kernel to see if there are some modules that
> >> were left out, based on what info I could find on the ivtv
> >> website, but I haven't been able to find any other info on this
> >> problem and I'm wondering if I should just break down and go back
> >> to a manually reconfigured 2.6.17 kernel or if there are some
> >> other things I should look at first.
> >>
> >> Any help you could offer would be greatly appreciated.
> >
> > Doesn't ring a bell. Can you give the dmesg output? Do you get any
> > suspicious message there?
> >
> > Regards,
> >
> > Hans
>
> _______________________________________________
> 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
