On Wednesday 26 September 2007 07:19:59 Harondel J. Sibble wrote:
> Okay, my system has 3 Hauppauge PVR cards, 2x PVR 150's and 1x PVR
> 250. I've had problems on and off for a while now on my MythTV
> system, after a recent recording got badly recorded, I had another
> look at this and determined that tuning on this card (250) seems to
> be borked.
>
> Running Knoppmyth R5E50, with the latest manual update to Myth 0.20.2
> and ivtv 0.10.5
>
> You can see an example of the tuning problems here
>
> http://www.pdscc.com/troubleshooting/PVR-250-miss-tuning.jpg
>
> Here is the init stuff
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.10.5 (tagged release) loading
> ivtv: Linux version: 2.6.18-chw-13 SMP preempt mod_unload 586
> 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 card (cx23416 based)
> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv0: Encoder revision: 0x02060039
> ivtv0: Autodetected Hauppauge WinTV PVR-150
> ivtv0: reopen i2c bus for IR-blaster support
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> cx25840 1-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #0)
> wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
> ivtv0: Registered device video0 for encoder MPEG (4 MB)
> ivtv0: Registered device video32 for encoder YUV (2 MB)
> ivtv0: Registered device vbi0 for encoder VBI (1 MB)
> ivtv0: Registered device video24 for encoder PCM audio (1 MB)
> ivtv0: Initialized Hauppauge WinTV PVR-150, card #0
> ivtv: ====================== NEXT CARD ======================
> ivtv1: Autodetected Hauppauge card (cx23416 based)
> ivtv1: Unreasonably low latency timer, setting to 64 (was 32)
> ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv1: Encoder revision: 0x02060039
> tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> ivtv1: Autodetected Hauppauge WinTV PVR-250
> saa7115 2-0021: saa7115 found @ 0x42 (ivtv i2c driver #1)
> msp3400 2-0040: MSP3435G-B6 found @ 0x80 (ivtv i2c driver #1)
> ivtv1: Registered device video1 for encoder MPEG (4 MB)
> ivtv1: Registered device video33 for encoder YUV (2 MB)
> ivtv1: Registered device vbi1 for encoder VBI (1 MB)
> ivtv1: Registered device video25 for encoder PCM audio (1 MB)
> ivtv1: Initialized Hauppauge WinTV PVR-250, card #1
> ivtv: ====================== NEXT CARD ======================
> ivtv2: Autodetected Hauppauge card (cx23416 based)
> ivtv2: Unreasonably low latency timer, setting to 64 (was 32)
> ivtv2: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv2: Encoder revision: 0x02060039
> tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #2)
> cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #2)
> wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #2)
> ivtv2: Autodetected Hauppauge WinTV PVR-150
> ivtv2: reopen i2c bus for IR-blaster support
> tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #2)
> cx25840 3-0044: cx25841-23 found @ 0x88 (ivtv i2c driver #2)
> wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #2)
> ivtv2: Registered device video2 for encoder MPEG (4 MB)
> ivtv2: Registered device video34 for encoder YUV (2 MB)
> ivtv2: Registered device vbi2 for encoder VBI (1 MB)
> ivtv2: Registered device video26 for encoder PCM audio (1 MB)
> ivtv2: Initialized Hauppauge WinTV PVR-150, card #2
> ivtv: ==================== END INIT IVTV ====================
> lirc_pvr150: ivtv i2c driver #1: no devices found
>
>
> I originally started with just the PVR250 like 3 or 4 years ago and
> it worked great with ivtv. Now I don't see any messages about tuner
> issues per se in the logs.
>
> # dmesg | grep tuner
> tveeprom 1-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> tuner 1-0061: type set to 50 (TCL 2002N)
> tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> tveeprom 2-0050: tuner model is Philips FI1236 MK2 (idx 10, type 2)
> tuner 2-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and
> compatibles)) tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #2)
> tveeprom 3-0050: tuner model is TCL 2002N 5H (idx 99, type 50)
> tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #2)
> tuner 3-0061: type set to 50 (TCL 2002N)
>
> Tuner 2 seems right from what I remember. Even with latest firmware,
> still get the ugly channel tuning on all channels. Being that it's
> the second tuner, when multiple shows are set to record concurrently,
> the second one is mangled, of course if's usually the wife's show, so
> the WAF is low at the moment.
>
> lspci gives
>
> 00:09.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Hauppauge computer works Inc. WinTV PVR 150
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32
> bytes Interrupt: pin A routed to IRQ 10
> Region 0: Memory at e0000000 (32-bit, prefetchable)
> [size=64M] Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2- ,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:0a.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Hauppauge computer works Inc. WinTV PVR 250
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32
> bytes Interrupt: pin A routed to IRQ 11
> Region 0: Memory at e4000000 (32-bit, prefetchable)
> [size=64M] Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2- ,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> 00:0b.0 Multimedia video controller: Internext Compression Inc iTVC16
> (CX23416) MPEG-2 Encoder (rev 01)
> Subsystem: Hauppauge computer works Inc. WinTV PVR 150
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium
> >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64 (32000ns min, 2000ns max), Cache Line Size: 32
> bytes Interrupt: pin A routed to IRQ 7
> Region 0: Memory at e8000000 (32-bit, prefetchable)
> [size=64M] Capabilities: [44] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2- ,D3hot-,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> There are no additional module options than the basic defaults now
> that ivtv autodetects most things.
>
> alias char-major-81 videodev
> alias char-major-81-1 ivtv
>
> Any suggestions on what to change or to look at to resolve the tuning
> issues with the PVR250. I guess I could have a bad card, although I
> am about 70% certain it will occaisionally tune and record
> properly... <shrug>
>
> P.S. since upgrading to the latest firmware tonight, tuning on tuner1
> (150) also seems to be not so good. :-(
I've been reading reports that the FI/FM1236 tuner support has become
worse for some time now. I've looked at the tuner kernel source without
finding anything relevant.
Can you help me out by installing the latest v4l-dvb drivers from
www.linuxtv.org/hg/v4l-dvb? If it still happens with the latest and
greatest tuner drivers, then I'll take another look. I can't imagine
what could cause this problem, but you're not the first to complain.
I might have a PVR-250 with a similar tuner at home, but I won't be able
to test that for another two weeks.
Regards,
Hans
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
