I used the patch and tuner 1 was working fine after I compiled and did the modprobe (I never got tuner 2 to work on /dev/video2, hdb HDTV card on 0).

After a reboot I tried to add tuner 2 for the 500 in myth and neiter works, and watch tv does not even let me go to HDTV.

I tried removing the cards and adding them back in, still watch TV does nothing.

Plus the system seem quite sluggish. Things take much longe, like ESC to get out of the frontend...

I bought this stupid PVR-500 card thinking it was supported well, now I read the boards and see that in the last month or two it has become a nightmare....

Thanks for the step-by-step instruction on the patch, maybe I can get this working one day.

And when I try to quit the front end it takes forever and gives me a message that the backend is not running, although I know it is (ps -ealf | grep myth)....

Anyone else patch and get oddness?

I did a totally fresh install and ran the patch and everything looks great this time... Something odd happened the first time with a full HD, not sure why. Maybe recordings were going to / and not /mythtv/tv for some reason.

Thanks again for the patch. And the MCE USB remote works OOTB. I think I have a tier 2 system!

pcHDTV 3000
winTV PVR-500 with USB Remote

How can you tell if you have the new PVR-500 with the Samsung drivers vs whatever they were before the switch?

TIA

I peeled the sticker off one of the tuner cans.
Hauppauge places their sticker on top of Samsungs, so you have to be careful, but this can be done.

If you have the card installed in the system, just look at the logfiles. See this wiki page for how to extract the relevant block of information: http://www.knoppmythwiki.org/index.php?page=CheckingLogFiles
Look for the fairly obvious line that says "tuner model". There are known issues with at least the Samsung TCPN 2121P30A, and possibly others in that family.

This is easier and potentially less destructive if you want to try to return the card.

BTW - I would recommend upgrading to the 0.7.1 drivers and applying the Samsung patch over that since it fixes other problems as well.

I don't have that directory:
/usr/src/linux/drivers/media/video/

And a "find . -name tuner-types.c" doesn't show the file on my machine.
Where do we get the source necessary to patch?

TIA

As always, see the CompileIvtv page on the wiki for this and other details. http://www.knoppmythwiki.org/index.php?page=CompileIvtv

Ah, the missing link was I needed the kernel source. That is where tuner-types.c is.

The CompileIvtv page doesn't tell you how to get the source, so for other newbie's this worked for me.
uname -r
2.6.17-10-generic
wget ftp://ftp.kernel.org/pub/linux/kernel/v ... 17.tar.bz2
cd /usr/src
sudo tar -xvjf linux-2.6.17.tar.bz

I am trying to determine the scope of updating my PVR500 ivtv drivers.

I have an ASUS MB with onboard nvidia.
I am currently using Ubuntu Edgy (6.10) using the binary driver that is included with that distribution.

So, I have recompiled ivtv in the past to update the firmware. That was due to ivtv not starting correctly. So I ended updating ivtv-fw-dec.bin, ivtv-fw-enc.bin and hcwpvrp2.sys.

Now I want to update the actual pvr-500 samsung tuners.

Since I am needing the kernel source for this, does this mean that I will be installing a new kernel?

Or does it mean that I update the kernel source (with the patch) and that allows me to compile a new ivtv that takes advantage of the updated pvr-500 firmware.

I am new to all of this, so excuse the lack of knowledge.

cd /usr/src/linux-2.6.17
sudo make oldconfig (not sure what this does, hopefully keeps things the same)
sudo make


I gather I am not actually replacing the entire kerner, given I am only installing the modules. These would be equivalent to DLL's on Windows?
sudo make modules_install
sudo rmmod ivtv
sudo rmmod tuner
sudo modprobe tuner
sudo modprobe ivtv

TIA

The kernel source should already be there in /usr/src, the wiki page does tell you this (it's step 1 there), and I strongly recommend using the patched version that Cecil provides there rather than the raw release from kernel.org that you're fetching.

From the wiki page:


Ah. The missing bit of information. Telling us this up front might have gotten you a better answer...