Reinstalling v4l-dvb fixed it. On Sun, Aug 22, 2010 at 10:48 PM, Richard <[email protected]> wrote:
> On Sun, Aug 22, 2010 at 4:21 PM, Mike Isely <[email protected]> wrote: > >> >> On Sun, 22 Aug 2010, Richard wrote: >> >> > Debian 5 Lenny (2.6.26-2-686) on HP Pavilion zv5235us (2.8Ghz/1.5Gb) >> MythTV >> > 0.23 Hauppauge WinTV-HVR-1950, working with Video4Linux driver. >> > >> > I had this working great. Tonight I had to unplug everything to get >> access >> > to the computer so I could change my WPA key. Afterward, I was in >> mythweb >> > scheduling recordings, and under "Upcomming Recordings" everything is >> gone. >> > >> > I checked the "record" table in the "mythconverge" database in mysql. >> All of >> > my schedule programs are there. >> > >> > Googling I got a tip to check the backend. Under Capture Cards > MPEG >> > /Dev/Video0 all of my info is missing. It seems most with this problem >> are >> > people who are trying to get it initially setup, but mine was already >> > working for a couple of weeks. >> > >> > # dmesg | grep pvrusb2 gives: >> > [ 12.262593] usbcore: registered new interface driver pvrusb2 >> > [ 12.262600] pvrusb2: Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner : V4L >> > in-tree version >> > [ 12.262603] pvrusb2: Debug mask is 31 (0x1f) >> > [ 13.272131] firmware: requesting v4l-pvrusb2-73xxx-01.fw >> > [ 13.365442] pvrusb2: wrong fx2 firmware size >> > [ 13.365442] pvrusb2: Failure uploading firmware1 >> > [ 13.365442] pvrusb2: Device initialization was not successful. >> > [ 13.365442] pvrusb2: ***WARNING*** pvrusb2 device hardware appears to >> be >> > jammed and I can't clear it. >> > [ 13.365442] pvrusb2: You might need to power cycle the pvrusb2 device >> in >> > order to recover. >> > >> > I've tried repeatedly to unplug and replug the HVR-1950, and rebooting. >> > Nothing. >> > >> > Any tips? >> > >> >> Richard: >> >> You must have done more than just change a WPA key. >> >> First, I can't speak to the MytvTV issues and this is the wrong list for >> those questions anyway. >> >> As for the pvrusb2 driver's refusal to start, it is complaining that the >> FX2 firmware size is wrong, which can happen if you have a more recent >> 16KB-sized FX2 firmware image and an older driver which looks for only >> 8KB firmware. >> >> A little less than a year ago, the pvrusb2 driver was updated to handle >> the larger firmware image, but if you're running a pvrusb2 driver >> included from a Linux kernel, then that kernel must be fairly recent. >> >> You said this was working before, so if the driver isn't working now >> then it's because either you somehow updated that firmware image or >> switched to a version of the driver that doesn't work with that >> firmware. That's obviously more than just a change of a WPA key. Maybe >> you swapped firmware at some point in the recent past but haven't >> rebooted the device since then? >> >> -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 >> [email protected] >> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 >> > > Mike, > > Thanks for the reply. > > I never got the firmware to work. I had to go with the Video 4 Linux route > and followed the directions to get that going. Then it worked. > > I did let the machine do some automatic updates. Do you think that could > have broken it? If so, an update to what? > > Thanks, > Richard > _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
