[pvrusb2] 2040:2400 ID New WinTV-pvr-usb2

[Mike Isely]

On Sat, 4 Mar 2006, mike wrote:

> Hey guys, I recently went out to Best Buy hoping they had a Plextor
> ConnectX that I could plug in and use as a tuner for mythtv.  Instead,
> they only had the Hauppauge WinTV-PVR-USB2, so I bought that and figured
> that I'd see if I can help out.
>
> It does report with Vendor ID 2040:2400 and I am willing to be a guinea
> pig.  I'm running Gentoo Liux on a 2.6.13 kernel, amd64.
>

OK.  Join the club :-)

> The latest snapshot does compile with these warnings:
>
> *** Warning: "tveeprom_hauppauge_analog"
> [/root/pvrusb2-mci-20060209/driver/pvrusb2.ko] undefined!
> *** Warning: "i2c_transfer"
> [/root/pvrusb2-mci-20060209/driver/pvrusb2.ko] undefined!
> *** Warning: "i2c_add_adapter"
> [/root/pvrusb2-mci-20060209/driver/pvrusb2.ko] undefined!
> *** Warning: "i2c_del_adapter"
> [/root/pvrusb2-mci-20060209/driver/pvrusb2.ko] undefined!
> *** Warning: "request_firmware"
> [/root/pvrusb2-mci-20060209/driver/pvrusb2.ko] undefined!
> *** Warning: "release_firmware"
> [/root/pvrusb2-mci-20060209/driver/pvrusb2.ko] undefined!

Those warnings have to do with your build environment.  You need to be 
running a kernel with lots of V4L stuff configured into it; this looks 
like none of that is present.


>
> The fwfind.sh script works and results in pvusb2.f1 and pvrusb2.f2 being
> generated.

The new hardware includes a newer driver, which alas appears not to be on 
Hauppauge's web site.  Since fwfind.sh grabs from there if it can't find 
your CD, you might not have viable firmware for the device.  Also, with 
this new device there is a *third* firmware file you'll need.  These 
problems I've already solved and the next driver snapshot will include an 
updated fwextract.pl which will account for all of this.


>
> I copied the firmware to the respective directory and the kernel modules
> (just had the pvrusb2.ko file) and did a depmod -a, then tried to insert
> the module.  Here's the error:
>
> FATAL: Error inserting pvrusb2
> (/lib/modules/2.6.13-gentoo/pvrusb2/pvrusb2.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
>
> Here's the dmesg output:
>
> Linux video capture interface: v1.00
> pvrusb2: Unknown symbol release_firmware
> pvrusb2: Unknown symbol request_firmware
> pvrusb2: Unknown symbol i2c_del_adapter
> pvrusb2: Unknown symbol i2c_add_adapter
> pvrusb2: Unknown symbol i2c_transfer
> pvrusb2: Unknown symbol tveeprom_hauppauge_analog
> pvrusb2: Unknown symbol release_firmware
> pvrusb2: Unknown symbol request_firmware
> pvrusb2: Unknown symbol i2c_del_adapter
> pvrusb2: Unknown symbol i2c_add_adapter
> pvrusb2: Unknown symbol i2c_transfer
> pvrusb2: Unknown symbol tveeprom_hauppauge_analog

Yeah, that's the same issue you noted earlier.  Your kernel needs to have 
V4L configured into it in order to use the standalone driver.  However 
since that driver doesn't at all support the new hardware (yet), you're 
still stuck :-(


>
>
> Let me know if there's anything else I can do to help.  Feel free to
> send any updated drivers to this email address (mikepetty at gmail.com).
>

At this point, I *still* do not have a sample of the newer device 
hardware.  I've been making progress but all testing & debugging has been 
by proxy through others with the new device.  I intend on releasing a new 
driver snapshot as soon as I have it all working, but we're not there yet.

If you (or anyone else here) would like to jump in with testing and/or bug 
chasing, please e-mail me directly or come find me on IRC in the #pvrusb2 
channel.

   -Mike


-- 
                         |         Mike Isely          |     PGP fingerprint
      Spammers Die!!     |                             | 03 54 43 4D 75 E5 CC 92
                         |   isely @ pobox (dot) com   | 71 16 01 E2 B5 F5 C1 E8
                         |                             |