[lkml]   [2000]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: compiling 2.4.0-test10 kernel
>>>>> "KO" == Keith Owens <> writes:

KO> On Fri, 10 Nov 2000 11:23:29 -0500 (EST), "Georg Nikodym"
KO> <> wrote:
C> i've manged to successfully compile 2.4.0-test10 kernel. however,
C> upon startup there are some failed/error messages:
C> 1. finding module dependencies: depmod *** Unresolved symbols in
C> /lib/modules/2.4.0-test10/kernel/arch/i386/kernel/apm.o
>> There are two things you can do about this:
>> 1. Disable module versioning.
>> 2. Copy the file that's made during the kernel build to
>> /boot/

KO> has nothing, repeat nothing to do with depmod at
KO> startup. Yes, you can run depmod reading from a but
KO> that only makes sense before you boot the new kernel. Once you
KO> have booted your new kernel, depmod -a reads from kernel memory,
KO> not

OK. Makes sense. My first kicks at building and running a kernel had
these problems (with module loading) until I added the copying of to my installation procedure. I was led to this by
messages in /var/log/messages... Thanks for the additional pointers.

KO> Q. Why do I get unresolved symbols like foo__ver_foo in modules?

KO> A. If /proc/ksyms or the output from depmod -ae contains symbols
KO> like
KO> "foo__ver_foo" then you have been bitten by the broken Makefile
KO> code for symbol versioning. The only safe way to recover is save
KO> your config, delete everything, restore the config and recompile.

KO> mv .config .. make mrproper mv ../.config . make oldconfig make
KO> dep clean bzImage modules install, boot

OK, but I guess my question wasn't very clear. I have a kernel tree,
I add a printk to maestro.c and make modules. I cannot load the
module until I rebuild and reinstall everything. Is there a way to
avoid this headache, or, stated differently: What's the prescribed
way to be able to load, unload, build, test modules?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:0.084 / U:0.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site