Yes brendan is corrct. The PVR 500 is essentially 2 PVR 150's on the same pci card. So you should be able to follow the instructions I posted here with the execption of:



change that to:



and remove the line below from /etc/init.d/set_ivtv_params



At present, I've had the best luck with ivtv-0.3.2s.tgz altho I haven't tried ivtv-0.3.2v.tgz yet.

I've currently got a pvr-350 working (with tv out although slightly unstable). I'm adding the pvr-150. Problem is every time I upgrade to any ivtv version that uses john harvey's ivtvdev X driver, X errors with: no device found. Should I use the old X driver?

Could you verify that /etc/mythtv/modules/ivtv should look like:


everything else would be the same since I'd still want to do the ivtvctl for the 350 (video0) and the 150 (video1)

I think /etc/mythtv/modules should look like below since you are using /dev/video1 for the pvr 150:



I'm assuming that tuner=47 is for your pvr 350.

yes... my pvr350 is a tuner 47. Are all pvr150's tuner 57? When I installed ivtv0.3.2u and I removed the tuner assignment from /etc/mythtv/modules/ivtv the driver autodected both cards as tuner 47. Should I disregard that and go 47, 57 or should I use 47, 47?

I think all 150's are tuner=57 (tho I could be wrong) Try both ways and see which one works for ya.

Thanks. Since they write

on the Downloads page, I would guess that's it's really a part of the official branch. But I don't really know for sure

The instructions here-- http://knoppmythwiki.homelinux.org/inde ... stallation worked for me.

[quote]on the Downloads page, I would guess that's it's really a part of the official branch. But I don't really know for sure[/quote]

This has been confirmed to be an official branch, painstakenly tested and confirmed to be stable.

I have a PVR350 and a PVR150MCE and below is my ivtv module file

MCE uses tuner type 47 and my 350 has tuner type 2.

Right now ivtv detects pvr150 first then 350 so the tuner type is set to 47,2 instead of 2,47.


alias char-major-81 videodev
alias char-major-81-0 ivtv
alias char-major-61 lirc_i2c
options ivtv tuner=47.2
#options msp3400 once=1 simple=1
options saa7127 i2c_enable=-1,1
options cx25840 i2c_enable=1 no_black_magic=1

I got mine (none MCE) working using tuner=50

Here's the recipe that worked for me tonight for melting the snow on my pvr-150.

Start with

PVR-150, tuner type 47
KnoppMyth r5a16 (kernel already has up-to-date tuners, see http://www.ivtv.tv/releases/new_tuners/)
(All running in/on a Biostar iDeq 210v. Nice and quiet, especially with a cord-suspended HD.)

See snow on vid out. In June. Bummer.

Add one helping of

ivtv-0.3.6s
(see http://www.ivtv.tv/releases/ivtv-0.3/)
(cd /usr/src; tar xjvf kernel{tab}; cd /usr/local/src; tar xjvf ivtv-0.3.6s.tgz; less ivtv-0.3.6s/doc/install{tab}; cd ivtv-0.3.6s/driver/; make ...)

Still see snow. Looks like same out of season snow as before, though the grains might be finer. Could also just be my imagination.

Finally, bake with newer decoder firmware (HcwFalcn.rom --> /lib/modules/iptv-fw-dec.bin, don't forget to back up old firmware) from

pvr_2.0.24.23035
(see ftp://ftp.shspvr.com/download/wintv-pvr_150-500/inf/ and http://www.gossamer-threads.com/lists/ivtv/devel/21151)

After a cold reboot to make sure that the card doesn't have any residual register values in the way, the snow is now melted down into as much coherence as TV ever achieves. Yay.

Thanks! I've been struggling with my PVR-150 for a few days and something (not exactly sure what) in your message brought it all together. I think the rom I was using was non-ideal (I was getting choppy video and audio that cut out).

A few minor things to note about your steps:

* The link to the ivtv releases has a minor typo. The correct link is http://www.ivtv.tv/releases/ivtv-0.3/

* I'm pretty sure that you meant to copy HcwFalcn.rom to /lib/modules/iptv-fw-enc.bin (not dec)

* In addition to your suggestions, I also had to implement some/all of the directions in Ralph's post above. Specifically, I had to install to HcwMakoA.ROM module to get audio. I read on another board that if you can get audio without this module, you're probably better off though. I also had to do the two file modifcations that Ralph mentioned.

Thanks to you and Ralph and many others for informative posts on this card. Seems like a lot of people have bought these in the last few days.

Now onto IR support!
[/url]

This may be simple but I have never done this.

How do I back up the old firmware from my pvr-150?

Thanks for any insight

The firmware is loaded to the card by the drivers, but doesn't stay when it's powered off. The card usually comes with a CD containing the MS-Windows drivers which the firmware can be extracted from or you can get it from the Hauppauge web site. The bin files used by KnoppMyth can be found (or replaced) at:
But I don't think that's what you're asking...

pi$$ on this card... I'm done. PVR-150MCE tuner type=47 AKA: piece of sh*!. I've been running this card for about 3 months. Poor quality picture (mostly due to a higher tendancy to switch to comb filtering), increased lockups, loud audio (which has gotten better with newer drivers) and most annoying: a discrepency in actual framerate and reported framerate. This last issue makes no sense. Everyone thinks I'm crazy. I play until the OSD says 10min has elapsed, I skip 30 seconds forward and the OSD time changes to 10:30 but I'm about 4 minutes back from where I skipped because myth thinks it's farther than it actually is. Even better is when I get to near the end of a long recording and I can't skip anymore because the time stops at the length of the recording but it's still playing. Myth say "at end". I've tried almost every ivtv driver since 0.2.0 rc3j to the current 0.3.7a. I'm 90% sure the lockups are due to the framerate discrepancy because they happen mostly when skipping in a recording that was recorded with the POS-150MCE.

My suggestion. Don't buy this card. Any suggestions on what to replace it with? I will only put hw encoding cards in my machine so that should narrow the field a bit. I want it to be as stable as my pvr-350 but I don't want another pvr-350. Remote is optional.