On Sunday 12 February 2006 17:43, Andrew Dodd wrote:
> Quoting Brad Farris <[EMAIL PROTECTED]>:
> > When I boot up and look at dmesg I see things like:
> >
> > tuner 1-0061: tuner type not set
> > tuner 1-0061: tuner type not set
> >
> > Other than that everything looks normal, but all I get is static.
> > When I do this:
> >
> > $ rmmod ivtv
> > $ modprobe ivtv tuner=57,57
> >
> > and check dmesg I see the "type not set" messages have disappeared,
> > and my card begins to work! So my question is why is it necessary
> > to include "tuner=57,57"? And how to I get that part to be included
> > during bootup?
>
> Look more carefully at your dmesg output *without* the tuner=57,57
> line.
>
> That line was a workaround some people used to get partial (but not
> complete) functionality on PVR-500s with Samsung tuners. "tuner type
> not set" is what you will see if your copies of tuner.o and
> tveeprom.o do not support the Samsung tuner.
>
> Samsung tuner support requires ivtv 0.4.2 with some extra
> installation steps (you need to override the kernel's tuner.o and
> tveeprom.o with one from ivtv, and change one of the ivtv build files
> - it's in one of the READMEs). Even that support has some problems,
> there is a later patch from Hans that fixes most of the problems.
I'll probably release a 0.4.3 this week containing this patch and also
support for tuner 103 (the LG-something tuner).
Hans
>
> If you see *anything* about a Samsung TCPN tuner (I forget the exact
> model number, it starts with 21) in your dmesg, you need to go
> through the aforementioned extra steps to enable Samsung support -
> tuner type 57 will only give you partial functionality.
>
>
> _______________________________________________
> 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
