Hauppauge HVR-1950 with Ubuntu Intrepid
Quoted 5 lines · William Austin
Quoted 3 lines
I have a Hauppauge WinTV HVR-1950 USB box on a box running Ubuntu Intrepid. Although I should expect problems from a testing distro, I've tried getting this box working on stable, Live-CD versions of Ubuntu, Open Suse, and Mandriva as well (because they were what I had around the house.)
First, there is a kernel problem in Ubuntu Intrepid where, if the 1950 is plugged into USB, the system will hang on boot. Yet, if I boot without it and plug it in after boot, the drivers (pvrusb2 et al) seem to load, but no device nodes are created. I have downloaded the firmware, renamed it properly, and placed it in
/lib/firmware. So I'm at a loss on how to troubleshoot. Here's the relevant information on plug-in the box in after the system has been booted.What firmware did you " download and rename " ??
I tried both the version on Stephen Toth's site and the version that came with my windows driver CD (4.5a). The firmware was extracted with Mike Isely's perl script and renamed according to information on his website. There were three files total.
Quoted 1 line
Where did you get " v4l-pvrusb2-73xxx-01.fw " ?? or did you forget it?
See above.
Quoted 7 lines
Quoted 4 lines
dmesg says:
usbcore: registered new interface driver pvrusb2
pvrusb2: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : V4L in-tree version
pvrusb2: Debug mask is 31 (0x1f)Those lines will show up is you simply "modprobe pvrusb2" even if the device is not present. What comes next? It should download firmware, >disconnect & reconnect USB automatically, then continue on with driver initialization.
That was the end of my dmesg as far as the dvb stuff is concerned. There were a few more lines dealing with my wireless adapter, but I didn't think it relevant. I did not modprobe pvrusb2. Those lines were the result of just plugging the device in.
Quoted 12 lines
Quoted 10 lines
lsmod (edit):
usbcore
pvrusb2i2c_corev4l2_common
tveepromdvb_core
cx2341x
videodevv4l1_compat
Quoted 1 line
lsmod doesnt tell us anything. You can load all those modules by hand, and it says nothing about the device that you have plugged in.
But I didn't load them by hand. Just trying to help people help me.
Quoted 9 lines
Quoted 5 lines
/proc/deviceslists DVB as a character device.Now, I'm assuming I'm missing some chip drivers. I think I should have at least three, if memory serves, but only cx2341x is loading on plug-in. Unfortunately (and I assume this is another Ubuntu problem) I can't unload pvrusb2 once loaded. It hangs the terminal. It makes playing around with it a tedious endeavor.
If anyone has had the same problems or could give some advice, I appreciate it in advance.
I think you're best off taking a look at the pvrusb2 home page and reading the information there. If you are still having trouble, then please just paste your full dmesg into an email so that we can have a better idea of what's wrong. Good Luck,
Mike
If I hadn't already checked out the pvrusb2 home page and read the information there, I wouldn't be feeling patronised on a mailing list asking for help. But then, I understand requests like this can get tedious, so no worries.
I just rebooted with the device unplugged. Here is the end of my dmesg (the changes after I plugged in the HVR-1950):
[ 5115.393036] usb 2-2: new high speed USB device using ehci_hcd and address 12 [ 5115.529015] usb 2-2: configuration #1 chosen from 1 choice [ 5115.616658] Linux video capture interface: v2.00 [ 5115.672945] usbcore: registered new interface driver pvrusb2 [ 5115.674849] pvrusb2: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : V4L in-tree version [ 5115.674857] pvrusb2: Debug mask is 31 (0x1f) [ 5116.673636] firmware: requesting v4l-pvrusb2-73xxx-01.fw [ 5116.697396] pvrusb2: Device microcontroller firmware (re)loaded; it should now reset and reconnect. [ 5116.861037] usb 2-2: USB disconnect, address 12 [ 5116.862449] pvrusb2: Device being rendered inoperable [ 5118.488036] usb 2-2: new high speed USB device using ehci_hcd and address 13 [ 5118.625005] usb 2-2: configuration #1 chosen from 1 choice
Now, for the first time (and it'd have to be after I've already written to the list asking about it) it seems to load the firmware correctly; however, I'm still without a device node for it.
Will
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
William,
On Tue, Sep 9, 2008 at 9:52 PM, William Austin <[email protected]> wrote:
[snip]
Quoted 1 line
If I hadn't already checked out the pvrusb2 home page and read the information there, I wouldn't be feeling patronised on a mailing list asking for help. But then, I understand requests like this can get tedious, so no worries.
Sorry about that... I couldn't know for sure whether you had seen that website or not.
Quoted 14 lines
I just rebooted with the device unplugged. Here is the end of my dmesg (the changes after I plugged in the HVR-1950):
[ 5115.393036] usb 2-2: new high speed USB device using ehci_hcd and address 12 [ 5115.529015] usb 2-2: configuration #1 chosen from 1 choice [ 5115.616658] Linux video capture interface: v2.00 [ 5115.672945] usbcore: registered new interface driver pvrusb2 [ 5115.674849] pvrusb2: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : V4L in-tree version [ 5115.674857] pvrusb2: Debug mask is 31 (0x1f) [ 5116.673636] firmware: requesting v4l-pvrusb2-73xxx-01.fw [ 5116.697396] pvrusb2: Device microcontroller firmware (re)loaded; it should now reset and reconnect. [ 5116.861037] usb 2-2: USB disconnect, address 12 [ 5116.862449] pvrusb2: Device being rendered inoperable [ 5118.488036] usb 2-2: new high speed USB device using ehci_hcd and address 13 [ 5118.625005] usb 2-2: configuration #1 chosen from 1 choice
Quoted 1 line
Now, for the first time (and it'd have to be after I've already written to the list asking about it) it seems to load the firmware correctly; however, I'm still without a device node for it.
Now this is interesting. Can you show me what lsusb looks like after the above?
Something indeed looks wrong.
Also -- just to confirm -- I am assuming that you are using the stock intrepid 2.6.27-2 kernel? Please show me the output from 'uname -r'
-Mike
_______________________________________________
linux-dvb mailing list
[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Quoted 4 lines · William Austin
If I hadn't already checked out the pvrusb2 home page and read the information there, I wouldn't be feeling patronised on a mailing list asking for help. But then, I understand requests like this can get tedious, so no worries.
I just rebooted with the device unplugged. Here is the end of my dmesg (the changes after I plugged in the HVR-1950):
Quoted 13 lines
[ 5115.393036] usb 2-2: new high speed USB device using ehci_hcd and address 12 [ 5115.529015] usb 2-2: configuration #1 chosen from 1 choice [ 5115.616658] Linux video capture interface: v2.00 [ 5115.672945] usbcore: registered new interface driver pvrusb2 [ 5115.674849] pvrusb2: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : V4L in-tree version [ 5115.674857] pvrusb2: Debug mask is 31 (0x1f) [ 5116.673636] firmware: requesting v4l-pvrusb2-73xxx-01.fw [ 5116.697396] pvrusb2: Device microcontroller firmware (re)loaded; it should now reset and reconnect. [ 5116.861037] usb 2-2: USB disconnect, address 12 [ 5116.862449] pvrusb2: Device being rendered inoperable [ 5118.488036] usb 2-2: new high speed USB device using ehci_hcd and address 13 [ 5118.625005] usb 2-2: configuration #1 chosen from 1 choice
These same symptoms came across the pvrusb2 mailing list recently. A couple things (unfortunately not very helpful)...
First, missing firmware should NEVER cause the driver to get stuck. Even if the FX2 firmware is missing it should still be possible to remove the kernel module. You're saying that isn't working, which is a serious problem. But right now I have nothing to go on. This could be a real bug. But it'd be nice to reproduce the problem using a vanilla kernel from kernel.org.
Second, from the messages above, the point where things are getting stuck is very, very early in initialization. The HVR-1950 (and similar devices) actually have to appear "twice" before each will work. The first time the driver is supposed to load the FX2 microcontroller's firmware and reset the device. As part of that reset process, the hardware will logically disconnect from the USB cable and then reconnect. It's just like unplugging then re-plugging the device back into the USB port. Except on this reconnect, the driver (pvrusb2 in this case) must "figure out" that the FX2 firmware has already been loaded - and take a different course of action. In the case of the pvrusb2 driver, a test is performed to figure out if the firmware is present and if the test passes then the driver continues normal initialization and eventually you get stuff appearing in /dev.
But what you have showing above is running aground on that reconnect. The hardware connects up, the driver sends the FX2 firmware, a reset takes place, the device reappears, BUT the USB core never reassociates the hardware with the pvrusb2 driver. The pvrusb2 driver hasn't even started to run that second time yet so there's nothing in the driver itself (e.g. the "test") that could have gone wrong. Thus the initialization process gets stuck.
Bad FX2 firmware *could* do that (e.g. FX2 processor resets and crashes after being loaded), however the extraction process simply won't let you extract incorrect firmware and I think you said you tried downloaded FX2 firmware as well. In fact, in all the work I've done on the pvrusb2 driver, I've *never* actually had a case of bad FX2 firmware. Ever. That makes me wonder if instead something with that kernel is causing the FX2 firmware to be corrupted during the download process. But if that were the case pretty much anything in your system requiring a firmware download would probably be messed up (it's all common code elsewhere in the kernel). So far the only reports I've heard of this have involved Ubuntu's build of the 2.6.27 kernel - which itself is not considered release-stable yet. Makes me wonder...
Well I said it wouldn't be very helpful. But that's where my line of thinking is right now.
-Mike
Signature · 8 lines
Mike Isely isely @ pobox (dot) com PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8 _______________________________________________ linux-dvb mailing list [email protected] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb