Bill Eldridge wrote: > Peter Silva wrote: > >> I've been doing that for 2.4.18 and 2.4.19, and the kernel >> builds correctly, although the modules end up in a funny place. >> I would expect them to go into >> /lib/modules/2.4.19/kernel/drivers/media/video >> but they actually get put into /lib/modules/2.4.19/v4l2. Strange, >> but depmod >> finds them OK, and modprobe works. >> >> unfortunately, the machine then hangs solid. well the kernel build >> is clean :-) > > > While depmod "finds them", it's often finding > the wrong ones, which can cause your machine > to hang solid. I noticed this when I was sure > I'd installed v4l2 drivers but only one program > could access the device - doh! - it was loading > the older v4l stuff. Delete the duplicates > in /lib/modules/xxx/kernel/drivers/media/video
did that, stuck printk's in the good ones too. _______________________________________________ Video4linux-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/video4linux-list
