Depmod Unresolved symbols?

Forum: The Linux Kernel Hackers' Guide
Re: driver x_open,x_release work, x_ioctl,x_write don't (Carl Schwartz)
Date: Tue, 31 Mar 1998 22:50:12 GMT
From: Carl Schwartz <schwcarl@e-z.net>

Sorry, I forgot to click '?' on original message. One of my original problems that I just discovered is that I had put 'x.o' under /lib/modules/2.0.31/ 'char' instead of 'misc'. Relating 'modules' to 'drivers', I guess I had created the 'char' subdirectory which Modprobe apparently does not search. My remaining problem seems to be that Depmod -a does not resolve the symbols, but does go ahead and put 'x' in the modules.dep. I need to determine what, if not Depmod, updates the symbol table. The symbols returned by depmod -e are all found in ksyms and some of them work just fine in the 'cleanup', 'init' and 'open' functions which work OK. I haven't found the *.c source to help in figuring out how things fit together for the module utilities, just the *.o files.