I just picked up a second PVR-250. It is the newer revision and requires that /etc/mythtv/modules/ivtv be edited with:

rather than:


This would not be a problem if I didn't want 2 tuners. That is after all why I picked up the second. (Damn thing cam from the same store, same box, and same sticker on the box saying model 980 as the one from a couple of weeks ago..errrr!)

I have looks around here and the ivtv forums but just can't find the right combination of search terms to find and answer. I have tried:

But only the first type is used. I have tried it 2,39 or 2, 39 and so on. I have also tried adding the line options tuner type=2 into ivtv1 and the line options tuner type=39 into ivtv0 and removing it from ivtv, and every other permutation of this, trying to get something to work. Nothing.... Please help.
PS: Has anyone else noticed the quality difference between the "newer" and slightly "older" 250's? The older seems to have more interlace issues, and a red tent to everything. I keep xv off, and there is a distinct difference between the two.

I just picked up a PVR-250 that needs tuner type 39 and my other 350 needs tuner type 2. When I do a modinfo tuner I get the folowing:

filename: /lib/modules/2.4.25-chw/kernel/drivers/media/video/tuner.o description: "device driver for various TV and TV+FM radio tuners"
author: "Ralph Metzler, Gerd Knorr, Gunther Mayer"
license: "GPL"
parm: probe short array (min = 1, max = 48), description "List of adapter,address pairs to scan additionally"
parm: probe_range short array (min = 1, max = 48), description "List of adapter,start-addr,end-addr triples to scan additionally"
parm: ignore short array (min = 1, max = 48), description "List of adapter,address pairs not to scan"
parm: ignore_range short array (min = 1, max = 48), description "List of adapter,start-addr,end-addr triples not to scan"
parm: force short array (min = 1, max = 48), description "List of adapter,address pairs to boldly assume to be present"
parm: debug int
parm: type int
parm: addr int
parm: tv_range int array (min = 2, max = 2\)
parm: radio_range int array (min = 2, max = 2\)
parm: pal string

As shown above in bold, the type can only be one value.
Does anyone know if this is on anyone's list to get fixed?

_________________
Athalon XP 2600
512MB RAM
ATI 9000
Sony DVD Burner
3ware 7506-8
1 Segate 200GB Knoppmyth
6 Segate 200GB Raid-5 (1TB!)

What version of ivtv are you using? IIRC, you have to be using a relatively recent version of 0.1.10pre2 to get the tuner option to work.

Try the following in ivtv:

options tuner type=39,-1

this will cause the first tuner to be set to 39 and the second to autodetect.

This should either be stickied, or in the FAQ

Hi, I just bought a new PVR-250 to go add to the existing PVR-250. I have been having great trouble getting the new PVR-250 to work properly.

The old PVR-250 shows up as the "model 32032, rev B310" and the new one is "model 32063, rev B185". The old PVR-250 works just fine but when I try to get the new one to tune a station it just gives static.

I tried the instructions on how to get the new PVR-250s to find their tuners properly by updating to the most recent recompiled IVTV modules. That seemed to work but did not fix the problem with the new PVR-250 tuning properly.



