Mailing List Archive: PVR 1600 / "tuner model is unknown"

PVR 1600 / "tuner model is unknown"

Jun 6, 2010, 7:38 PM

Post #1 of 7 (4579 views)

Hello:

I recently purchased a Hauppauge PVR-1600, which I intend to use in a MythTV
setup as an analog capture card, connected to "cable out" on my cable STB.
Despite my best efforts, all I am able to see from the card's analog input
is static, both in MythTV and reading /dev/video0 with mplayer. the clear
QAM half of the card works fine -- it grabs all the clear digital channels
my provider has to offer.

I am running Mythbuntu 10.04; here's what uname -a has to say: "Linux myth
2.6.32-22-generic #35-Ubuntu SMP Tue Jun 1 14:17:36 UTC 2010 i686
GNU/Linux". I'm using the latest version of the V4L drivers, which I
downloaded yesterday from http://linuxtv.org/hg/v4l-dvb/, built, and
installed. And the cable is plugged into the correct input on the PVR 1600
(the top one).

Absolutely nothing happens when I change channels regardless of whether it's
on the STB, or using ivtv-tune, and regardless of frequency table I use in
ivtv-tune -- the static pattern shows no sign that anything has just
happened, almost as if the tuner isn't doing any tuning.

I have confirmed that the STB's cable out is working, using a PVR 150.

I noticed the following in the output of dmesg -- note the triple-asterisk'd
lines:

[ 27.136529] tveeprom 1-0050: Hauppauge model 74041, rev C6G8, serial#
7155635
[ 27.136534] tveeprom 1-0050: MAC address is 00:0d:fe:6d:2f:b3
*** [ 27.136537] tveeprom 1-0050: tuner model is unknown (idx 168, type 4)
[ 27.136540] tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
[ 27.136543] tveeprom 1-0050: audio processor is CX23418 (idx 38)
[ 27.136546] tveeprom 1-0050: decoder processor is CX23418 (idx 31)
[ 27.136549] tveeprom 1-0050: has no radio, has IR receiver, has IR
transmitter
[ 27.136552] cx18-0: Autodetected Hauppauge HVR-1600
*** [ 27.136554] cx18-0: tveeprom cannot autodetect tuner!
[ 27.136702] cx18-0: Simultaneous Digital and Analog TV capture supported
[ 27.250445] IRQ 20/cx18-0: IRQF_DISABLED is not guaranteed on shared IRQs
[ 27.261509] tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
[ 27.261603] tda9887 2-0043: creating new instance
[ 27.261606] tda9887 2-0043: tda988[5/6/7] found
[ 27.264659] tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)

Could this mean that the tuner isn't working at all? If so, is there a
workaround?

Here is abbreviated output of v4l2-ctl --all -d /dev/video0; the full thing
can be seen here: http://pastebin.com/4jMqXXzd

Driver Info:
Driver name : cx18
Card type : Hauppauge HVR-1600
Bus info : PCI:0000:03:06.0
Driver version: 66560
Capabilities : 0x01030051
Video Capture
VBI Capture
Sliced VBI Capture
Tuner
Audio
Read/Write
Video input : 0 (Tuner 1)
Audio input : 0 (Tuner 1)
Frequency: 1076 (67.250000 MHz)
Video Standard = 0x00001000
NTSC-M
Tuner:
Name : cx18 TV Tuner
Capabilities : 62.5 kHz multi-standard stereo lang1 lang2
Frequency range : 44.0 MHz - 958.0 MHz
Signal strength/AFC : 0%/-187500
Current audio mode : lang1
Available subchannels: mono

Thank you!

Larry

Re: PVR 1600 / "tuner model is unknown" [ In reply to ]

awalls at md

Jun 6, 2010, 9:08 PM

Post #2 of 7 (4508 views)

Permalink

