On 3/24/06, Praveen Shenoy <[EMAIL PROTECTED]> wrote: > Thanks Nick. I don't understand much about how things get loaded but, > before I changed my initial ramdisk to include loading the ivtv > drivers, everything worked as in Jarod Wilson's HOWTO. I haven't > tried putting the old image back and trying to see if I can watch TV > using the 350's TV-OUT. But I bet it will work. My guess is the > error's caused by the initial loading of the ivtv-fb using the > modified ramdisk causes the error you are pointing to. Either way, I > will check tonight to see if the firmware exists in the hotplug
> directory. Correct me if I am wrong, my understanding is that, while > the initrd is being loaded and executed, the file systems are not yet > mounted. So, the firmware not being in the hotplug directory should > not be an issue at-least at that point. But I could be totally wrong > as I don't have much knowledge about this. Will post again after > verifying the firmware being in the hotplug directory. You're mostly correct, but your conclusion is wrong. When ivtv is loaded, the filesystem hasn't been mounted, so ivtv can't find the firmware files. You need to add the firmware files into the *initrd image* so the files can be found even when the filesystem isn't mounted. Ross _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
