Mailing List Archive: MythTV: Users

Tuner type not set

Index | Next | Previous | View Threaded

brad+myth at templetons

May 29, 2006, 12:19 AM

Post #1 of 12 (1015 views)
Permalink

Tuner type not set

>
> Add
>
> options ivtv tuner=50
>
> to your modprobe.conf. If you have multiple cards, use -1 for all the
> other tuners in a comma-separated list. I.e. if you have a PVR-150 and
> a PVR-500 set up so the 150 is initialized first (i.e. is /dev/video0),
>
> options ivtv tuner=50,-1,-1
>
> Or, if the PVR-150 is initialized last, use
>
> options ivtv tuner=-1,-1,50
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
Ah! It works wonderfully. Thanks! The sound is even good. "IT IS
ALIVE!"

Alas, this is not working for me. I have also run into this problem
after upgrading to 2.6.12 kernel, ivtv 0.4.5. tveeprom identifies
the pvr250 as tuner type 50, but I still get "tuner 0-0061: tuner type not set"
even if I modprobe ivtv tuner=50

At first I was just finding I could not tune the channel (nor was I
getting any sound after the upgrade) but after more recent changes,
including add/remove of cards in mythtv-setup in an attempt to fix
other things, it now just crashes the backend if I try to use this
tuner with:

2006-05-29 00:11:25.303 MainServer: HandleRemoteEncoder(cmd IS_BUSY) Unknown enc
oder: 1, exiting

(Perhaps I've mucked something up in other upgrade efforts. Upgrading
continues to be an adventure, which means you wait a while before doing
it, and that makes it even worse...)

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

May 29, 2006, 7:50 AM

Post #2 of 12 (971 views)
Permalink

Re: Tuner type not set [In reply to]

On 05/29/2006 03:19 AM, Brad Templeton wrote:
> Alas, this is not working for me. I have also run into this problem
> after upgrading to 2.6.12 kernel, ivtv 0.4.5. tveeprom identifies
> the pvr250 as tuner type 50, but I still get "tuner 0-0061: tuner type not set"
> even if I modprobe ivtv tuner=50
>
> At first I was just finding I could not tune the channel (nor was I
> getting any sound after the upgrade) but after more recent changes,
> including add/remove of cards in mythtv-setup in an attempt to fix
> other things, it now just crashes the backend if I try to use this
> tuner with:
>
> 2006-05-29 00:11:25.303 MainServer: HandleRemoteEncoder(cmd IS_BUSY) Unknown enc
> oder: 1, exiting
>
>
> (Perhaps I've mucked something up in other upgrade efforts. Upgrading
> continues to be an adventure, which means you wait a while before doing
> it, and that makes it even worse...)

Without logs, we couldn't even begin to guess where it's failing.

tac /var/log/messages |
sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p;
/= START INIT IVTV =/q' |
tac

should provide all the relevant information.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

brad+myth at templetons

May 29, 2006, 12:27 PM

Post #3 of 12 (964 views)
Permalink

Re: Tuner type not set [In reply to]

On Mon, May 29, 2006 at 10:50:49AM -0400, Michael T. Dean wrote:
> On 05/29/2006 03:19 AM, Brad Templeton wrote:
> > Alas, this is not working for me. I have also run into this problem
> > after upgrading to 2.6.12 kernel, ivtv 0.4.5. tveeprom identifies
> > the pvr250 as tuner type 50, but I still get "tuner 0-0061: tuner type not set"
> > even if I modprobe ivtv tuner=50
> >
> > At first I was just finding I could not tune the channel (nor was I
> > getting any sound after the upgrade) but after more recent changes,
> > including add/remove of cards in mythtv-setup in an attempt to fix
> > other things, it now just crashes the backend if I try to use this
> > tuner with:
> >
> > 2006-05-29 00:11:25.303 MainServer: HandleRemoteEncoder(cmd IS_BUSY) Unknown enc
> > oder: 1, exiting
> >
> >
> > (Perhaps I've mucked something up in other upgrade efforts. Upgrading
> > continues to be an adventure, which means you wait a while before doing
> > it, and that makes it even worse...)
>
> Without logs, we couldn't even begin to guess where it's failing.
>
> tac /var/log/messages |
> sed -n '/=\ \ END INIT IVTV\ \ =/,/= START INIT IVTV =/p;
> /= START INIT IVTV =/q' |
> tac
>

AH, sorry.

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.5 (tagged release) loading
ivtv: Linux version: 2.6.12-2.3.legacy_FC3smp SMP 686 REGPARM 4KSTACKS gcc-3.4
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 WinTV PVR 250 card (cx23416 based)
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 18 (level, low) -> IRQ 169
ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tveeprom 0-0050: Hauppauge model 32062, rev B185, serial# 7476925
tveeprom 0-0050: tuner model is TCL 2002N 6A (idx 85, type 50)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is MSP3445 (idx 12)
tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
tveeprom 0-0050: has no radio, has IR remote
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
msp3400 0-0040: MSP3445G-B8 found @ 0x80 (ivtv i2c driver #0)
msp3400 0-0040: MSP3445G-B8 supports radio, mode is autodetect and autoselect
ivtv0: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40]
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02040024
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner 0-0061: tuner type not set
tuner 0-0061: tuner type not set
ivtv0: Initialized WinTV PVR 250, card #0
ivtv: ==================== END INIT IVTV ====================

Alas, everything looks very happy it seems, except the tuner type not
set. This output is coming even from "modprobe ivtv tuner=50"

(In a lovely irony, I bumped the kernel to 2.6.12 to get dvb support
for the pchdtv 3000 after myth started failing in atsc mode, and thus
lost the pvr250.)
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

andrew.kreps at gmail

May 30, 2006, 9:33 AM

Post #4 of 12 (958 views)
Permalink

Re: Tuner type not set [In reply to]

I had that exact problem with 2.6.16 and my PVR-350. After trying
ivtv 0.4.x and 0.6.2, I found that only 0.6.1 would actually work
properly. If it's quick and easy to do, you may want to give the
0.6.x branches a shot.

On 5/29/06, Brad Templeton <brad+myth[at]templetons.com> wrote:
> > > Alas, this is not working for me. I have also run into this problem
> > > after upgrading to 2.6.12 kernel, ivtv 0.4.5. tveeprom identifies
> > > the pvr250 as tuner type 50, but I still get "tuner 0-0061: tuner type not set"
> > > even if I modprobe ivtv tuner=50
> > >
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

andrew.kreps at gmail

May 30, 2006, 9:33 AM

Post #5 of 12 (969 views)
Permalink

Re: Tuner type not set [In reply to]

andrew.kreps at gmail

May 30, 2006, 9:33 AM

Post #6 of 12 (956 views)
Permalink

Re: Tuner type not set [In reply to]

brad+myth at templetons

May 30, 2006, 12:56 PM

Post #7 of 12 (958 views)
Permalink

Re: Tuner type not set [In reply to]

On Tue, May 30, 2006 at 09:33:41AM -0700, Andrew Kreps wrote:
> I had that exact problem with 2.6.16 and my PVR-350. After trying
> ivtv 0.4.x and 0.6.2, I found that only 0.6.1 would actually work
> properly. If it's quick and easy to do, you may want to give the
> 0.6.x branches a shot.
>

Sigh. Well, that needs a upgrade to the latest kernel, which in turn
means either building it myself, or the even more complex but worthwhile
upgrade to FC5 to get an RPM of it. Neither of which I have time to do
today. I'll have to do it when I get back and see if I can't downgrade
the box with ivtv to the prior drivers.
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

brad+myth at templetons

May 30, 2006, 3:38 PM

Post #8 of 12 (963 views)
Permalink

Re: Tuner type not set [In reply to]

On Tue, May 30, 2006 at 12:56:47PM -0700, Brad Templeton wrote:
> On Tue, May 30, 2006 at 09:33:41AM -0700, Andrew Kreps wrote:
> > I had that exact problem with 2.6.16 and my PVR-350. After trying
> > ivtv 0.4.x and 0.6.2, I found that only 0.6.1 would actually work
> > properly. If it's quick and easy to do, you may want to give the
> > 0.6.x branches a shot.
> >
>
> Sigh. Well, that needs a upgrade to the latest kernel, which in turn
> means either building it myself, or the even more complex but worthwhile
> upgrade to FC5 to get an RPM of it. Neither of which I have time to do
> today. I'll have to do it when I get back and see if I can't downgrade
> the box with ivtv to the prior drivers.

