Did you put ivtv into your boot image with mkinitrd? If you followed
Jarod's guide you may have. If this is the case, you need to do that
again now that you've compiled the new version.

On 9/4/05, Timothy McFadden <[EMAIL PROTECTED]> wrote:
> >1. Look for both ivtv.o and ivtv.ko and look over the entire filesystem.
> >Also, IIRC, the .ko extension is for linux 2.6 modules, but 2.4 and
> >earlier used .o.
> 
> I haven't tried looking for any .o ( I'm using kernel 2.6 ).  A file
> system search only found ivtv.ko ( in /lib/modules anyway, more in the
> source dir tree obviously ).
> 
> > 2. Any chance that box has ivtv and related modules compiled directly
> > into the kernel?  (is that even possible?)
> >
> > -brendan
> 
> I didn't compile this kernel, so I can't see how it would be in there.
> 
> While looking through ivtv-driver.c, it looks like the "== START"/"==
> END" lines should be output but I can't find them.  I didn't have any
> errors during 'make' or 'make install'.
> 
> -Tim
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> ivtv-devel mailing list
> ivtv-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ivtv-devel
>


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to