Mailing List Archive: ivtv: users

Is HVR-1600 model 74591 supported by cx18 driver?

Index | Next | Previous | View Threaded

matt.beadon at gmail

May 1, 2009, 11:26 AM

Post #1 of 9 (3122 views)
Permalink

Is HVR-1600 model 74591 supported by cx18 driver?

Originally posted a long description of my problems here:
http://www.gossamer-threads.com/lists/mythtv/users/380947#380947
What it boils down to first of all is the Hauppauge HVR-1600 model 74591
supported by the cx18 driver?

I'm really starting to think that this different model # is the key to my
problems since I have:

tveeprom 1-0050: Hauppauge model 74591, rev C1A4, serial#

and everything I've found online has been like this one:

tveeprom 5-0050: Hauppauge model 74041, rev C6B2, serial# xxxxxxx

Here's a more complete dump of my dmesg (note that my system has a working
PVR-500 card as well:

Linux video capture interface: v2.00
ivtv: Start initialization, version 1.4.1
ivtv0: Initializing card 0
ivtv0: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 18
ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [LNKB] -> GSI 18 (level, low) ->
IRQ 18
tveeprom 0-0050: Hauppauge model 23552, rev D492, serial#
tveeprom 0-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101,
type 62)
tveeprom 0-0050: audio processor is CX25843 (idx 37)
tveeprom 0-0050: decoder processor is CX25843 (idx 30)
tveeprom 0-0050: has radio
ivtv0: Autodetected WinTV PVR 500 (unit #1)
cx18: Start initialization, version 1.1.0
cx18-0: Initializing card 0
cx18-0: Autodetected Hauppauge card
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 17
ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNKA] -> GSI 17 (level, low) ->
IRQ 17
cx18-0: cx23418 revision 01010000 (B)
cx25840 0-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0)
lirc_dev: lirc_register_plugin: sample_rate: 0
lirc_mceusb2[2]: Philips eHome Infrared Transceiver on usb1:2
usbcore: registered new interface driver lirc_mceusb2
tveeprom 1-0050: Hauppauge model 74591, rev C1A4, serial#
tveeprom 1-0050: MAC address is 00-0D-FE-19-B8-32
tveeprom 1-0050: tuner model is TCL MNM05-4 (idx 104, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX23418 (idx 38)
tveeprom 1-0050: decoder processor is CX23418 (idx 31)
tveeprom 1-0050: has no radio
cx18-0: Autodetected Hauppauge HVR-1600
cx18-0: tveeprom cannot autodetect tuner!<6>cx18-0: Simultaneous Digital and
Analog TV capture supported

> The previous two lines seem to contradict each other. What's happening
> here?

tuner 0-0060: chip found @ 0xc0 (ivtv i2c driver #0)
tea5767 0-0060: type set to Philips TEA5767HN FM Radio
tuner 0-0043: chip found @ 0x86 (ivtv i2c driver #0)
tda9887 0-0043: creating new instance
tda9887 0-0043: tda988[5/6/7] found
ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LAZA] -> GSI 23 (level, low) ->
IRQ 23
PCI: Setting latency timer of device 0000:00:09.0 to 64
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
tda9887 2-0043: creating new instance
tda9887 2-0043: tda988[5/6/7] found
wm8775 0-001b: chip found @ 0x36 (ivtv i2c driver #0)
hda_codec: Unknown model for ALC883, trying auto-probe from BIOS...
tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
DVB: registering new adapter (cx18)
tuner-simple 0-0061: creating new instance
tuner-simple 0-0061: type set to 57 (Philips FQ1236A MK4)
ivtv0: Registered device video1 for encoder MPG (4096 kB)
ivtv0: Registered device video33 for encoder YUV (2048 kB)
ivtv0: Registered device vbi1 for encoder VBI (1024 kB)
ivtv0: Registered device video25 for encoder PCM (320 kB)
ivtv0: Registered device radio1 for encoder radio
ivtv0: Initialized card: WinTV PVR 500 (unit #1)
ivtv1: Initializing card 1
ivtv1: Autodetected Hauppauge card (cx23416 based)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 16
ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [LNKC] -> GSI 16 (level, low) ->
IRQ 16
tveeprom 3-0050: Hauppauge model 23552, rev D492, serial#
tveeprom 3-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57)
tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio (idx 101,
type 62)
tveeprom 3-0050: audio processor is CX25843 (idx 37)
tveeprom 3-0050: decoder processor is CX25843 (idx 30)
tveeprom 3-0050: has radio
ivtv1: Correcting tveeprom data: no radio present on second unit
ivtv1: Autodetected WinTV PVR 500 (unit #2)
cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #1)
tda9887 3-0043: creating new instance
tda9887 3-0043: tda988[5/6/7] found
tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1)
wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1)
MXL5005S: Attached at address 0x63
DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
cx18-0: DVB Frontend registered
cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)
cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
cx18-0: Initialized card: Hauppauge HVR-1600
tuner-simple 3-0061: creating new instance
tuner-simple 3-0061: type set to 57 (Philips FQ1236A MK4)
ivtv1: Registered device video2 for encoder MPG (4096 kB)
ivtv1: Registered device video34 for encoder YUV (2048 kB)
ivtv1: Registered device vbi2 for encoder VBI (1024 kB)
ivtv1: Registered device video26 for encoder PCM (320 kB)
ivtv1: Initialized card: WinTV PVR 500 (unit #2)
ivtv: End initialization
cx18: End initialization

thanks!

awalls at radix

May 1, 2009, 1:20 PM

Post #2 of 9 (2983 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

On Fri, 2009-05-01 at 11:26 -0700, Matt Beadon wrote:
> Originally posted a long description of my problems
> here: http://www.gossamer-threads.com/lists/mythtv/users/380947#380947

Ah, I see Dale has been helping you out. He was a very patient
tester. :)

> What it boils down to first of all is the Hauppauge HVR-1600 model
> 74591 supported by the cx18 driver?

In a generic sense, yes all HVR-1600's from 74000-74999 are.

> I'm really starting to think that this different model # is the key to
> my problems since I have:
> tveeprom 1-0050: Hauppauge model 74591, rev C1A4, serial#
>
>
> and everything I've found online has been like this one:
> tveeprom 5-0050: Hauppauge model 74041, rev C6B2, serial#
> xxxxxxx

It's could be a reason why analog TV may not work. Composite or SVideo
should certainly be OK. Have you tried those?

> Here's a more complete dump of my dmesg (note that my system has a
> working PVR-500 card as well:

I've snipped out the PVR-500 stuff...

> Linux video capture interface: v2.00
> cx18: Start initialization, version 1.1.0
> cx18-0: Initializing card 0
> cx18-0: Autodetected Hauppauge card
> ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 17
> ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNKA] -> GSI 17 (level,
> low) -> IRQ 17
> cx18-0: cx23418 revision 01010000 (B)
> tveeprom 1-0050: Hauppauge model 74591, rev C1A4, serial#
> tveeprom 1-0050: MAC address is 00-0D-FE-19-B8-32
> tveeprom 1-0050: tuner model is TCL MNM05-4 (idx 104, type 4)

