On Thu, 14 Dec 2000, David Hananel wrote:
> I have RedHat 6.2.
> When I recompiled my kernel from 2.2.14-50 to 2.2.17,
just for the record - is this 2.2.17 kernel taken from redhat's site (and
is a modified redhat kernel) or from kernel.org or one of its mirrors)?
redhat has a tendency to break their soruces annoyingly.
> I recompiled also the
> modules, and I had some errors when I recompiled the modules, and now,
> everytime I start linux, I get the messages:
>
> "depmod: *** unresolved simboles in /lib/modules.....
> depmod: *** unresolved simboles in /lib/modules.....
> depmod: *** unresolved simboles in /lib/modules....."
>
> With lot's of unresolved simboles in files' messages...
do these messages refer to modules that you have compiled, or modules that
were left from a previous kernel installation?
> What is it?
it means that you have conflicting modes of kernel compilation, or modules
of one kernel versin used against another kernel version.
when you compile a kernel, you can choose to copile it with versioning
support, or without it. this method affects the names of symbols used for
all functions and variabels that the kernel exports for the usage of
kernel modules. with kernel versining, 'printk' turns into something like
'printk_R1b7d4074'. the hex number at the end is a checksum over printk's
function prototype (i.e. return value type and parameter types). this way,
if you try to load a module into a kernel whose printk's function
prototype has changed, you'll get an 'unresolved symbol error' instead of
a potential kernel crash.
> Can it be related to the Power Off problem?
might be, if part of the APM support is inside modules that couldn't have
been loaded by the kernel.
> Yes, I made "make modules" and "make modules_install"... And the errors were
> when I made "make modules".
ah. here we come to the question of which kernel sources source(...) you
used to get the kernel sources from. on redhat 6.2, i found that i must
disable kernel symbols versioning support in order to compile a kernel
that can actually load its modules. this, only if using kernel sources
supplied as part of redhat 6.2 . and this is not the first time i
encounter this problem...
conclusion: make sure you get kernel sources from kernel.org (or its
mirrors), and not from redhat's site or redhats install CD. then compile
everything afresh. note that you might need to recompile the modules after
rebooting with the new kernel version, due to the odd way in which kernel
versining info is acquired during compilation time.
hope this helps,
--
guy
"For world domination - press 1,
or dial 0, and please hold, for the creator." -- nob o. dy
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
