[mythtv-users] Re: Highly confused - tuner type=39 ??

[Don Brett]

Thanks for the answers, you're comments led me to a solution.  I have it mostly working now (remote
control is the next thing to attack).  Here's what I did:

Note - Lots of this is guessing and experimentation.  If I came to the wrong conclusion, please correct
me!!)

1. I was using the released version of the ivtv driver (ivtv-0.1.9.tar.gz).  It appears that it does
not support the video-out hardware of the WinPvr 350.  Also, the latest Hauppauge hardware seems to
have a new tuner, which is currently not supported with the release drivers.  I downloaded the latest
driver from Chris Kennedy:

http://67.18.1.101/~ckennedy/ivtv/ivtv-0.3/

ivtv-0.3.1h.tgz

2. Install driver: (downloaded to /usr/src/)
tar -xzvvf  ivtv-0.3.1h.tgz
cd ivtv-0.3.1h
cd drivers
make
make install

3. Make changes to /etc/modules.conf

Original setup:

alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-61 lirc_i2c
options tuner type=2
options saa7127 enable_output=1 output_select=0
options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 saa7127 tuner
add above ivtv ivtv-fb

New setup, which is identical, except for the tuner type:

alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-61 lirc_i2c
options tuner type=39
options saa7127 enable_output=1 output_select=0
options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 saa7127 tuner
add above ivtv ivtv-fb

4. Make changes to /etc/X11/XF86Config as suggested by CKennedy instructions in
/usr/src/ivtv-0.3.1h/doc/README.ivtvfb

5. Interesting observations:
- tveeprom does not install with the released drivers, but it does with ckennedy drivers
- tveeprom shows that the hardware has a type 47 tuner!
- from dmesg:
tveeprom: Hauppauge: model = 48132, rev = K168, serial# = 2844024
tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)

, which would imply that the tuner type is 47.  The old tuner.h definitions stopped at 45 (as seen in
CKennedy's doc/modules.txt instructions).  However, tuner type 39 (which IS in the old list) seems very
close to 47, so I tried it, and it worked.

>From /usr/src/ivtv-0.3.1h/doc/modules.txt - LG_NTSC_NEW_TAPC   39
>From /usr/src/ivtv-0.3.1h/driver/tuner.h - TUNER_LG_NTSC_TAPE       47

- I suspect that something else is using the old tuner definition, which was having trouble finding
it.  Perhaps something associated with bttl?

Thanks again for the help,
Don

PS - for those who wanted to set the channel frequency with ivtvctl while testing the driver
installation (from another post I came across):

# I did solve the same problem, you should compute this :
#     <value> = <frequency_to_set> * 16
#    for setting 175.25 Mhz, set the value 2804

# Channel 2 = 55.25 Mhz / 55.25 x 16 = 884
# Channel 5 = 79.25 Mhz / 79.25 x 16 = 1268

ivtvctl -r 884      # for channel 2
ivtvctl -r 1268    # for channel 5



>
> John Andersen wrote:
>
> >On Saturday 06 November 2004 15:46, Mark wrote:
> >
> >
> >>The patch is available on chris' website,
> >>and I've successfully patched the kernel tuner module, but haven't
> >>succesfully compiled and installed the new module yet.  I just last
> >>night fubar'd my Slackware install by compiling all modules and
> >>installing them without re-compiling my kernel.
> >>
> >>IE, I did:  make modules && modules_install
> >>
> >>which screwed up all my modules so that nothing is working anymore.  I'm
> >>not sure what the right procedure for installing the single module is,
> >>but I'm sure that it IS possible without recompiling a kernel.   If you
> >>figure out what it is, let me know.  I'll be reinstalling Slackware
> >>again tonight.
> >>
> >>
> >
> >I'm glad you posted that, because on the advice of Joel Merrick
> ><joel at servicestyle.com> I was about to do the same thing.
> >
> >I've patched, but not yet compiled - looking for a way to
> >compile JUST one module.
> >
> >But In the past, I have done make modules and install and it
> >worked fine (just took a long time).
> >
> >I wonder if you missed the make cloneconfig step?
> >Theoretically, with a recent and correct config you should be
> >able to recompile modules with no problem.
> >
> >
> >
> >
> I didn't do make cloneconfig.  Not familiar with that one.  It was a
> stock Slack 10.0
> install, I hadn't even recompiled yet.  I tend to recompile only if
> absolutely necessary.
>
> If you try it, let me know how it goes.
>
> Mark
>