The tveeprom module can decode the EEPROM on the HVR-1600 and knows it
has a "TCL MNM05-4" analog tuner assembly. But looking at the entry in
the table in tveeprom.c:

/* 100-109 */
{ TUNER_PHILIPS_FMD1216ME_MK3, "Philips FMD1216ME"},
{ TUNER_TEA5767, "Philips TEA5768HL FM Radio"},
{ TUNER_ABSENT, "Panasonic ENV57H12D5"},
{ TUNER_PHILIPS_FM1236_MK3, "TCL MFNM05-4"},
---> { TUNER_ABSENT, "TCL MNM05-4"},
{ TUNER_PHILIPS_FM1216ME_MK3, "TCL MPE05-2"},
{ TUNER_ABSENT, "TCL MQNM05-4"},

The tveeprom parsing doesn't set any tuner type for that specific analog
tuner assembly (type 4 is TUNER_ABSENT).

I can't find the TCL MNM05-4 on the TCL King High Frequency website, but
I suspect the TCL MNM05-4 is similar to the TCL MFNM05-4 except without
FM radio:

http://www.tclrf.com/English/html/enewsproopen.asp?proname=108&url=product

> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is CX23418 (idx 38)
> tveeprom 1-0050: decoder processor is CX23418 (idx 31)
> tveeprom 1-0050: has no radio
> cx18-0: Autodetected Hauppauge HVR-1600
> cx18-0: tveeprom cannot autodetect tuner!<6>cx18-0: Simultaneous
> Digital and Analog TV capture supported

