UPDATE 12/19/2005 DIDN'T GET THIS TO WORK AT ALL AND RETURNED PRODUCT TO STORE - BUT THERE IS GREAT TROUBLESHOOTING MATERIAL HERE IF YOU'RE TRYING TO GET YOUR PVR-USB TO WORK

Using R5A26 on a Dell Latitude D600 (P4 1.7 GHz, 1 GB RAM, 40 GB HDD, Ac97 sound, ATI9000 Vid). Install goes without incident, using the instructions found here:

http://mysettopbox.tv/phpBB2/viewtopic. ... 117eb11139

Install goes ok as far as I can tell, and the program guide appears to download ok, but when trying to watch tv, I get snow. No channels work. I've confirmed that I can watch a DVD with sound. Also, I do get my channel guide information when flipping through the snow, and the channel guide information is displayed correctly.

Looking at dmesg, there are no START INIT IVTV or END INIT IVTV messages, so obviously there is a problem. I found this line in messages log:

root@mythtv:/var/log# grep 'type set to' messages
Dec 10 16:44:51 mythtv kernel: tuner: type set to 4 (NoTuner) by pvrusb2_a

I've done a lot of digging in the forums and can't find anything. I suspect I missed something when setting up the WinTV PRV2 USB that wasn't documented or was just assumed I would do. I'm new to Linux.

the pvrusb2 won't print the start and end ivtv messages because it is run by the pvrusb2 driver not the ivtv driver. Some of the driver components can come from ivtv such as on my system, the msp34xx driver. Instead of the ivtv messages, you can grep for pvrusb2 in your dmesg. This should give you a slew of information, also the tveeprom info printed in the log. Also, are you trying to tune a cable source, an antenna source or are you using the svideo/composite source? The channel frequency table in mythtv-setup/general needs to match if you're using the tuner (broadcast of you're using antenna, cable if you're using cable). This really fouled me up when I first added a broadcast source (it had been set to cable and so I was having a devil of a time watching UHF channels).

Those are some things I might check. Apologies if you've already done them.

Good information, thank you for all the suggestions. I'm not at the system at the moment but I have changed the settings for us-cable and us-cable-hrc and getting the same results on both (bug fights). My source is cable. Known good cable running from the wall to my PVR-USB, with the USB cable to the laptop. I'll get outputs from the log(s) and post them here if I can't figure out what's going on. I think, perhaps, that I should test the PVR box on a Windows system to be sure it's working before doing any more troubleshooting on the Linux side. Thanks very much again for taking time to help!

Ok, here's some output from an egrep command against the dmesg file. Looks like there is a firmware failure of some type here. I'm going to reload A26 and try again just to see what happens, and will report back. If you have any obvious suggestion that I'm totally missing, please contribute. Thanks!

---
root@mythtv:/home/mythtv# egrep 'pvrusb2|tveeprom' /var/log/dmesg
pvrusb2 pvr_init
pvrusb2 pvr2_hdw_create: hdw=f6718000
pvrusb2 Driver unit number is 0, name is pvrusb2_a
pvrusb2 subsys_stream_mask: 0x7800
pvrusb2 pvr2_hdw_setup(hdw=f6718000) begin
pvrusb2 pvr2_upload_firmware1
pvrusb2 pvr_probe(pvr=f61af780)
usbcore: registered new driver pvrusb2
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : 20051208 (from www.isely.net)
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Debug mask is 4214975 (0x4050bf)
pvrusb2 request_firmware failed for 'pvrusb2.f1'
pvrusb2 Failure uploading firmware1
pvrusb2 pvr2_hdw_setup(hdw=f6718000) done, ok=1 init_ok=0
pvrusb2 Device firmware (re)load executed; it should now reset and reconnect.
----

Did you do the following steps?

assuming that /usr/local/src/pvrusb2 is where you downloaded and expanded your pvrusb2 driver:

cd /usr/local/src/pvrusb2/utils
mkdir win_driver
wget http://hauppauge.lightpath.net/software ... nf_26c.zip
unzip pvrusb2_inf_26c.zip HCWUSB2.sys -d win_driver
./fwextract.pl
cp pvrusb2.f1 pvrusb2.f2 /usr/lib/hotplug/firmware

and assuming that /usr/lib/hotplug/firmware is where hotplug is going to get your firmware.

Reloaded a26 - went ok. Now getting this from the dmesg log. Looks like it's ok. I also did a grep of pvrusb2 from /var/log/messages but I hesitate to post the output as it's several dozen lines. I did find one entry that may be relevant, see below after the dashes. oh yes, I did check and still get snow on channels, and I also loaded this PVR on a Windows system with the Hauppauge software and it's working fine (although I'm not impressed with Hauppauge's software).