Hmm. I decided to try running ivtv 0.2, and still get the error, so it's
not the ivtv version, it seems. The question then, is what is it?
I also replaced the in-kernel versions of msp3400, tveeprom, tuner and tda9887
with the ivtv versions as recommended.

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.2.0 (tagged release) loading
ivtv: Linux version: 2.6.12-2.3.legacy_FC3smp SMP 686 REGPARM 4KSTACKS gcc-3.4
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 250 card
ivtv: Found an iTVC16 based chip
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 18 (level, low) -> IRQ 169
ivtv: XXX PCI device: 0x2570 vendor: 0x8086
ivtv: i2c attach [client=tveeprom,ok]
tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0)
ivtv: i2c attach [client=(tuner unset),ok]
saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv: i2c attach [client=saa7115,ok]
msp3400 0-0040: MSP3445G-B8 found @ 0x80 (ivtv i2c driver #0)
msp3400 0-0040: MSP3445G-B8 supports radio, mode is autodetect and autoselect
ivtv: i2c attach [client=MSP3445G-B8,ok]
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
ivtv: i2c attach [client=Hauppauge IR,ok]
lirc_dev: lirc_register_plugin: sample_rate: 10
tveeprom 0-0050: Hauppauge model 32062, rev B185, serial# 7476925
tveeprom 0-0050: tuner model is TCL 2002N 6A (idx 85, type 50)
tveeprom 0-0050: TV standards NTSC(M) (eeprom 0x08)
tveeprom 0-0050: audio processor is MSP3445 (idx 12)
tveeprom 0-0050: decoder processor is SAA7115 (idx 19)
tveeprom 0-0050: has no radio, has IR remote
ivtv: Tuner Type 50, Tuner formats 0x00001000, Radio: yes, Model 0x00891615, Rev
ision 0x00000000
ivtv: NTSC tuner detected
ivtv: Radio detected
ivtv: Encoder revision: 0x02040024
ivtv: Encoder Firmware may be buggy, use version 0x02040011
ivtv: Configuring WinTV PVR 250 card with 5 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: Create stream 4
ivtv: Registered v4l2 device, streamtype 4 minor 64
ivtv: Setting Tuner 50
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
tuner 0-0061: tuner type not set
ivtv: Initialized WinTV PVR 250, card #0
ivtv: ==================== END INIT IVTV ====================
ivtv: ivtv_enc_thread: pid = 5071, itv = 0xe0b71aa0

And all attempts to reference the tuner generate the "Tuner type not set" error.

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

May 30, 2006, 4:01 PM

Post #9 of 12 (960 views)
Permalink

Re: Tuner type not set [In reply to]

On 05/30/2006 06:38 PM, Brad Templeton wrote:
> Hmm. I decided to try running ivtv 0.2, and still get the error, so it's
> not the ivtv version, it seems. The question then, is what is it?
> I also replaced the in-kernel versions of msp3400, tveeprom, tuner and tda9887
> with the ivtv versions as recommended.

Hard to tell with the default output. It would be much easier to tell
if you specify an appropriate debug setting for your tuner module. I.e.
add to your modprobe.conf:

options tuner debug=2

and then run "depmod -ae" then load your ivtv modules (without the
"tuner=" option--i.e. remove "options ivtv tuner=50" from modprobe.conf)
and post your dmesg output.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

brad+myth at templetons

May 30, 2006, 5:50 PM

Post #10 of 12 (976 views)
Permalink

Re: Tuner type not set [In reply to]

On Tue, May 30, 2006 at 07:01:02PM -0400, Michael T. Dean wrote:
> On 05/30/2006 06:38 PM, Brad Templeton wrote:
> > Hmm. I decided to try running ivtv 0.2, and still get the error, so it's
> > not the ivtv version, it seems. The question then, is what is it?
> > I also replaced the in-kernel versions of msp3400, tveeprom, tuner and tda9887
> > with the ivtv versions as recommended.
>
> Hard to tell with the default output. It would be much easier to tell
> if you specify an appropriate debug setting for your tuner module. I.e.
> add to your modprobe.conf:
>
> options tuner debug=2
>
> and then run "depmod -ae" then load your ivtv modules (without the
> "tuner=" option--i.e. remove "options ivtv tuner=50" from modprobe.conf)
> and post your dmesg output.
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Well, it gets curiouser. I worked a bit harder at removing the kernel's
built in drivers and put in a hand built 0.2 and then 0.4.4 version of
ivtv (did not do 0.4.5 because I wanted to change things.)

I eventually got past the tuner not being identified, and the system is
working now -- except I am getting the classic "cable channels off by one"
problem, ie. channel 64 shows up when you tune to 63. (But 5 shows up on
5.) This problem is normally identified with tuner mis-identification, but
it's always been identifying it as a 50, and after it started working it
still does so, and I haven't seen any indication this model would be other
than that. Is there a nice directory of other tuner numbers to try?

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.4.4 (tagged release) loading
ivtv: Linux version: 2.6.12-2.3.legacy_FC3smp SMP 686 REGPARM 4KSTACKS gcc-3.4
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 WinTV PVR 250 card (cx23416 based)
ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 18 (level, low) -> IRQ 169
lirc_i2c: chip found @ 0x18 (Hauppauge IR)
ivtv0: i2c attach to card #0 ok [client=Hauppauge IR, addr=18]
lirc_dev: lirc_register_plugin: sample_rate: 10
tveeprom: ivtv version
tveeprom: Hauppauge: model = 32062, rev = B185, serial# = 7476925
tveeprom: tuner = TCL 2002N 6A (idx = 85, type = 50)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = MSP3445 (type = c)
tveeprom: decoder processor = SAA7115 (type = 13)
ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50]
tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0
ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61]
saa7115 0-0021: ivtv driver
saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21]
msp3400 0-0040: ivtv driver
msp3400 0-0040: chip=MSP3445G-B8 +nicam +simple +simpler +radio mode=simpler
ivtv0: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40]
msp3400 0-0040: msp34xxg daemon started
ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
ivtv0: Encoder revision: 0x02040024
ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total)
ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total)
ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total)
ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total)
tuner: type set to 50 (TCL 2002N) by ivtv i2c driver #0
tuner: switching to v4l2
tuner: tv freq set to 67.25
tuner: tv 0x07 0x10 0x8e 0x01
ivtv0: Initialized WinTV PVR 250, card #0
ivtv: ==================== END INIT IVTV ====================

