On Sun, 19 Jun 2011, Magnus Ekhall wrote: > Thanks for your help. > > I've now enabled a bunch of debug printouts to see what actually happens > under the hood. > > I took a closer look at the kernel log and I'm pretty sure I got one of > those messages regarding the stuck encoder, and the encoder was still > working just fine. Maybe the printouts are unrelated to the problem > after all...
This is what I would expect if the driver did the recovery successfully (but the debug printouts were turned off). > > I also downloaded the latest windows driver from Hauppauges website and > extracted the various firmwares. I found one firmware that was different > from what I was currently running. The new firmware v4l-cx25840.fw has a > md5sum of 95bc688d3e7599fd5800161e9971cc55. I don't know if that is what > "everybody else" is running? > > I don't know if that will help me, but I'm running the new one now. Well "in theory" the cx25840 setup should not make a difference. There are in fact many versions of the cx25840 firmware floating around and they basically all work fine using the pvrusb2 driver. There is a firmware version floating around that is rumored to help enable FM radio reception on the HVR-1950, but the changes also I believe require incompatible V4L core changes. > > Now I'm just waiting for the problem to happen again so that I can take > a dive in the now slightly more verbose kernel logs. :) What would be interesting would be to see evidence of the encoder getting stuff and the recovery *not* working. But it sounds like at this point we haven't even correlated your lack-of-video with a stuck encoder. And if you can get this to happen fairly regularly it would also be useful to see if cooling it might affect the incidence. -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