root@mythtv:/home/mythtv# egrep 'pvrusb2|tveeprom' /var/log/dmesg
pvrusb2 pvr_init
pvrusb2 pvr2_hdw_create: hdw=f6a1e000
pvrusb2 Driver unit number is 0, name is pvrusb2_a
pvrusb2 subsys_stream_mask: 0x7800
pvrusb2 pvr_probe(pvr=f6d89100)
usbcore: registered new driver pvrusb2
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : 20051208 (from www.isely.net)
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Debug mask is 4214975 (0x4050bf)
pvrusb2 pvr2_hdw_setup(hdw=f6a1e000) begin
pvrusb2 pvr2_upload_firmware1
-----------------------------

A line from /var/log/messages

Dec 12 12:40:23 mythtv kernel: tuner: type set to 4 (NoTuner) by pvrusb2_a

Are there any messages in your logs from tveeprom? Check out http://www.isely.net/pvrusb2.html, there is mention there of what it means when you get a tuner type=4 message, and the mailing list at http://www.isely.net/pipermail/pvrusb2/ might have some info too.

Good luck!

Two things are different:

You are using different pvrusb2 code.
Did you try the pvrusb2-mci-20051113.tar.bz2 snapshot?

Your WinTV-PVR-USB2 probably has a different tuner than mine.
Maybe the ivtv drivers that are in KnoppMyth R5A26 need to
be replaced with the ivtv drivers from the pvrusb2 snapshot?
IF that is the case, then perhaps compile and install the ivtv
drivers trom the snapshot with:

make --directory=ivtv
make --directory=ivtv install

and find and replace the KnoppMyth R5A26 version of the
ivtv drivers following the instructions on http://www.isely.net/pvrusb2.html.

Please include the lines from /var/log/messages that mention
tuner, tveeprom, saa7115, msp34xx, and pvrusb2. That will
help describe what is really happening.

Please include the lines from /var/log/messages that mention
tuner, tveeprom, saa7115, msp34xx, and pvrusb2. That will
help describe what is really happening.

Also lines that mention ivtv.

KnoppMyth R5A26 with the latest pvrusb2 snapshot,
pvrusb2-mci-20051208.tar.bz2, works for me.

I get this from dmesg:

tuner: type set to 47 (LG NTSC (TAPE series)) by pvrusb2_a

This is using the ivtv modules that are installed by R5A26,
not the ones from the pvrusb2 snapshot.

If you need to replace the KnoppMyth ivtv modules, they are in
/lib/modules/2.6.13.2-chw-3/ivtv.

I'll say sorry now .. I'm still pretty fresh with Linux. Are you saying, per your last post, that everything worked for you following the steps provided by Mike Isely that you posted on Nov 25 here, but using the ...1208.tar.bz2 snapshot?

Yes. I just changed the first wget to grab the latest pvrusb2 code.
the rest of the steps were exactly the same as the script. When
it rebooted, I could configure Mythtv and watch TV thru the pvrusb2.
My WinTV-PVR-USB2 works with KnoppMyth R5A26 and either
pvrusb2-mci-20051113.tar.bz2 or pvrusb2-mci-20051208.tar.bz2.

Please post the output of your dmesg or /var/log/messages so we
can see what is happening differently with your setup.

The impetus for buying the PVR-USB was to test Knoppmyth and MythTV in general, and if I really liked it, I planned on either keeping the USB device, or getting a PCI card and returning the USB. I broke down last night and picked up a PVR-150 to stick in a system I have laying around.

It, by the way, worked perfectly out of the box with A26 and my hardware. Tier 1 for sure, and I'll do a detailed write up this week in the Tier 1 forum.

So, now that I've finally seen MythTV in action, and done some recordings (which worked perfectly too, by the way), I'm going to return the PVR-USB and press on with my other plans. However, I still have a few days left before it MUST be returned, so I'll keep working it for posterity if nothing else. Will post the necessary output tonight. Neat system by the way (Knoppmyth). Very easy to use.

Update Supposed to get almost a foot of snow here tonight, so instead I'll be waxing my snowboard. Will work the USB driver problem as time permits. Thanks again for the suggestions and help.

Here's info from DMESG. Doing this from /var/log/messages resulted in way too large a file.

From DMESG:

root@mythtv:~# egrep 'tuner|tveeprom|saa7115|msp34xx|pvrusb2' /var/log/dmesg
pvrusb2 pvr_init
pvrusb2 pvr2_hdw_create: hdw=f7767000
pvrusb2 Driver unit number is 0, name is pvrusb2_a
pvrusb2 subsys_stream_mask: 0x7800
pvrusb2 pvr2_hdw_setup(hdw=f7767000) begin
pvrusb2 Performing a device reset...
pvrusb2 pvr_probe(pvr=f77c6d00)
usbcore: registered new driver pvrusb2
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : 20051208 (from www.isely.net)
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Debug mask is 4214975 (0x4050bf)
tveeprom: Encountered bad packet header [c2]. Corrupt or not a Hauppauge eeprom.
pvrusb2 i2c_attach [client=tveeprom @ 0x50 id=0xf2]
pvrusb2 attaching tveeprom I2C client
tuner (ivtv): chip found at addr 0xc2 i2c-bus pvrusb2_a
pvrusb2 i2c_attach [client=(tuner unset) @ 0x61 id=0x2]
pvrusb2 attaching tuner I2C client
msp34xx: ivtv version
msp34xx: init: chip=MSP3445G-B8, has NICAM support, simple (D) mode, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Oct 9 2005 22:52:16
pvrusb2 i2c_attach [client=MSP3445G-B8 @ 0x40 id=0x1]
pvrusb2 attaching msp3400 I2C client
saa7115 0-0021: saa7115 found @ 0x42 (pvrusb2_a)
pvrusb2 i2c_attach [client=saa7115 @ 0x21 id=0xf1]
pvrusb2 attaching saa7115 I2C client
pvrusb2 i2c_attach [client=tda9887 @ 0x43 id=0xffffffff]
pvrusb2 attaching tda9887 I2C client
pvrusb2 pvr2_upload_firmware2
pvrusb2 Requesting uproc soft reset
pvrusb2 Requesting uproc hard reset
pvrusb2 request_firmware failed for 'pvrusb2.f2'
pvrusb2 device unstable!!
pvrusb2 render_useless
pvrusb2 pvr2_hdw_setup(hdw=f7767000) done, ok=0 init_ok=0
pvrusb2 ***WARNING*** pvrusb2 device hardware appears to be jammed and I can't clear it.
pvrusb2 You might need to power cycle the pvrusb2 device in order to recover.
----------
So I rebooted and power cycled the usbpvr .. and this, after the reboot:

root@mythtv:~# egrep 'tuner|tveeprom|saa7115|msp34xx|pvrusb2' /var/log/dmesg
pvrusb2 pvr_init
pvrusb2 pvr2_hdw_create: hdw=f7795000
pvrusb2 Driver unit number is 0, name is pvrusb2_a
pvrusb2 subsys_stream_mask: 0x7800
pvrusb2 pvr2_hdw_setup(hdw=f7795000) begin
pvrusb2 pvr2_upload_firmware1
pvrusb2 pvr_probe(pvr=f73e1f80)
usbcore: registered new driver pvrusb2
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : 20051208 (from www.isely.net)
/usr/local/src/pvrusb2/pvrusb2-mci-20051208/driver/pvrusb2-main.c: Debug mask is 4214975 (0x4050bf)
pvrusb2 request_firmware failed for 'pvrusb2.f1'
pvrusb2 Failure uploading firmware1
pvrusb2 pvr2_hdw_setup(hdw=f7795000) done, ok=1 init_ok=0
pvrusb2 Device firmware (re)load executed; it should now reset and reconnect.

It looks like the firmware was not loaded.

You should see messages like:

pvrusb2 Performing a device reset...
tuner (ivtv): chip found at addr 0xc2 i2c-bus pvrusb2_a
pvrusb2 i2c_attach [client=(tuner unset) @ 0x61 id=0x2]
pvrusb2 attaching tuner I2C client
msp34xx: ivtv version
msp34xx: init: chip=MSP3445G-B8, has NICAM support, simple (D) mode, simpler (G) no-thread mode
msp34xx: $Id$ compiled on: Oct 9 2005 22:52:16
pvrusb2 i2c_attach [client=MSP3445G-B8 @ 0x40 id=0x1]
pvrusb2 attaching msp3400 I2C client
saa7115 0-0021: saa7115 found @ 0x42 (pvrusb2_a)
pvrusb2 i2c_attach [client=saa7115 @ 0x21 id=0xf1]
pvrusb2 attaching saa7115 I2C client
pvrusb2 pvr2_upload_firmware2
pvrusb2 Requesting uproc soft reset
pvrusb2 Requesting uproc hard reset
pvrusb2 upload of pvrusb2.f2 : 262144 / 262144
tveeprom: ivtv version
tveeprom: Hauppauge: model = 29032, rev = D168, serial# = 7653922
tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio processor = MSP3445 (type = c)
tveeprom: decoder processor = SAA7115 (type = 13)
pvrusb2 eeprom detected ivtv tveeprom module
pvrusb2 eeprom direct call results:
pvrusb2 has_radio=1
pvrusb2 tuner_type=47
pvrusb2 tuner_formats=0x1000
pvrusb2 audio_processor=12
pvrusb2 model=29032
pvrusb2 revision=9508248
pvrusb2 serial_number=7653922
pvrusb2 rev_str=D168
tuner: type set to 47 (LG NTSC (TAPE series)) by pvrusb2_a
pvrusb2 Detected video standard NTSC-M (from eeprom)
etc.

Did you see the messages from fwextract.pl
that the firmware files were successfully extracted and the checksums
were OK when you installed?

Check to make sure that the two firmware files are installed:

ls -l /usr/lib/hotplug/firmware/pvrusb2.f?

If those two files are there, try these steps to to get all the info at the end
of the logs:

shutdown and turn the power off for both PC and pvrusb2.
Boot PC.
When it is done booting, power up the pvrusb2.
Then the tail of the /var/log/messages will have all of the useful messages in one place.