_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

david at shay

May 30, 2006, 7:16 PM

Post #11 of 12 (954 views)
Permalink

Re: Tuner type not set [In reply to]

On 5/30/06, Brad Templeton <brad+myth[at]templetons.com> wrote:
>
> On Tue, May 30, 2006 at 07:01:02PM -0400, Michael T. Dean wrote:
> > On 05/30/2006 06:38 PM, Brad Templeton wrote:
> > > Hmm. I decided to try running ivtv 0.2, and still get the error, so
> it's
> > > not the ivtv version, it seems. The question then, is what is it?
> > > I also replaced the in-kernel versions of msp3400, tveeprom, tuner and
> tda9887
> > > with the ivtv versions as recommended.
> >
> > Hard to tell with the default output. It would be much easier to tell
> > if you specify an appropriate debug setting for your tuner module. I.e.
> > add to your modprobe.conf:
> >
> > options tuner debug=2
>

I recently went down a very similar path for this same error and after about
3 days I dual-rebooted into Windows and realized that it didn't work there
either. I then reseated the card and all was well again. Probably not your
problem, but worth a shot.

brad+myth at templetons

May 30, 2006, 7:21 PM

Post #12 of 12 (947 views)
Permalink

Re: Tuner type not set [In reply to]

On Tue, May 30, 2006 at 10:16:29PM -0400, David Shay wrote:
> On 5/30/06, Brad Templeton <brad+myth[at]templetons.com> wrote:
> >
> >On Tue, May 30, 2006 at 07:01:02PM -0400, Michael T. Dean wrote:
> >> On 05/30/2006 06:38 PM, Brad Templeton wrote:
> >> > Hmm. I decided to try running ivtv 0.2, and still get the error, so
> >it's
> >> > not the ivtv version, it seems. The question then, is what is it?
> >> > I also replaced the in-kernel versions of msp3400, tveeprom, tuner and
> >tda9887
> >> > with the ivtv versions as recommended.
> >>
> >> Hard to tell with the default output. It would be much easier to tell
> >> if you specify an appropriate debug setting for your tuner module. I.e.
> >> add to your modprobe.conf:
> >>
> >> options tuner debug=2
> >
>
> I recently went down a very similar path for this same error and after about
> 3 days I dual-rebooted into Windows and realized that it didn't work there
> either. I then reseated the card and all was well again. Probably not your
> problem, but worth a shot.

I guess I'll try that if nothing else worse, but it seems unlikley a system
upgrade would cause a tuning frequency error!
_______________________________________________
mythtv-users mailing list
mythtv-users[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com