> The previous two lines seem to contradict each other. What's
> happening here?

They don't. By "tuner" the error message meant the analog tuner
assembly on the HVR-1600. The cx18 driver gripes when tveeprom doesn't
tells us what the analog tuner type is.

> tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
> tda9887 2-0043: creating new instance
> tda9887 2-0043: tda988[5/6/7] found
> tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)

Yet, the cx18 driver searching for an analog tuner on the I2C bus yields
an RF oscillator/mixer chip and IF demodulator chip that are inside the
analog tuner assembly. The I2C addresses and the presence of a TDA988x
chip makes me further suspect it is like a TCL MFNM05-4, just without FM
radio.

I'm just not sure the analog tuner driver will let you tune to a channel
when you have a tuner type of TUNER_ABSENT set.

Can you unload the cx18 module and reload it with a

# modprobe cx18 tuner=43 radio=0

That'll tell the cx18 driver that, for the first card, the analog tuner
is a TCL MFNM05-4 but that there is no FM radio.

That's just a guess. You can guess other tuner types and try to see
what's best. The list of numbers is in linux/include/media/tuner.h. I
suggest you try only NTSC tuners. ;)

The tuner type parameters are in
linux/drivers/media/common/tuners/tuner-types.c
in case you can find actual data on the TCL MNM05-4 and want to find a
similar existing entry.

When/if you find a good match for the analog tuner, then let me know,
and I'll get tveeprom.c updated.

Regards,
Andy

> cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
> cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
> DVB: registering new adapter (cx18)
> MXL5005S: Attached at address 0x63
> DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB
> Frontend)...
> cx18-0: DVB Frontend registered
> cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)
> cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
> cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
> cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
> cx18-0: Initialized card: Hauppauge HVR-1600
> cx18: End initialization
>
>
> thanks!

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

matt.beadon at gmail

May 1, 2009, 5:10 PM

Post #3 of 9 (2986 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

> Originally posted a long description of my problems
>> here: http://www.gossamer-threads.com/lists/mythtv/users/380947#380947
>
>Ah, I see Dale has been helping you out. He was a very patient
>tester. :)

He's definitely helped me out (as have you)!
>
>
>> What it boils down to first of all is the Hauppauge HVR-1600 model
>> 74591 supported by the cx18 driver?
>
>In a generic sense, yes all HVR-1600's from 74000-74999 are.

whew, have kept the ebay seller waiting for feedback too long already. :)
>
>
>> I'm really starting to think that this different model # is the key to
>> my problems since I have:
>> tveeprom 1-0050: Hauppauge model 74591, rev C1A4, serial#
>>
>>
>> and everything I've found online has been like this one:
>> tveeprom 5-0050: Hauppauge model 74041, rev C6B2, serial#
>> xxxxxxx
>
>It's could be a reason why analog TV may not work. Composite or SVideo
>should certainly be OK. Have you tried those?

No, haven't tried that. I don't have a convenient comp or svideo source to
use. It would involve crawling behind my tv and sorting out 100's of
cables.

