> > From: Gerd Knorr <kraxel@xxxxxxxxxxx> > > I got a fresh 2.4.18 kernel, patched it to 2.4.19-rc3, applied the > > v4l2-api-2.4.19-rc3.diff patch, > > Fine. > > > installed videodevX-20020330 from > > don't do that. Thanks very much for the tip. I started completely from scratch again, blew away my /lib/modules/2.4.19-rc3 directory, re-built and re-installed bttv 0.8.43, but now I get a bunch of unresolved symbols when I insmod bttv (I do an insmod video-buf beforehand). For example: /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol v4l2_video_std_confirm_Rd2bee5d5 /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol video_register_device_R37cae8d1 /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol video_unregister_device_R42e3830f /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol v4l2_video_std_tpf_R3c43d354 /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol video_usercopy_Reee71369 /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol v4l2_fill_ctrl_category_R89e3aafc /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol v4l2_masterclock_gettime_Ra44210f3 /lib/modules/2.4.19-rc3/v4l2/bttv.o: unresolved symbol v4l2_video_std_construct_R94eb59ae Now, one thing I'm not entirely clear on - when I was "make menuconfig"-ing my 2.4.19-rc3 kernel, I told it that yes I wanted v4l, but I didn't include any of the specific drivers such as bttv since I figured I was going to be compiling that separately anyway. I this wrong? Am I missing an obvious and important step? - Dave
