Bryan Mayland wrote:

Some systems actually put conflicting modules in a /lib/modules/xxx/v4l or v4l2 directory, which we don't check for during `make install`. My Makefile-fu stinks beyond simple rules, or else I'd fix that. Just something to be aware of.

Well, whatever the problem was, I removed and re-installed my Mandrake 2.6 kernel and kernel source, and re-built the modules.

Installed them, removed the IVTV subfolder in my modules directory (the 2.0 modules included with the kernel) and ran depmod, followed by a "modprobe ivtv" and all is well, even under kernel 2.6.

Thanks for the assistance.

Brian K


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
ivtv-devel mailing list
ivtv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to