On 9/17/07, Robert Johnston wrote: >On 9/17/07, Mark Paulus <mark.paulus at verizonbusiness.com> wrote: >> What howto did you follow? (URLs are always good....) >> One thing to check is: Did you name things v4l (vee-four-ell), >> or v41 (vee-four-one)? Where did you actually wind up with the >> firmware files??? Could you do an 'ls -l' on your firmware >> files? or do a "locate v4l | grep '\.fw'"? > >Could you also try: >rmmod ivtv >modprobe ivtv > >And see if the second IVTV entry in dmesg loads the firmware AOK. If >so, you need to adjust which loads first, as ivtv is loading before >hotplug (So it can't load the firmware using hotplug).
As it turns out, I missed this statement in the general how-to: "It is recommended to compile all as modules. Ivtv will not be able to load the firmware (yet) if it is build in!!" I didn't build ivtv as a module, once I did that, it looks like things are working. Thanks, Erik _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