tveeprom: Hauppauge: model = 32032, rev = B310, serial# = 6983654
tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio_processor = MSP3440 (type = 11)
ivtv: i2c attach [client=tveeprom[0],ok]
i2c-core.o: client [tveeprom[0]] registered to adapter [ivtv i2c driver #0](pos. 2).
tveeprom: Hauppauge: model = 32062, rev = B185, serial# = 7362937
tveeprom: tuner = <unknown> (idx = 85, type = -1)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio_processor = MSP3445 (type = 12)
ivtv: i2c attach [client=tveeprom[1],ok]
i2c-core.o: client [tveeprom[1]] registered to adapter [ivtv i2c driver #1](pos. 2).


Would someone help me debug this? Thanks in advance.

What really scares me is that "model = 32032" appears frequently on google associated with PVR-250 but "model = 32062" does not appear at all! WTF!

Andrew Lynch

I wanted to add some configuration info to my original post to help anyone with figuring this out.

I just bought the PVR-250 from Circuit City and it arrived Wednesday 1 Sep 2004

I followed the instructions on adding new second PVR-250's in this post:

http://mysettopbox.tv/phpBB2/viewtopic. ... ght=pvr250

so, I am using a new IVTV version from the website:

ivtv-0.1.10-pre2-ck107s.tgz

I am running original KnoppMyth R4 with latest updated mythtv debs (15.1, I think and data direct w/ zap2it) with Nvidia's video module 5336

Linux mythtv 2.4.21-xfs #1 SMP Thu Oct 2 17:33:33 PDT 2003 i686 GNU/Linux

here is the listing from dmesg of the part related to IVTV:

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.1.10 (0.1.10pre2-ck107s) loading
ivtv: Linux version: 2.4.21-xfs
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
PCI: Found IRQ 12 for device 02:09.0
ivtv: XXX PCI device: 0x2560 vendor: 0x8086
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
saa7115: detecting saa7115 client on address 0x42
saa7115: writing init values
ivtv: i2c attach [client=saa7115[0],ok]
i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver #0](pos. 0).
saa7115: status: (1E) 0x50, (1F) 0xc0
msp34xx: ivtv version
msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Sep 4 2004 00:25:59
ivtv: i2c attach [client=MSP3448W-A2,ok]
i2c-core.o: client [MSP3448W-A2] registered to adapter [ivtv i2c driver #0](pos. 1).
i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
i2c-core.o: driver tveeprom registered.
tveeprom: Hauppauge: model = 32032, rev = B310, serial# = 6983654
tveeprom: tuner = Philips FI1236 MK2 (idx = 10, type = 2)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio_processor = MSP3440 (type = 11)
ivtv: i2c attach [client=tveeprom[0],ok]
i2c-core.o: client [tveeprom[0]] registered to adapter [ivtv i2c driver #0](pos. 2).
ivtv: Tuner Type 2, Tuner formats 0x00001000, Radio: yes, Model 0x00893450, Revision 0x00000000
ivtv: NTSC tuner detected
ivtv: Radio detected
ivtv: Encoder revision: 0x02040011
ivtv: Configuring WinTV PVR 250 card with 5 streams
ivtv: Create DMA stream 0 using 64 32768 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1 using 64 32768 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 256 4096 byte buffers 1048576 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 32 32768 byte buffers 1048576 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 2
ivtv: i2c client addr: 0x61 not found!
ivtv: i2c client addr: 0x61 not found!
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: i2c client addr: 0x61 not found!
saa7115: decoder set norm NTSC
saa7115: set audio: 0x01
ivtv: Initialized WinTV PVR 250, card #0
ivtv: Autodetected WinTV PVR 250 card
ivtv: Found an iTVC16 based chip
PCI: Found IRQ 3 for device 02:0b.0
PCI: Sharing IRQ 3 with 00:1d.7
ivtv: XXX PCI device: 0x2560 vendor: 0x8086
saa7115: starting probe for adapter ivtv i2c driver #1 (0x10005)
saa7115: detecting saa7115 client on address 0x42
saa7115: writing init values
ivtv: i2c attach [client=saa7115[1],ok]
i2c-core.o: client [saa7115[1]] registered to adapter [ivtv i2c driver #1](pos. 0).
saa7115: status: (1E) 0x48, (1F) 0xc0
msp34xx: ivtv version
msp34xx: init: chip=MSP3445G-B8, has NICAM support, simple (D) mode, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Sep 4 2004 00:25:59
ivtv: i2c attach [client=MSP3445G-B8,ok]
i2c-core.o: client [MSP3445G-B8] registered to adapter [ivtv i2c driver #1](pos. 1).
tveeprom: Hauppauge: model = 32062, rev = B185, serial# = 7362937
tveeprom: tuner = <unknown> (idx = 85, type = -1)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio_processor = MSP3445 (type = 12)
ivtv: i2c attach [client=tveeprom[1],ok]
i2c-core.o: client [tveeprom[1]] registered to adapter [ivtv i2c driver #1](pos. 2).
i2c-core.o: adapter ivtv i2c driver #1 registered as adapter 1.
ivtv: Tuner Type -1, Tuner formats 0x00001000, Radio: yes, Model 0x00891615, Revision 0x00000000
ivtv: NTSC tuner detected
ivtv: Radio detected
ivtv: Encoder revision: 0x02040011
ivtv: Configuring WinTV PVR 250 card with 5 streams
ivtv: Create DMA stream 0 using 64 32768 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 1
ivtv: Create DMA stream 1 using 64 32768 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 1 minor 33
ivtv: Create stream 2 using 256 4096 byte buffers 1048576 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 225
ivtv: Create DMA stream 3 using 32 32768 byte buffers 1048576 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 25
ivtv: Create stream 4
ivtv: Registered v4l2 device, streamtype 4 minor 65
ivtv: i2c client addr: 0x61 not found!
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: i2c client addr: 0x61 not found!
saa7115: decoder set norm NTSC
saa7115: set audio: 0x01
ivtv: Initialized WinTV PVR 250, card #1
ivtv: ==================== END INIT IVTV ====================


hardware:
Emachines T2692, 2.6GHz Celeron with 512M DDR RAM
80GB hda, 200GB hdb, DVD-ROM/CD-RW hdc, 200GB hdd
PVR-250 6 months old primary tuner (works fine) with grey remote
PVR-250 1 day old, (doesn't work, only static on screen)
ATI wonder VE remote (I removed the ATI TV wonder VE)
PCI Nvidia GeForce4 440MX w/tvout


I really can't think of any other relevant information. If I am missing something, please let me know and I will add.

My question:

Do I need to update the tuner.o module? It appears that the ivtv modules are not recognizing the new PVR-250 hardware.

Thoughts?

THANKS IN ADVANCE!

Andrew Lynch

Oh, one more thing. Here is the ivtv module config file

root@mythtv:/etc/mythtv/modules # less ivtv

alias char-major-81 videodev
alias char-major-61 lirc_i2c

#options ivtv debug=1
options ivtv card=85 type=39

#options tuner type=2
options tuner type=-1,39

options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c


Obviously, I tried tuner 39 but if tveeprom can't recognize the tuner that is not much help. Still get just static when I switch to that tuner.

If I start KnoppMyth box, the MythTV starts as usual and I can watch channels normally on the primary tuner. Press Y to switch to the alternate tuner and I get "snow" static screens.

Andrew Lynch

Ok, after more investigation it seems the problem is similar to the one wififun posted originally with a subtle twist. My PVR-250's are detected in the opposite order so the older PVR-250 is detected first and the newer PVR-250 is second.

The symptoms I am seeing is that I can configure both ivtv modules to the older PVR-250 (card=10, type=2) or the newer PVR-250 (card=85, type=39). That means I get broken functionality either way the tuner.o is configured.

Configuring both PVR-250's for the older model results in my primary tuner working perfectly but the secondary tuner only presenting static screens and failing to tune properly.

Configuring both PVR-250's to the newer model results in the primary tuner only properly tuning channels 62 and higher but nothing but static between 2-61. The secondary tuner works normally.

So the issue is seems to be linux can load ivtv module twice, once for each PVR-250, however, tuner can only be set for a single tuner type and if my tuners are different, then I am in trouble. I have seen 2 sorts of workarounds posted on the forum:

first method posted here relys on the newer PVR-250 getting detected first and configuring tuner for it and relying on autoconfiguring to correctly configure the older PVR-250. Since my older PVR-250 is detected first, relying on autoconfigure for the newer PVR-250 fails. ivtv apparently does not support autoconfigure for the newer card=85 type=39 style PVR-250s.

second method is to patch the tveeprom.c ivtv driver itself to allow autoconfiguration of the newer PVR-250 tuner. Then specify the card type and tuner type.

Bottom line is ... neither configuration works properly.

I think what I need is a new tuner.o module that accepts multiple, different tuner types for the same PVR-250 ivtv modules. How to do this?

My tuner.o dates from Oct 2003. Can tuner.o be updated from the source tree or is that going to break the system?

Is there anyway to switch the order Linux detects the PVR-250's so I can rely on the workarounds posted here?

Is there a way to force configuration of tuner type per each instance of ivtv being loaded and associated with a specific PVR-250?

HELP!

Thanks!

Andrew Lynch

have you tried card=x,x and type=x,x with the appropriate numbers of course.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets

Yes, to no avail. The tuner.o apparently only accepts a single tuner type parameter per class of tuners.

root@mythtv:~ # less /etc/mythtv/modules/ivtv
alias char-major-81 videodev
alias char-major-61 lirc_i2c

#options ivtv debug=1
#options ivtv card=85 type=39
#options ivtv card=10,85 type=2,39
options ivtv card=10,85 type=-1,39

#options tuner type=2
#options tuner type=39

options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c

I commented out the card=xx,yy type=zz,aa when I tried to get the first PVR-250 to autoconfigure its tuner and that did not work either.

Thanks for the response!

Andrew Lynch

Happy ending, I think. Checked with the Gurus on ivtv-devel and they used their ivtv Kung Fu to dispatch my problem in spite of my mishandling their advice. Check it out here:

http://sourceforge.net/mailarchive/foru ... m_id=27233

this is what my ivtv config file finally looked like when it worked:

root@mythtv:~ # less /etc/mythtv/modules/ivtv
alias char-major-81 videodev
alias char-major-61 lirc_i2c

#options ivtv debug=1
#options ivtv card=85 type=39
options ivtv card=10,85 type=2,39
#options ivtv card=10,85 type=-1,39

options ivtv tuner=-1,39


#options tuner type=2
#options tuner type=39

options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c


Initial testing seems to indicate it MythTV works fully with both PVR-250's. I will post again if that turns out to not be true. Looks good so far though!

Thanks All!

Andrew Lynch

Did you have to make any other changes besides upgrading ivtv from 0.1.9 to 0.1.10-44_pre2_ch107... ?

I'm in the exact same boat...two PVR-250s, one type 2 tuner and one type 39.

Most of what I know of Linux comes from following Jarod's MythTV on Fedora setup guide several times, so please keep that in mind if you respond!

Thanks,
Jeff

Well, to start, I am not a KnoppMyth nor linux expert but what I would do is to examine the output of your dmesg to see what card is detected first. Post the results here. To make that easier, I use another PC with WinXP on it and log in to the KnoppMyth box via Putty. Then cut and paste the dmesg output to a message on this forum.

dmesg | less

or try the same with:

rmmod tveeprom
modprobe tveeprom


The order of how the linux kernel detects the PVR-250s is important since it will determine the order of the parameters of ivtv in its config file.

Or, if you know you have KnoppMyth working properly just try the order I posted and if that doesn't work, flip them.

Try this first,

root@mythtv:~ # less /etc/mythtv/modules/ivtv
alias char-major-81 videodev
alias char-major-61 lirc_i2c

options ivtv card=10,85 type=2,39
options ivtv tuner=-1,39

options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c




then this...


root@mythtv:~ # less /etc/mythtv/modules/ivtv
alias char-major-81 videodev
alias char-major-61 lirc_i2c

options ivtv card=85,10 type=39,2
options ivtv tuner=39,-1

options msp3400 once=1 simple=1
add below ivtv msp3400 saa7115 tuner
add above ivtv lirc_dev lirc_i2c




Andrew Lynch

PS, no guarantees this will work at all. The folks on ivtv-devel are still saying that type idx=85 PVR-250s are officially unsupported resulting in all sorts of unknown side effects.

I was recording a show last night and went to watch the other tuner and my KnoppMyth box TV video display (even for console mode) went completely nutso and corrupted garbage for the first time ever in almost a year of operation. I was able to use the keyboard and "log in blind" and tell it to poweroff normally, but it just points out that some stuff is experimental and just barely works, if it works at all. Please bear that in mind. YMMV.

Well, I'm not using Knoppmyth, but rather a FC1 build using Jarod's guide. But anyway, hopefully this is what you mean...
-----------------
tveeprom.c: starting probe for adapter ivtv i2c driver #0 (0x10005)
tveeprom.c: detecting tveeprom client on address 0xa0
9 [04] 20 77 00 40 00 59 70 00
3 [05] 8c 00
8 [06] 3e 7d 00 00 15 16 89
2 [07] 70
Not sure what to do with tag [07]
3 [09] 13 5f
Not sure what to do with tag [09]
3 [0a] 08 55
4 [0b] 98 18 0c
Not sure what to do with tag [0b]
2 [0f] 01
Not sure what to do with tag [0f]
2 [10] 01
Not sure what to do with tag [10]
2 [11] 00
Not sure what to do with tag [11]
tvee: Hauppauge: model=32062, rev=B185, serial#=7362816
tvee: tuner=<unknown> (idx=85, type=-1)
tvee: tuner fmt=NTSC(M) (eeprom=0x08, v4l2=0x00001000)
tvee: audio_processor=MSP3445 (type=12)
tveeprom.c: starting probe for adapter ivtv i2c driver #1 (0x10005)
tveeprom.c: detecting tveeprom client on address 0xa0
9 [04] 20 77 00 40 55 6e 63 00
3 [05] 9b 00
8 [06] 30 bd 00 00 50 14 a5
2 [07] 70
Not sure what to do with tag [07]
3 [09] 13 5f
Not sure what to do with tag [09]
3 [0a] 08 0a
4 [0b] 98 18 0c
Not sure what to do with tag [0b]
2 [10] 01
Not sure what to do with tag [10]
2 [11] 00
Not sure what to do with tag [11]
tvee: Hauppauge: model=48432, rev=I110, serial#=6516309
tvee: tuner=Philips FI1236 MK2 (idx=10, type=2)
tvee: tuner fmt=NTSC(M) (eeprom=0x08, v4l2=0x00001000)
tvee: audio_processor=MSP3440 (type=11)
-------------

I don't recall getting all of that stuff before, but that's what it's doing now.

I can make either card work by changing the tuner type in modules.conf (switch between 2 and 39), but not both together of course. I've got it set to use 39, since that one has a remote (my other 250 is a Freestyle).

Does the "ivtv-cardtype-patch" from PCAlchemy for ivtv 0.1.9 work? I was getting all sorts of errors when I tried to use 0.1.10...

I SERIOUSLY doubt that that old patch for 0.1.9 will work for any of the new tuner 39 cards.

_________________
Have a question search the forum and have a look at the KnoppMythWiki.

Xsecrets