Scott A. Conway wrote:
> --- Tyler Trafford <[EMAIL PROTECTED]> wrote:
>
>> Scott A. Conway wrote:
>>
>>> I first discovered that it would not load the
>> modules, but not load
>>> the firmware at all, so I poked around on the web
>> for a while until I
>>> saw that the 2.6.24 kernels require that the
>> ivtvfb module be loaded
>>> to enable firmware loading.
>> I don't believe this is true.
>
> I beg to differ.
> 2.6.22 and 2.6.23 both attempt to autoload the
> firmware with or without the frame buffer module.
> 2.6.24.4, however, loads only the modules without
> attempting firmware loading.
Oh right, that firmware load was moved. It now happens before the first
capture, not at module load time.
I didn't think that change was in the kernel yet.
>> your firmware.sh
>> located?
>
> /usr/lib/udev
>
> Frustating...isn't it?
There should be a /etc/udev/hotplug.rules. At the end of that file is a
commented line to enable some verbose debugging to /var/log/hotplug.log.
Try enabling that and then rebooting.
--
Tyler Trafford
A sect or party is an elegant incognito devised to save a man from
the vexation of thinking.
-- Ralph Waldo Emerson, Journals, 1831
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
