insmod
 

when i go to insmod stv680( the driver for a digital cam), i get
/lib/modules/2.4.18/kernel/drivers/usb/stv680.o: unresolved symbol video_unregister_device_Rsmp_55ac2b50

/lib/modules/2.4.18/kernel/drivers/usb/stv680.o: unresolved symbol
video_register_device_Rsmp_924aa3b6

/lib/modules/2.4.18/kernel/drivers/usb/stv680.0: unresolved symbol
video_proc_entry_Rsmp_bbc51cf6

similar lines come up for other drivers while dabusb.o loaded ok
what are these "symbol"s and what's the message here?
lsmod shows only lp
is there a list somewhere of all compiled modules loaded or not?
storm's comin up so i'll post this now case i go down - any help appreciated

I had this problem with the newest drivers for my modem and had to use older 1's

Thats about the only help I can give u on this subject, u could type "man insmod" and see what it says in there about unresolved symbols. otherwise u have to change some code to match the new symbols

The modules ready for use are in /lib/modules/.

To see the modules loaded run /sbin/lsmod.

Finally, try using the modprobe command instead of insmod to load modules, it's the preferred way of loading kernel modules.

modprobe was my first effort-i switched to insmod to see if i would gain any options. i have noticed that two of the unresolved symbol notices are identical for several of the unworkable modules i have tried to load,leading me to wonder if i have sommehow compiled them for the wrong kernel, or as Phonics3k has suggested, i need older drivers. will press on. thanks, everyone for taking some time out for this.

Has this happened after you installed a newer kernel?

with the modules for my modem I had 2 modules
pctel.o
ptserial.o

If I typed "insmod ptserial" first then I would get unresolved symbols, but if I typed "insmod pctel" first then I wouldnt get the unresolved symbols error

order does seem to matter in that i have to enable certain usb supports to open the port to the camera, but then both the possible drivers, stv680 and ov511 gave me the same unresolved symbols. and yes, this all happened after installing 5.4.18 after a botched 5.4.18 following an original cd installed 2.2.19. the second 5.4.18 was botched because i added a make install step not realizing that lilo.conf would be rewritten thus moving the Sys.map and linuz to Sys.map.old and linuz.old(which were booting 2.2.19 in my manually edited lilo.cof from the first attempt at 2.4.18). at that point, booting 2.4.18 gave me an immediate crc error-system halted- while booting 2.2.19(from the lilo screen) gave me 2.4.18 whch seemed to be working great- however-aside from the general mess of things-i can believe that the modules may or may not have suffered from all this-they were all compiled for the same kernel(2.4.18) but from one menuconfig to the next, i changed some things(mostly to maximize modularization-minimize kernel size-had to bzImage anyway)
am back to 2.2.19 after a reinstall-had /home on its own partition so nothing lost there-did however have some errors in auto full install which i've not had before- had to restart setup to get /dev/hda5 mounted as/home and had to skip a couple of files because of compressed data problem-went back and installed them individually-so there are enough anomalies here to wonder that i am not just typing to a blank screen-haven't mentioned the several momentary power outages this week, always in the middle of something-a UPS will be in place as soon as funding is available- windows2000(a dual boot setup here) has become corrupted simultaneously with this, but i wasaiming at trashing that with the inauguration of gphoto, gtkam and xine(all up and running on 2nd 2.4.5)
so, will continue on and will continue to appreciate all the help you guys will offer. more later

when you installed the new kernel, make bzImage, did you run:

make modules

then:

make modules_install

???

no, i will do that on the next attempt after i sort out the rest-i've dumped win2000 from /dev/hda1 and when i went to boot the mandrake install.cd, i got the exact kernel panic message i got after my first 2.4.18 install-so maybe i will rearrange the partitioning and put slack on /hda1-lilo is on the mbr -is that wiped by a format of /hda1? thanks much.

remember to run:

depmod -a

as well after all that.

will do and thanks

what does the depmod -a do?

my reading of man depmod indicates that depmod -a will search for modules stored in any directories in /etc/modules.conf as it searches deps for its object module-i assume one could then use this file as a place to get your ducks in a row, so to speak. but, as always, i welcome enlightenment and caution that i offer only supposition here.