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.
Still not sure what the problem was, but re-booting with kernel 2.4 and rebuilding/re-installing ivtv has everything working just peachy!
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
