I recall some folks changing the firmware load script in /lib/udev. I think they added some time delays (sleep) in the script to allow the hardware to settle prior to hitting it with tests for firmware being loaded. I will see if I can pursue those via google.
I will also re-extract the firmware, just in case it is at issue. On Sun, Jun 14, 2009 at 1:46 PM, Mike Isely<[email protected]> wrote: > My first guess is that the firmware file is corrupt or that something is > going wrong with the loading process. A while back there were some > posts here showing problems loading the encoder's firmware. In that > case the Linux kernel was handing truncated / bad data to the driver. I > pointed this out but I never got a followup from the user so I don't > know what that root cause was. It might be related however because the > mechanism for requesting firmware data out of user space is the same > regardless of the specific firmware in question. > > -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 > _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