>
>
>
>> Here's a more complete dump of my dmesg (note that my system has a
>> working PVR-500 card as well:
>
>I've snipped out the PVR-500 stuff...
>
>> Linux video capture interface: v2.00
>> cx18: Start initialization, version 1.1.0
>> cx18-0: Initializing card 0
>> cx18-0: Autodetected Hauppauge card
>> ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 17
>> ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNKA] -> GSI 17 (level,
>> low) -> IRQ 17
>> cx18-0: cx23418 revision 01010000 (B)
>> tveeprom 1-0050: Hauppauge model 74591, rev C1A4, serial#
>> tveeprom 1-0050: MAC address is 00-0D-FE-19-B8-32
>> tveeprom 1-0050: tuner model is TCL MNM05-4 (idx 104, type 4)
>
>The tveeprom module can decode the EEPROM on the HVR-1600 and knows it
>has a "TCL MNM05-4" analog tuner assembly. But looking at the entry in
>the table in tveeprom.c:
>
> /* 100-109 */
> { TUNER_PHILIPS_FMD1216ME_MK3, "Philips FMD1216ME"},
> { TUNER_TEA5767, "Philips TEA5768HL FM Radio"},
> { TUNER_ABSENT, "Panasonic ENV57H12D5"},
> { TUNER_PHILIPS_FM1236_MK3, "TCL MFNM05-4"},
>---> { TUNER_ABSENT, "TCL MNM05-4"},
> { TUNER_PHILIPS_FM1216ME_MK3, "TCL MPE05-2"},
> { TUNER_ABSENT, "TCL MQNM05-4"},
>
>The tveeprom parsing doesn't set any tuner type for that specific analog
>tuner assembly (type 4 is TUNER_ABSENT).
>
>I can't find the TCL MNM05-4 on the TCL King High Frequency website, but
>I suspect the TCL MNM05-4 is similar to the TCL MFNM05-4 except without
>FM radio:
>
>http://www.tclrf.com/English/html/enewsproopen.asp?proname=108&url=product
>
>
>> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
>> tveeprom 1-0050: audio processor is CX23418 (idx 38)
>> tveeprom 1-0050: decoder processor is CX23418 (idx 31)
>> tveeprom 1-0050: has no radio
>> cx18-0: Autodetected Hauppauge HVR-1600
>> cx18-0: tveeprom cannot autodetect tuner!<6>cx18-0: Simultaneous
>> Digital and Analog TV capture supported
>
>> The previous two lines seem to contradict each other. What's
>> happening here?
>
>They don't. By "tuner" the error message meant the analog tuner
>assembly on the HVR-1600. The cx18 driver gripes when tveeprom doesn't
>tells us what the analog tuner type is.
>
>
>
>> tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
>> tda9887 2-0043: creating new instance
>> tda9887 2-0043: tda988[5/6/7] found
>> tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
>
>Yet, the cx18 driver searching for an analog tuner on the I2C bus yields
>an RF oscillator/mixer chip and IF demodulator chip that are inside the
>analog tuner assembly. The I2C addresses and the presence of a TDA988x
>chip makes me further suspect it is like a TCL MFNM05-4, just without FM
>radio.
>
>I'm just not sure the analog tuner driver will let you tune to a channel
>when you have a tuner type of TUNER_ABSENT set.
>
>Can you unload the cx18 module and reload it with a
>
># modprobe cx18 tuner=43 radio=0
>
>That'll tell the cx18 driver that, for the first card, the analog tuner
>is a TCL MFNM05-4 but that there is no FM radio.
>
>That's just a guess. You can guess other tuner types and try to see
>what's best. The list of numbers is in linux/include/media/tuner.h. I
>suggest you try only NTSC tuners. ;)
>
>The tuner type parameters are in
>linux/drivers/media/common/tuners/tuner-types.c
>in case you can find actual data on the TCL MNM05-4 and want to find a
>similar existing entry.
>
>When/if you find a good match for the analog tuner, then let me know,
>and I'll get tveeprom.c updated.
>
>Regards,
>Andy
>

