Yes, I was able to get the entire script to work, and that includes the two firmware files. And I've done at least 6 reloads, each one very successful, at least from a "Knoppmyth loaded" properly point of view. I'll follow your steps tonight and check it out. It's starting to feel like I have a hardware problem, but then again, it worked fine in Windows. Bizarre.

Thank you,
Dane

OK. I just wanted to make sure about the firmware being installed before
I started this next step.

Hauppauge has switched the hardware inside the WinTV-PVR-USB2 quite
often. You may have a new tuner in yours. Mine is a few months old, so it
was already supported.

Since you ran it under Windows, which firmware did you install under Windows?
Did it come from the Hauppauge CD-ROM or did you download a newer version
from the Hauppauge web site?

The Windows system should have something like:
c:\windows\system32\drivers\hcwusb2.sys

My script uses the v2.6c firmware. The fwfind.sh script in the
pvrusb2-mci-20051208/utils directory can extract firmware either
from Hauppauge CD-ROM's, or firmware downloaded from the
Hauppauge web site. I choose the wget option in case there wasn't
a spare cdrom drive available during the KnoppMyth install.

If you can copy the hcwusb2.sys file from the working Windows system
to the utils/win_driver directory instead of unziping the one from
pvrusb2_inf_26c.zip, then the fwextract.pl script might be able to extract it.

Watch to see if the checksums match a know version of the firmware.

If your pvrusb2 really does use a new version of the firmware that
fwextract.pl doesn't recognize, then there are ways to extract the firmware
which I have never had to use.

See http://www.isely.net/pvrusb2-utils.html for more
info on extracting firmware.

I think that the firmware has to be loaded so that tveeprom figures out what kind
of tuner is inside the box.

You may want to try asking the experts on the pvrusb2 mailing lists. It doesn't
sound like this is a mythtv problem.

I toyed with the box for a bit longer, and returned it to the store from whence it came. Thread closed, as far as I'm concerned. Thank you for all the help - good troubleshooting experience gleaned from this foray.

Sorry I came late to this thread; I only just now found out about its existence. From reading through this discussion it looks like you were fighting two problems (1) the firmware was not always being loaded, and (2) your device had an unrecognized tuner type.

The fact that you hit (2) a few times means that you in fact did successfully get past (1), if at least intermittently.

Issue (2) as rja points out is that Hauppauge likes changing out the tuner module without changing models. There is a LARGE amount of support in V4L to detect and handle 50+ different types of tuner modules; probably we could have gotten past this issue with a little digging. PCI devices from Hauppauge suffer from this same sort of "problem"; you probably just got lucky when you swapped out the device and got something better known by V4L (both ivtv and pvrusb2 use the same tuner handling architecture).

As for issue (1), the fact that you apparently got the firmware to load at least once (in order to hit issue (2)) probably means you were very close to having it solved.

So it's a shame you gave up on the PVR USB2 device. But in the end all that matters is that now you have something that works. Have fun with your PVR