[pvrusb2] WinTV PVR USB2 with Beagleboard driver
marco at panzanella.net
marco at panzanella.net
Thu Dec 17 22:41:06 CST 2009
I am getting closer. There is pre-compiled modules in the angrstrom
archives for this board. My problem is that I only copied the
pvrusb2.ko file instead of using tar on the modules file from the root
directory. I did that for my kernel version and the driver seems to
load fine. I have a /dev/video0 device now. I can also copy from this
device to a file but only get static so far.
One thing that I have found is that I occassionally get the following:
[ 2452.706542] usb 1-2.3: firmware: requesting v4l-cx2341x-enc.fw
[ 2452.856628] pvrusb2: ***WARNING*** Device encoder firmware seems to
be missing.
[ 2452.864746] pvrusb2: Did you install the pvrusb2 firmware files in
their proper location?
[ 2452.876617] pvrusb2: request_firmware unable to locate encoder file
v4l-cx2341x-enc.fw
I did follow your setup file to copy the firmware (downloaded) of the
PVR USB2 device to /lib/firmware:
root at beagleboard:~# ls /lib/firmware/v4l-*
144 /lib/firmware/v4l-cx23418-apu.fw 156
/lib/firmware/v4l-cx2341x-init.mpg
160 /lib/firmware/v4l-cx23418-cpu.fw 16 /lib/firmware/v4l-cx25840.fw
16 /lib/firmware/v4l-cx23418-dig.fw 8
/lib/firmware/v4l-pvrusb2-24xxx-01.fw
260 /lib/firmware/v4l-cx2341x-dec.fw 8
/lib/firmware/v4l-pvrusb2-29xxx-01.fw
376 /lib/firmware/v4l-cx2341x-enc.fw
I have udev and the firmware.sh file has two directories, one of them
being /lib/firmware. So I don't know why the driver can't find the
firmware file. Is there a better way to test why it can't find the
file? I did copy ALL the firmware files to this directory (as you can
see above) so I shouldn't be missing a supporting file either. Do I
need to make these executable or something else?
Thanks for all your help.
-------- Original Message --------
Subject: [SPAM] Re: [pvrusb2] WinTV PVR USB2 with Beagleboard driver
From: Mike Isely <isely at isely.net>
Date: Thu, December 17, 2009 11:09 pm
To: Communications nexus for pvrusb2 driver <pvrusb2 at isely.net>
On Tue, 15 Dec 2009, marco at panzanella.net wrote:
> Dear Mike,
>
> Thanks for the reply. Sorry to disturb you again. I was wondering if
> you can make a quick comment on my progress. I think I sucessfully
> compiled the pvrusb driver. When I plug in your device I see the
> following errors:
Marco:
No sorry, you're still not there yet. Looks like you're still having
some build problems here...
>
> [ 2288.158325] usb 1-2.2: new high speed USB device using ehci-omap
and address 6
> [ 2288.307006] usb 1-2.2: configuration #1 chosen from 1 choice
> [ 2288.502258] tveeprom: disagrees about version of symbol
struct_module
> [ 2288.509490] v4l1_compat: disagrees about version of symbol
struct_module
> [ 2288.518280] videodev: disagrees about version of symbol
struct_module
> [ 2288.525970] v4l2_common: disagrees about version of symbol
struct_module
> [ 2288.533966] cx2341x: disagrees about version of symbol
struct_module
> [ 2288.542022] dvb_core: disagrees about version of symbol
struct_module
These errors still suggest that the system is still trying to link up
modules that have been compiled in different ways or with different
kernel versions :-(
> [ 2288.570526] pvrusb2: version magic '2.6.32 mod_unload ARMv7 '
should be '2.6.29-omap1 preempt mod_unload modversions ARMv7 '
Well I know that "omapX" corresponds to a TI architecture that happens
to use an ARM core. So this sounds like a compilation environment
mismatch. Last time I saw something like this the pvrusb2 module would
fail to load. Are you *sure* the driver actually loaded?...
>
> So it appears the pvrusb2 driver is fine now. I don't know if the
rest
> matter. I still don't have /dev/video0 so the issue is either the
> above dependencies or you mention in your usage.html file about
running
> udev. I believe I have udev installed. Do you think the /dev/video0
> isn't being created because of dependency issues or something else?
If the pvrusb2 driver had loaded then you should have seen a number of
additional messages in the system log generated by the driver itself as
it goes through the steps to initialize the hardware. I'm guessing you
don't have those messages (otherwise I assume you would have pasted
them
here). So possibly the driver didn't load. Without the driver then of
course /dev/video0 can't appear. If you do "lsmod" do you see "pvrusb2"
anywhere in the output of the command?
-Mike
--
Mike Isely
isely @ isely (dot) net
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
_______________________________________________
pvrusb2 mailing list
pvrusb2 at isely.net
[1]http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
References
1. http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
More information about the pvrusb2
mailing list