Aha! With the modprobe commands above I suddenly have evidence that it is
loading the firmware (which I'd idly wondered about earlier) syslog snip
below.

My wife is watching tv right now so I can't check it but the following used
to give "Signal strength : 0%" So I'm very optimistic that it is now
working.
# v4l2-ctl --get-tuner -d /dev/HVR-1600
Tuner:
Capabilities : 62.5 kHz multi-standard stereo lang1 lang2
Frequency range : 44.0 MHz - 958.0 MHz
Signal strength : 100%
Current audio mode : lang1
Available subchannels: stereo lang2

Thanks Andy!

Not to seem ungrateful for the work around but how soon do you think you'll
be able to get this into the code tree? I'm sure to forget to modprobe the
card after a reboot. :)
Actually WTF... I changed line 214 of tveeprom.c to:
{ TUNER_PHILIPS_FM1236_MK3_NO_RADIO, "TCL MFNM05-4"},
I'll rebuild and try it when I get home. [update] hmm not as simple as
that. :(

Well here's my syslog entry after: # modprobe -r cx18; modprobe cx18
tuner=43 radio=0

cx18-0: unregister DVB
tda9887 2-0043: destroying instance
ACPI: PCI interrupt for device 0000:01:06.0 disabled
cx18-0: Removed Hauppauge HVR-1600
cx18: Start initialization, version 1.1.0
cx18-0: Initializing card 0
cx18-0: Autodetected Hauppauge card
ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [LNKA] -> GSI 17 (level, low) ->
IRQ 17
cx18-0: cx23418 revision 01010000 (B)
tveeprom 1-0050: Hauppauge model 74591, rev C1A4, serial# 1685554
tveeprom 1-0050: MAC address is 00-0D-FE-19-B8-32
tveeprom 1-0050: tuner model is TCL MNM05-4 (idx 104, type 4)
tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 1-0050: audio processor is CX23418 (idx 38)
tveeprom 1-0050: decoder processor is CX23418 (idx 31)
tveeprom 1-0050: has no radio
cx18-0: Autodetected Hauppauge HVR-1600
cx18-0: tveeprom cannot autodetect tuner!<6>cx18-0: Simultaneous Digital and
Analog TV capture supported
tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
tda9887 2-0043: creating new instance
tda9887 2-0043: tda988[5/6/7] found
tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
cs5345 1-004c: chip found @ 0x98 (cx18 i2c driver #0-0)
tuner-simple 2-0061: creating new instance
tuner-simple 2-0061: type set to 43 (Philips NTSC MK3 (FM1236MK3 or
FM1236/F))
cx18-0: Registered device video0 for encoder MPEG (64 x 32 kB)
DVB: registering new adapter (cx18)
MXL5005S: Attached at address 0x63
DVB: registering adapter 0 frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)...
cx18-0: DVB Frontend registered
cx18-0: Registered DVB adapter0 for TS (32 x 32 kB)
cx18-0: Registered device video32 for encoder YUV (16 x 128 kB)
cx18-0: Registered device vbi0 for encoder VBI (20 x 51984 bytes)
cx18-0: Registered device video24 for encoder PCM audio (256 x 4 kB)
cx18-0: Initialized card: Hauppauge HVR-1600
cx18: End initialization
firmware: requesting v4l-cx23418-cpu.fw
cx18-0: loaded v4l-cx23418-cpu.fw firmware (158332 bytes)
firmware: requesting v4l-cx23418-apu.fw
cx18-0: loaded v4l-cx23418-apu.fw firmware V00120000 (141200 bytes)
cx18-0: FW version: 0.0.74.0 (Release 2007/03/12)
firmware: requesting v4l-cx23418-cpu.fw
firmware: requesting v4l-cx23418-apu.fw
firmware: requesting v4l-cx23418-dig.fw
cx18-0 843: loaded v4l-cx23418-dig.fw firmware (16382 bytes)

awalls at radix

May 1, 2009, 6:10 PM

Post #4 of 9 (2995 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

On Fri, 2009-05-01 at 17:10 -0700, Matt Beadon wrote:

> >Can you unload the cx18 module and reload it with a
> >
> ># modprobe cx18 tuner=43 radio=0
> >
> >That'll tell the cx18 driver that, for the first card, the analog
> tuner
> >is a TCL MFNM05-4 but that there is no FM radio.
> >
> >That's just a guess. You can guess other tuner types and try to see
> >what's best. The list of numbers is in linux/include/media/tuner.h.
> I
> >suggest you try only NTSC tuners. ;)
> >
> >The tuner type parameters are in
> >linux/drivers/media/common/tuners/tuner-types.c
> >in case you can find actual data on the TCL MNM05-4 and want to find
> a
> >similar existing entry.
> >
> >When/if you find a good match for the analog tuner, then let me know,
> >and I'll get tveeprom.c updated.
> >
> >Regards,
> >Andy
> >
>
>
> Aha! With the modprobe commands above I suddenly have evidence that
> it is loading the firmware (which I'd idly wondered about earlier)
> syslog snip below.
>
>
> My wife is watching tv right now so I can't check it but the following
> used to give "Signal strength : 0%" So I'm very optimistic that it is
> now working.
> # v4l2-ctl --get-tuner -d /dev/HVR-1600
> Tuner:
> Capabilities : 62.5 kHz multi-standard stereo lang1
> lang2
> Frequency range : 44.0 MHz - 958.0 MHz
> Signal strength : 100%
> Current audio mode : lang1
> Available subchannels: stereo lang2
>
>
> Thanks Andy!

You're welcome.

> Not to seem ungrateful for the work around but how soon do you think
> you'll be able to get this into the code tree?

After you've tested it and are happy the settings are good enough for
general user use, I can add a patch and issue a PULL request. I usually
issue a PULL request on Sunday nights. The v4l-dvb maintainer usually
gets to them within a week, unless he's really busy.

> I'm sure to forget to modprobe the card after a reboot. :)
> Actually WTF... I changed line 214 of tveeprom.c to:
> { TUNER_PHILIPS_FM1236_MK3_NO_RADIO, "TCL MFNM05-4"},
> I'll rebuild and try it when I get home. [update] hmm not as simple
> as that. :(
>

Drop the '_NO_RADIO' - no define exists with that name. Leave the "TCL
MNM05-4" string alone - don't add in the "F".

TUNER_PHILIPS_FM1236_MK3 is tuner type 43.

The cx18 driver is smart enough to know that tveeprom says there is no
FM radio. No need to worry about radio being turned on.

Regards,
Andy

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

matt.beadon at gmail

May 3, 2009, 5:59 PM

Post #5 of 9 (2962 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

>After you've tested it and are happy the settings are good enough for
>general user use, I can add a patch and issue a PULL request. I usually
>issue a PULL request on Sunday nights. The v4l-dvb maintainer usually
>gets to them within a week, unless he's really busy.
I'm happy that analog tuning is working now. Do you have some suggestions
on what testing I should do beyond watching it? :)

>
>
>> I'm sure to forget to modprobe the card after a reboot. :)
>> Actually WTF... I changed line 214 of tveeprom.c to:
>> { TUNER_PHILIPS_FM1236_MK3_NO_RADIO, "TCL MFNM05-4"},
>> I'll rebuild and try it when I get home. [update] hmm not as simple
>> as that. :(
>>
>
>Drop the '_NO_RADIO' - no define exists with that name. Leave the "TCL
>MNM05-4" string alone - don't add in the "F".
>
>TUNER_PHILIPS_FM1236_MK3 is tuner type 43.
>
>The cx18 driver is smart enough to know that tveeprom says there is no
>FM radio. No need to worry about radio being turned on.

Cool, that looks like it's working. I originally thought the
"TUNER_PHILIPS_*" was a text string and didn't realize it was a define.
That's why I thought I'd throw in the "NO_RADIO" just so it wouldn't
conflict/match another entry. Anyway seems good now.

As a follow up I'm having some issues with the ATSC channels on this card
(beyond the listings problem I still have posted on the mythtv-users list).
Occasionally the signal breaks up and/or stutters along with audio glitches
and pops.
I have a Core2 E6600 and when I'm playing live ATSC the cpu usage is around
44% but it's actually about 2% higher when I'm playing live NTSC so I don't
think the system is too slow. I thought it might be signal strength so I've
cut out as many splitters as possible and this card is getting the 2nd
cleanest cable I have (best goes to cable modem).

When I tune an ATSC channel with mythtv it says "Signal 0% | SNR 2.5dB |
BEXXX | LAM(lock)". The 0% part is what has me worried that I still don't
have good enough SNR but I haven't poked around enough to figure what other
people are getting for signal % and SNR?

There seem to be a ton of cx18 threads. Is there a guide for optimizing
settings for cx18? Or some general tips that might help?

thanks

awalls at radix

May 5, 2009, 6:14 PM

Post #6 of 9 (2926 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

On Sun, 2009-05-03 at 17:59 -0700, Matt Beadon wrote:
> >After you've tested it and are happy the settings are good enough
> for
> >general user use, I can add a patch and issue a PULL request. I
> usually
> >issue a PULL request on Sunday nights. The v4l-dvb maintainer
> usually
> >gets to them within a week, unless he's really busy.
>
>
> I'm happy that analog tuning is working now. Do you have some
> suggestions on what testing I should do beyond watching it? :)

Test all the channels. Especially ones near the VHF-Low/VHF-High
boundary and the VHF-High/UHF boundary. The channel/frequency tables in
the ivtv-tune source can tell you the mapping of cable channels to
frequency.

The file

linux/drivers/media/common/tuners/tuner-types.c

shows that for the FM1236 MK3 tuner, the VHF-Low/VHF-High boundary is
around 160 MHz and the VHF-High/UHF boundary is 442 MHz.

There is only one other analog/only NTSC tuner in the tuner-types.c file
with a TDA9887: tuner type 46, the TUNER_PANASONIC_VP27. It likely
won't work. Please test tuner type 46 (I suspect it won't work or work
as well).

