[pvrusb2] HVR-1950 on the SheevaPlug (Ubuntu Jaunty)

[charleswgreenjr at aim.com]

Hi all,



I'm attempting to get an HVR-1950 running on the new SheevaPlug, a miniature server with an ARM processor (see http://www.marvell.com/products/embedded_processors/developer/kirkwood/sheevaplug.jsp for more details).? It's running Ubuntu Jaunty, I've extracted the necessary firmware into /lib/firmware, and I have a kernel with the following drivers compiled in:



pvrusb2

dvb_core

cx2341x

tveeprom

v4l2_common

videodev

v4l1_compat



I also have my "official" MythTV Intel box, currently running Ubuntu Hardy, with a newer (2.6.28) kernel, which successfully handles the tuner, and I have a basic Intel Ubuntu Jaunty system which also announces the tuner, loads firmware, etc. when I plug the tuner in, so I believe that I understand the basics of getting this thing going.



However, when I plug the tuner into the SheevaPlug, here's all I see on the kernel log:



usb 1-1.3: new high speed USB device using orion-ehci and address 5
usb 1-1.3: configuration #1 chosen from 1 choice

When I plug the tuner into either of the Intel boxes, I get quite a bit more:

[? 593.490018] usb 1-4: new high speed USB device using ehci_hcd and address 2
[? 593.644339] usb 1-4: configuration #1 chosen from 1 choice
[? 593.698637] Linux video capture interface: v2.00
[? 593.763880] usbcore: registered new interface driver pvrusb2
[? 593.763905] pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
[? 593.763910] pvrusb2: Debug mask is 31 (0x1f)
[? 594.760164] usb 1-4: firmware: requesting v4l-pvrusb2-73xxx-01.fw
[? 594.781660] pvrusb2: Device microcontroller firmware (re)loaded; it should now reset and reconnect.
[? 596.328962] usb 1-4: USB disconnect, address 2
[? 596.329440] pvrusb2: Device being rendered inoperable
[? 596.600019] usb 1-4: new high speed USB device using ehci_hcd and address 3
[? 596.759694] usb 1-4: configuration #1 chosen from 1 choice
[? 596.842134] cx25840' 1-0044: cx25843-24 found @ 0x88 (pvrusb2_a)
[? 596.912732] tuner' 1-0042: chip found @ 0x84 (pvrusb2_a)
[? 596.937121] tveeprom 1-00a2: Hauppauge model 75111, rev C3E9, serial# 5371386
...


It appears from 'grep -l' that the 'Linux video capture interface' messages should be coming from 'videodev' (at least in the Jaunty case; I don't see this one line on my Hardy system, though the rest of the log looks identical).



Is it possible that some configuration related to USB is preventing the firmware request from being received / processed?? Anything which might prevent 'videodev' or 'usbcore' from doing their thing?



Thanks for any pointers / suggestions,



Charles Green