On Sun, 2010-06-06 at 22:38 -0400, Larry Glenn wrote:
> Hello:
>
> I recently purchased a Hauppauge PVR-1600, which I intend to use in a
> MythTV setup as an analog capture card, connected to "cable out" on my
> cable STB. Despite my best efforts, all I am able to see from the
> card's analog input is static, both in MythTV and reading /dev/video0
> with mplayer. the clear QAM half of the card works fine -- it grabs
> all the clear digital channels my provider has to offer.

> Absolutely nothing happens when I change channels regardless of
> whether it's on the STB, or using ivtv-tune, and regardless of
> frequency table I use in ivtv-tune -- the static pattern shows no sign
> that anything has just happened, almost as if the tuner isn't doing
> any tuning.

That appears to be the case. See below...

> I have confirmed that the STB's cable out is working, using a PVR
> 150.
>
> I noticed the following in the output of dmesg -- note the
> triple-asterisk'd lines:
>
> [ 27.136529] tveeprom 1-0050: Hauppauge model 74041, rev C6G8,
> serial# 7155635
> [ 27.136534] tveeprom 1-0050: MAC address is 00:0d:fe:6d:2f:b3
> *** [ 27.136537] tveeprom 1-0050: tuner model is unknown (idx 168,
> type 4)

Tuner index 168 is not in tveeprom.c :

http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/drivers/media/video/tveeprom.c#l242

so the cx18 driver doesn't know how to set it up or use it (tuner type 4
is TUNER_ABSENT). I will try to contact Hauppauge and see if I can find
out the details.

In the meantime, if you carefully peel back the Hauppauge sticker from
the analog tuner can, there may be a readable sticker underneath that
has the tuner manufacturer/model/type.

Or you can just guess. You can use the tuner= option when loading the
cx18 module to force it to use a tuner type using the numbers in this
list:

http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/include/media/tuner.h#l29

I would try the TCL_2002N (type 50) first, since the tuner on my non-FM
radio HVR-1600 maps to that:

# modprobe -r cx18
# modprobe cx18 tuner=50 debug=3

> [ 27.136540] tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> [ 27.136543] tveeprom 1-0050: audio processor is CX23418 (idx 38)
> [ 27.136546] tveeprom 1-0050: decoder processor is CX23418 (idx 31)
> [ 27.136549] tveeprom 1-0050: has no radio, has IR receiver, has IR
> transmitter
> [ 27.136552] cx18-0: Autodetected Hauppauge HVR-1600
> *** [ 27.136554] cx18-0: tveeprom cannot autodetect tuner!
> [ 27.136702] cx18-0: Simultaneous Digital and Analog TV capture
> supported
> [ 27.250445] IRQ 20/cx18-0: IRQF_DISABLED is not guaranteed on
> shared IRQs
> [ 27.261509] tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
> [ 27.261603] tda9887 2-0043: creating new instance
> [ 27.261606] tda9887 2-0043: tda988[5/6/7] found
> [ 27.264659] tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)

Hmm. The driver is also detecting a tda9887 chip which is usually found
on tuners with FM radio. Maybe you should also try the
TUNER_PHILIPS_FM1236_MK3 type 43 tuner as well:

# modprobe -r cx18
# modprobe cx18 tuner=50 debug=3

> Could this mean that the tuner isn't working at all?

That's right.

> If so, is there a workaround?

Forcing a tuner type with the tuner= module option.

> Here is abbreviated output of v4l2-ctl --all -d /dev/video0; the full
> thing can be seen here: http://pastebin.com/4jMqXXzd

v4l2-ctl -d /dev/video0 --log-status

is actually more useful as is the dmesg output.

Regards,
Andy

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR 1600 / "tuner model is unknown" [ In reply to ]

yrral.glenn at gmail

Jun 7, 2010, 9:04 PM

Post #3 of 7 (4564 views)

Permalink

Hi Andy:

Thank you! That was what I was looking for. I have the card working now by
forcing the tuner type to 71 (TUNER_XC2028). I have not had the opportunity
yet to peel back the sticker and see what's stamped on the tuner. If I see
anything different when I do get to it, I'll let you know.

If anyone is interested, I sped up the process of trying each tuner value
with a small shell script that tested each tuner ID in turn. While I ran it,
I watched the output to see which ones I got signal greater than 0% with --
which I did with three tuners: 54 (TUNER_PHILIPS_TDA8290), 71, and 83
(TUNER_NXP_TDA18271). Then, for each of those three, I reloaded the cx18
module, forcing the tuner to the appropriate value, and tried using the
mplayer / ivtv-tune combination described below to see if there was anything
other than static on the screen. When I tried the XC2028, bingo, there was
the weather man, just like normal people have on *their* TV's!

Here is the script. Change CHANNEL, FREQUENCY_TABLE, and VIDEO_DEVICE to
fit your setup, if necessary. Note that I needed to modprobe -r cx18_alsa
before removing the cx18 module, I am not sure if that applies to everyone
or not.

#!/bin/bash

VIDEO_DEVICE=/dev/video0
CHANNEL=3
FREQUENCY_TABLE=us-bcast

let start=1
let end=84

for ((i=$start; i <= $end; i++))
do
echo -n "Tuner type $i: "
modprobe -r cx18_alsa
modprobe -r cx18
modprobe cx18 tuner=$i debug=3
ivtv-tune -t $FREQUENCY_TABLE -c $CHANNEL -d $VIDEO_DEVICE > /dev/null
v4l2-ctl -T -d $VIDEO_DEVICE | grep 'Signal strength'
done

Unfortunately, at the end of the day, I think I discovered that the problem
I was trying to solve by replacing my PVR 150, which is that I can watch
live TV via the STB's analog cable out, but recordings off that input fail
and crash the MythTV frontend about 98% of the time, was not a problem with
the card. It still happens with the 1600. But, as I can see live TV, and the
cards have different chips and drivers, I am going to assume that this most
likely isn't a driver problem. Correct?

Thanks again for your help, it is tremendously appreciated!!!

Larry

On Mon, Jun 7, 2010 at 12:08 AM, Andy Walls <awalls@md.metrocast.net> wrote:

> On Sun, 2010-06-06 at 22:38 -0400, Larry Glenn wrote:
> > Hello:
> >
> > I recently purchased a Hauppauge PVR-1600, which I intend to use in a
> > MythTV setup as an analog capture card, connected to "cable out" on my
> > cable STB. Despite my best efforts, all I am able to see from the
> > card's analog input is static, both in MythTV and reading /dev/video0
> > with mplayer. the clear QAM half of the card works fine -- it grabs
> > all the clear digital channels my provider has to offer.
>
> > Absolutely nothing happens when I change channels regardless of
> > whether it's on the STB, or using ivtv-tune, and regardless of
> > frequency table I use in ivtv-tune -- the static pattern shows no sign
> > that anything has just happened, almost as if the tuner isn't doing
> > any tuning.
>
> That appears to be the case. See below...
>
>
> > I have confirmed that the STB's cable out is working, using a PVR
> > 150.
> >
> > I noticed the following in the output of dmesg -- note the
> > triple-asterisk'd lines:
> >
> > [ 27.136529] tveeprom 1-0050: Hauppauge model 74041, rev C6G8,
> > serial# 7155635
> > [ 27.136534] tveeprom 1-0050: MAC address is 00:0d:fe:6d:2f:b3
> > *** [ 27.136537] tveeprom 1-0050: tuner model is unknown (idx 168,
> > type 4)
>
> Tuner index 168 is not in tveeprom.c :
>
>
> http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/drivers/media/video/tveeprom.c#l242
>
> so the cx18 driver doesn't know how to set it up or use it (tuner type 4
> is TUNER_ABSENT). I will try to contact Hauppauge and see if I can find
> out the details.
>
> In the meantime, if you carefully peel back the Hauppauge sticker from
> the analog tuner can, there may be a readable sticker underneath that
> has the tuner manufacturer/model/type.
>
> Or you can just guess. You can use the tuner= option when loading the
> cx18 module to force it to use a tuner type using the numbers in this
> list:
>
>
> http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/include/media/tuner.h#l29
>
> I would try the TCL_2002N (type 50) first, since the tuner on my non-FM
> radio HVR-1600 maps to that:
>
> # modprobe -r cx18
> # modprobe cx18 tuner=50 debug=3
>
>
> > [ 27.136540] tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> > [ 27.136543] tveeprom 1-0050: audio processor is CX23418 (idx 38)
> > [ 27.136546] tveeprom 1-0050: decoder processor is CX23418 (idx 31)
> > [ 27.136549] tveeprom 1-0050: has no radio, has IR receiver, has IR
> > transmitter
> > [ 27.136552] cx18-0: Autodetected Hauppauge HVR-1600
> > *** [ 27.136554] cx18-0: tveeprom cannot autodetect tuner!
> > [ 27.136702] cx18-0: Simultaneous Digital and Analog TV capture
> > supported
> > [ 27.250445] IRQ 20/cx18-0: IRQF_DISABLED is not guaranteed on
> > shared IRQs
> > [ 27.261509] tuner 2-0043: chip found @ 0x86 (cx18 i2c driver #0-1)
> > [ 27.261603] tda9887 2-0043: creating new instance
> > [ 27.261606] tda9887 2-0043: tda988[5/6/7] found
> > [ 27.264659] tuner 2-0061: chip found @ 0xc2 (cx18 i2c driver #0-1)
>
> Hmm. The driver is also detecting a tda9887 chip which is usually found
> on tuners with FM radio. Maybe you should also try the
> TUNER_PHILIPS_FM1236_MK3 type 43 tuner as well:
>
> # modprobe -r cx18
> # modprobe cx18 tuner=50 debug=3
>
> > Could this mean that the tuner isn't working at all?
>
> That's right.
>
> > If so, is there a workaround?
>
> Forcing a tuner type with the tuner= module option.
>
> > Here is abbreviated output of v4l2-ctl --all -d /dev/video0; the full
> > thing can be seen here: http://pastebin.com/4jMqXXzd
>
> v4l2-ctl -d /dev/video0 --log-status
>
> is actually more useful as is the dmesg output.
>
>
> Regards,
> Andy
>
>
>

Re: PVR 1600 / "tuner model is unknown" [ In reply to ]

awalls at md

Jun 10, 2010, 7:24 PM

Post #4 of 7 (4472 views)

Permalink

On Tue, 2010-06-08 at 00:04 -0400, Larry Glenn wrote:
> Hi Andy:
>
>
> Thank you! That was what I was looking for. I have the card working
> now by forcing the tuner type to 71 (TUNER_XC2028).

That can't possibly be the right setting. The XC2028 and XC3028 are
silicon tuners (very small chip) that require firmware.

http://www.xceive.com/technology_XC3028.htm

Unless you have an actual XC2028 or XC3028 in a small analog tuner can
on the card and have the xc2028.fw image installed under /lib/firmware,
that's not the tuner type that made things work.

> I have not had the opportunity yet to peel back the sticker and see
> what's stamped on the tuner. If I see anything different when I do get
> to it, I'll let you know.

I was informed that Hauppauge tuner index 168 corresponded to a TCL
M30WTP-4N-E along with a comment that indicates it might be a clone of a
Philips MK5 series tuner. So I'm going to write the rest of the email
assuming that is true (without positive confirmation from you that you
have a very small analog tuner can on your card to somewhat confirm an
XCeive silicon tuner.)

tuner.tcl.com doesn't list that exact M30WTP-4N-E tuner, so getting a
good definition will take some guessing. Looking at other TCL part
numbers, I can make these guesses:

M - Multimedia class tuner
30 - TCL model/series
W - (I have no idea)
T - Guess: a Texas Instruments Mixer/Oscillator chip in the first stage
("I" would mean an Infineon mixer/osc chip in the first stage)
P - Guess: a Philips IF demodulator chip in the second stage
("S" would mean a Sanyo IF demodulator chip in the second stage)
4N - Guess: Full size with F-connector(s) for RF inputs
E - (I have no idea)

Your previous dmesg output indicates that a Phillips IF demodulator chip
(TDA9885/6/7, likely a TDA9885) was found. That is likely the
demodulator inside the analog tuner can on your card.

I'd guess at a Philips FM1236 MK3

http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/drivers/media/common/tuners/tuner-types.c#l672
http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/include/media/tuner.h#l82

or an Philips FQ1236 MK4
http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/include/media/tuner.h#l101
http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/drivers/media/common/tuners/tuner-types.c#l1659

since you don't have FM radio.

IIRC the Philips MK5, MK4, and MK3 series really only differ in
materials (lead free, etc.) and noise performance. Functionally they
should be very close. Also, the LG-TAPE series tuners are knock-offs of
the Philips tuners as well.

If some of those work, I have a data sheet for the FQ1236 MK5 (which has
a TDA9885 and no FM radio) and can build a proper entry for it.
Hopefully it will be close enough to the TCL M30WTP-4N-E

When testing, I wouldn't rely on signal output reading from the tuners.
Use your eyes and ears. Signal indications are read in different ways
for different tuners (so you may be doing the wrong thing for your
actual tuner hardware), many tuners don't even have a way to read signal
strength, and if the read fails, you may just see the garbage value that
was in uninitialized memory as a the signal strength.

> Unfortunately, at the end of the day, I think I discovered that the
> problem I was trying to solve by replacing my PVR 150, which is that I
> can watch live TV via the STB's analog cable out, but recordings off
> that input fail and crash the MythTV frontend about 98% of the time,
> was not a problem with the card. It still happens with the 1600. But,
> as I can see live TV, and the cards have different chips and drivers,
> I am going to assume that this most likely isn't a driver problem.
> Correct?

Sounds like an X-windows and graphics card driver problem. I had a
similar problem with FEdora 10 and my ATI graphics card. I had to
disable the GL stuff and DRI in my xorg.conf and prvent the kernel drm
module from loading to keep the X server from crashing when MythTV was
trying to playback TV.

>
>
> Thanks again for your help, it is tremendously appreciated!!!

You're welcome. PLease keep pexperimenting, so we can nail this one
down as best we can.

Regards,
Andy

>
> Larry
>
> On Mon, Jun 7, 2010 at 12:08 AM, Andy Walls <awalls@md.metrocast.net>
> wrote:
> On Sun, 2010-06-06 at 22:38 -0400, Larry Glenn wrote:
> > Hello:
> >
> > I recently purchased a Hauppauge PVR-1600, which I intend to
> use in a
> > MythTV setup as an analog capture card, connected to "cable
> out" on my
> > cable STB. Despite my best efforts, all I am able to see
> from the
> > card's analog input is static, both in MythTV and
> reading /dev/video0
> > with mplayer. the clear QAM half of the card works fine --
> it grabs
> > all the clear digital channels my provider has to offer.
>
>
> > Absolutely nothing happens when I change channels regardless
> of
> > whether it's on the STB, or using ivtv-tune, and regardless
> of
> > frequency table I use in ivtv-tune -- the static pattern
> shows no sign
> > that anything has just happened, almost as if the tuner
> isn't doing
> > any tuning.
>
>
> That appears to be the case. See below...
>
>
> > I have confirmed that the STB's cable out is working, using
> a PVR
> > 150.
> >
> > I noticed the following in the output of dmesg -- note the
> > triple-asterisk'd lines:
> >
> > [ 27.136529] tveeprom 1-0050: Hauppauge model 74041, rev
> C6G8,
> > serial# 7155635
> > [ 27.136534] tveeprom 1-0050: MAC address is
> 00:0d:fe:6d:2f:b3
> > *** [ 27.136537] tveeprom 1-0050: tuner model is unknown
> (idx 168,
> > type 4)
>
>
> Tuner index 168 is not in tveeprom.c :
>
> http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/drivers/media/video/tveeprom.c#l242
>
> so the cx18 driver doesn't know how to set it up or use it
> (tuner type 4
> is TUNER_ABSENT). I will try to contact Hauppauge and see if
> I can find
> out the details.
>
> In the meantime, if you carefully peel back the Hauppauge
> sticker from
> the analog tuner can, there may be a readable sticker
> underneath that
> has the tuner manufacturer/model/type.
>
> Or you can just guess. You can use the tuner= option when
> loading the
> cx18 module to force it to use a tuner type using the numbers
> in this
> list:
>
> http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/include/media/tuner.h#l29
>
> I would try the TCL_2002N (type 50) first, since the tuner on
> my non-FM
> radio HVR-1600 maps to that:
>
> # modprobe -r cx18
> # modprobe cx18 tuner=50 debug=3
>
>
> > [ 27.136540] tveeprom 1-0050: TV standards NTSC(M) (eeprom
> 0x08)
> > [ 27.136543] tveeprom 1-0050: audio processor is CX23418
> (idx 38)
> > [ 27.136546] tveeprom 1-0050: decoder processor is CX23418
> (idx 31)
> > [ 27.136549] tveeprom 1-0050: has no radio, has IR
> receiver, has IR
> > transmitter
> > [ 27.136552] cx18-0: Autodetected Hauppauge HVR-1600
> > *** [ 27.136554] cx18-0: tveeprom cannot autodetect tuner!
> > [ 27.136702] cx18-0: Simultaneous Digital and Analog TV
> capture
> > supported
> > [ 27.250445] IRQ 20/cx18-0: IRQF_DISABLED is not
> guaranteed on
> > shared IRQs
> > [ 27.261509] tuner 2-0043: chip found @ 0x86 (cx18 i2c
> driver #0-1)
> > [ 27.261603] tda9887 2-0043: creating new instance
> > [ 27.261606] tda9887 2-0043: tda988[5/6/7] found
> > [ 27.264659] tuner 2-0061: chip found @ 0xc2 (cx18 i2c
> driver #0-1)
>
>
> Hmm. The driver is also detecting a tda9887 chip which is
> usually found
> on tuners with FM radio. Maybe you should also try the
> TUNER_PHILIPS_FM1236_MK3 type 43 tuner as well:
>
> # modprobe -r cx18
> # modprobe cx18 tuner=50 debug=3
>
> > Could this mean that the tuner isn't working at all?
>
>
> That's right.
>
> > If so, is there a workaround?
>
>
> Forcing a tuner type with the tuner= module option.
>
> > Here is abbreviated output of v4l2-ctl --all -d /dev/video0;
> the full
> > thing can be seen here: http://pastebin.com/4jMqXXzd
>
>
> v4l2-ctl -d /dev/video0 --log-status
>
> is actually more useful as is the dmesg output.
>
>
> Regards,
> Andy
>
>
>
>

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR 1600 / "tuner model is unknown" [ In reply to ]

awalls at md

Jun 12, 2010, 5:56 PM

Post #5 of 7 (4461 views)

Permalink

On Thu, 2010-06-10 at 22:24 -0400, Andy Walls wrote:
> On Tue, 2010-06-08 at 00:04 -0400, Larry Glenn wrote:
> > Hi Andy:

> I was informed that Hauppauge tuner index 168 corresponded to a TCL
> M30WTP-4N-E along with a comment that indicates it might be a clone of a
> Philips MK5 series tuner. So I'm going to write the rest of the email
> assuming that is true (without positive confirmation from you that you
> have a very small analog tuner can on your card to somewhat confirm an
> XCeive silicon tuner.)

> Your previous dmesg output indicates that a Phillips IF demodulator chip
> (TDA9885/6/7, likely a TDA9885) was found. That is likely the
> demodulator inside the analog tuner can on your card.
>
> I'd guess at a Philips FM1236 MK3
>
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/drivers/media/common/tuners/tuner-types.c#l672
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/include/media/tuner.h#l82
>
> or an Philips FQ1236 MK4
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/include/media/tuner.h#l101
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/drivers/media/common/tuners/tuner-types.c#l1659
>
> since you don't have FM radio.

> If some of those work, I have a data sheet for the FQ1236 MK5 (which has
> a TDA9885 and no FM radio) and can build a proper entry for it.
> Hopefully it will be close enough to the TCL M30WTP-4N-E

Hi Larry,

In the last two patches at this GIT repository:

http://git.linuxtv.org/awalls/v4l-dvb.git?a=shortlog;h=refs/heads/cx18tuner

and, identically, in the last two patches at this Mercurial repository
(if you don't like GIT):

http://linuxtv.org/hg/~awalls/ivtv-cx18/

I have added

- a defintion for the Philips FQ1236 MK5 tuner, and
- an entry in tveeprom mapping index 168 to that new tuner definition
with the tuner name set to "TCL M30WTP-4N-E".

Assuming you don't have an XCeive tuner chip, can you test these
patches?

Regards,
Andy

> > > I noticed the following in the output of dmesg -- note the
> > > triple-asterisk'd lines:
> > >
> > > [ 27.136529] tveeprom 1-0050: Hauppauge model 74041, rev
> > C6G8,
> > > serial# 7155635
> > > [ 27.136534] tveeprom 1-0050: MAC address is
> > 00:0d:fe:6d:2f:b3
> > > *** [ 27.136537] tveeprom 1-0050: tuner model is unknown
> > (idx 168,
> > > type 4)
> >
> >
> > Tuner index 168 is not in tveeprom.c :
> >
> > http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/drivers/media/video/tveeprom.c#l242
> >
> > so the cx18 driver doesn't know how to set it up or use it
> > (tuner type 4
> > is TUNER_ABSENT). I will try to contact Hauppauge and see if
> > I can find
> > out the details.
> >
> > In the meantime, if you carefully peel back the Hauppauge
> > sticker from
> > the analog tuner can, there may be a readable sticker
> > underneath that
> > has the tuner manufacturer/model/type.

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Re: PVR 1600 / "tuner model is unknown" [ In reply to ]

yrral.glenn at gmail

Jun 15, 2010, 7:20 AM

Post #6 of 7 (4505 views)

Permalink

Hi Andy:

Sorry, I was away for the weekend; thanks very much for following up on
this.

I took your two patches and applied them to my copy of the head revision on
the main branch (that is, http://linuxtv.org/hg/v4l-dvb/, I am assuming that
that's what you meant; I didn't build the ~awalls branch, but would be happy
to if you'd rather I did), and the tuner works fine now. I watched live TV
on the analog input for several hours last night, with no problems.

Please let me know if you want me to test anything else...

Thank you!

Larry

On Sat, Jun 12, 2010 at 8:56 PM, Andy Walls <awalls@md.metrocast.net> wrote:

> On Thu, 2010-06-10 at 22:24 -0400, Andy Walls wrote:
> > On Tue, 2010-06-08 at 00:04 -0400, Larry Glenn wrote:
> > > Hi Andy:
>
>
> > I was informed that Hauppauge tuner index 168 corresponded to a TCL
> > M30WTP-4N-E along with a comment that indicates it might be a clone of a
> > Philips MK5 series tuner. So I'm going to write the rest of the email
> > assuming that is true (without positive confirmation from you that you
> > have a very small analog tuner can on your card to somewhat confirm an
> > XCeive silicon tuner.)
>
>
> > Your previous dmesg output indicates that a Phillips IF demodulator chip
> > (TDA9885/6/7, likely a TDA9885) was found. That is likely the
> > demodulator inside the analog tuner can on your card.
> >
> > I'd guess at a Philips FM1236 MK3
> >
> >
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/drivers/media/common/tuners/tuner-types.c#l672
> >
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/include/media/tuner.h#l82
> >
> > or an Philips FQ1236 MK4
> >
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/include/media/tuner.h#l101
> >
> http://linuxtv.org/hg/v4l-dvb/file/023a0048e6a8/linux/drivers/media/common/tuners/tuner-types.c#l1659
> >
> > since you don't have FM radio.
>
>
> > If some of those work, I have a data sheet for the FQ1236 MK5 (which has
> > a TDA9885 and no FM radio) and can build a proper entry for it.
> > Hopefully it will be close enough to the TCL M30WTP-4N-E
>
> Hi Larry,
>
> In the last two patches at this GIT repository:
>
> http://git.linuxtv.org/awalls/v4l-dvb.git?a=shortlog;h=refs/heads/cx18tuner
>
> and, identically, in the last two patches at this Mercurial repository
> (if you don't like GIT):
>
> http://linuxtv.org/hg/~awalls/ivtv-cx18/
>
> I have added
>
> - a defintion for the Philips FQ1236 MK5 tuner, and
> - an entry in tveeprom mapping index 168 to that new tuner definition
> with the tuner name set to "TCL M30WTP-4N-E".
>
> Assuming you don't have an XCeive tuner chip, can you test these
> patches?
>
>
> Regards,
> Andy
>
> > > > I noticed the following in the output of dmesg -- note the
> > > > triple-asterisk'd lines:
> > > >
> > > > [ 27.136529] tveeprom 1-0050: Hauppauge model 74041, rev
> > > C6G8,
> > > > serial# 7155635
> > > > [ 27.136534] tveeprom 1-0050: MAC address is
> > > 00:0d:fe:6d:2f:b3
> > > > *** [ 27.136537] tveeprom 1-0050: tuner model is unknown
> > > (idx 168,
> > > > type 4)
> > >
> > >
> > > Tuner index 168 is not in tveeprom.c :
> > >
> > >
> http://linuxtv.org/hg/v4l-dvb/file/24ea80f2631f/linux/drivers/media/video/tveeprom.c#l242
> > >
> > > so the cx18 driver doesn't know how to set it up or use it
> > > (tuner type 4
> > > is TUNER_ABSENT). I will try to contact Hauppauge and see if
> > > I can find
> > > out the details.
> > >
> > > In the meantime, if you carefully peel back the Hauppauge
> > > sticker from
> > > the analog tuner can, there may be a readable sticker
> > > underneath that
> > > has the tuner manufacturer/model/type.
>
>
>

Re: PVR 1600 / "tuner model is unknown" [ In reply to ]

awalls at md

Jun 16, 2010, 3:50 AM

Post #7 of 7 (4400 views)

Permalink

On Tue, 2010-06-15 at 10:20 -0400, Larry Glenn wrote:
> Hi Andy:
>
>
> Sorry, I was away for the weekend; thanks very much for following up
> on this.
>
>
> I took your two patches and applied them to my copy of the head
> revision on the main branch (that is, http://linuxtv.org/hg/v4l-dvb/,
> I am assuming that that's what you meant; I didn't build the ~awalls
> branch, but would be happy to if you'd rather I did),

Larry,

Either way was fine.

> and the tuner works fine now. I watched live TV on the analog input
> for several hours last night, with no problems.

Good. I'll issue a pull request after work today.

> Please let me know if you want me to test anything else...

Nope. Thanks! :)

Regards,
Andy

>
> Thank you!
>
>
> Larry

_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users