> As a follow up I'm having some issues with the ATSC channels on this
> card (beyond the listings problem I still have posted on the
> mythtv-users list). Occasionally the signal breaks up and/or stutters
> along with audio glitches and pops.
> I have a Core2 E6600 and when I'm playing live ATSC the cpu usage is
> around 44% but it's actually about 2% higher when I'm playing live
> NTSC so I don't think the system is too slow.

That seems high for NTSC - you (MythTV) must be doing some software
scaling somewhere. mplayer doesn't do software scaling unless you tell
it to.

You can load the cx18 module with the debug=15 module parameter and look
for "Possibly falling behind" messages to see how respinsive you system
is to CX23418 interrupts. If you get a lot of those messages in the
logs that come with sequence numbers that are close together, you've got
some system level inefficiencies.

> I thought it might be signal strength so I've cut out as many
> splitters as possible and this card is getting the 2nd cleanest cable
> I have (best goes to cable modem).

You whole cable plant in your home affects the S/N ratio (e.g. voltage
wave reflections due to impedenace mismatches come back up from the far
end of the cable and can look like noise).

Please review:

http://www.ivtvdriver.org/index.php/Howto:Improve_signal_quality

>
> When I tune an ATSC channel with mythtv it says "Signal 0% | SNR 2.5dB
> | BEXXX | LAM(lock)". The 0% part is what has me worried that I still
> don't have good enough SNR but I haven't poked around enough to figure
> what other people are getting for signal % and SNR?

Meh. The signal 0% is a known deficiency. I can't remember if it's the
mxl5005s driver or the s5h1409 driver that's reporting junk. The SNR of
about 2.3 dB is what I get for OTA ATSC. LAM(lock) is good. BE (block
errors) should not be increasing, but a fixed non-zero number is OK.

Regards,
Andy

> There seem to be a ton of cx18 threads. Is there a guide for
> optimizing settings for cx18? Or some general tips that might help?
>

>

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

matt.beadon at gmail

May 9, 2009, 12:14 AM

Post #7 of 9 (2835 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

>
> Date: Tue, 05 May 2009 21:14:37 -0400
> From: Andy Walls <awalls [at] radix>
> Subject: Re: [ivtv-users] Is HVR-1600 model 74591 supported by cx18
> driver?
> To: User discussion about IVTV <ivtv-users [at] ivtvdriver>
> Message-ID: <1241572477.3152.73.camel [at] palomino>
> Content-Type: text/plain
>
> Test all the channels. Especially ones near the VHF-Low/VHF-High
> boundary and the VHF-High/UHF boundary. The channel/frequency tables in
> the ivtv-tune source can tell you the mapping of cable channels to
> frequency.
>
> The file
>
> linux/drivers/media/common/tuners/tuner-types.c
>
> shows that for the FM1236 MK3 tuner, the VHF-Low/VHF-High boundary is
> around 160 MHz and the VHF-High/UHF boundary is 442 MHz.
>
> There is only one other analog/only NTSC tuner in the tuner-types.c file
> with a TDA9887: tuner type 46, the TUNER_PANASONIC_VP27. It likely
> won't work. Please test tuner type 46 (I suspect it won't work or work
> as well).
>

Hmm. I finally had a chance to try this. From what I can tell the
boundaries are around channels 21-24 and 59-63. What I see is that
channels 21 & 22 are fine but 23 & 24 are just snow (25 works ok). However
this is expected in my lineup and matches what I see on my PVR-500 tuners.
So I don't think that really says anything bad about the HVR-1600 analog.
Similarly channel 59 is bad on both PVR-500 and HVR-1600 analog. While
channels 60-63 are ok on both.

> As a follow up I'm having some issues with the ATSC channels on this
> > card (beyond the listings problem I still have posted on the
> > mythtv-users list). Occasionally the signal breaks up and/or stutters
> > along with audio glitches and pops.
> > I have a Core2 E6600 and when I'm playing live ATSC the cpu usage is
> > around 44% but it's actually about 2% higher when I'm playing live
> > NTSC so I don't think the system is too slow.
>
> That seems high for NTSC - you (MythTV) must be doing some software
> scaling somewhere. mplayer doesn't do software scaling unless you tell
> it to.
>
> You can load the cx18 module with the debug=15 module parameter and look
> for "Possibly falling behind" messages to see how respinsive you system
> is to CX23418 interrupts. If you get a lot of those messages in the
> logs that come with sequence numbers that are close together, you've got
> some system level inefficiencies.
>

I can't repro the 40% utilization now. It's more like 4% so not sure what I
saw before.

>
>
> > I thought it might be signal strength so I've cut out as many
> > splitters as possible and this card is getting the 2nd cleanest cable
> > I have (best goes to cable modem).
>
> You whole cable plant in your home affects the S/N ratio (e.g. voltage
> wave reflections due to impedenace mismatches come back up from the far
> end of the cable and can look like noise).
>
> Please review:
>
> http://www.ivtvdriver.org/index.php/Howto:Improve_signal_quality
>

Yep went though that wiki already.

>
> >
> > When I tune an ATSC channel with mythtv it says "Signal 0% | SNR 2.5dB
> > | BEXXX | LAM(lock)". The 0% part is what has me worried that I still
> > don't have good enough SNR but I haven't poked around enough to figure
> > what other people are getting for signal % and SNR?
>
> Meh. The signal 0% is a known deficiency. I can't remember if it's the
> mxl5005s driver or the s5h1409 driver that's reporting junk. The SNR of
> about 2.3 dB is what I get for OTA ATSC. LAM(lock) is good. BE (block
> errors) should not be increasing, but a fixed non-zero number is OK.
>

good to know, thanks.

So based on my testing I think this is working well for this model of
HVR-1600. Anything else you want me to check or is this good to go?

thanks
Matt

awalls at radix

May 9, 2009, 5:39 AM

Post #8 of 9 (2843 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

On Sat, 2009-05-09 at 00:14 -0700, Matt Beadon wrote:

> So based on my testing I think this is working well for this model of
> HVR-1600. Anything else you want me to check or is this good to go?
>
> thanks
> Matt

Nope, thanks.

I'll ask for the change mapping of the TCL MNM05-4 in tveeprom.c to the
TUNER_PHILLIPS_FM1236_MK3 definition today or tomorrow.

Regards,
Andy

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

matt.beadon at gmail

May 9, 2009, 8:41 AM

Post #9 of 9 (2832 views)
Permalink

Re: Is HVR-1600 model 74591 supported by cx18 driver? [In reply to]

Thanks Andy!

On May 9, 2009 5:43 AM, "Andy Walls" <awalls [at] radix> wrote:

On Sat, 2009-05-09 at 00:14 -0700, Matt Beadon wrote: > So based on my
testing I think this is wor...
Nope, thanks.

I'll ask for the change mapping of the TCL MNM05-4 in tveeprom.c to the
TUNER_PHILLIPS_FM1236_MK3 definition today or tomorrow.

Regards,
Andy

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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads