Thanks for the advice Steve, I will give it a try.
-----Original Message-----
From: Steve Youngs [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 01, 1999 4:59 AM
To: Myers, Curtis
Cc: linux-newbie
Subject: Re: Unresolved symbol(s) after re-compile
Hey! Did you hear what Myers, Curtis was saying on Mar 31 ?
MC> I was running RedHat 5.2 kernel 2.0.36
MC> I downloaded 2.2.5 and untared in /usr/src/linux after renaming the old
one
MC> make xconfig and set the options I wanted
<snip>
MC> modified /etc/lilo.conf to add an option for new kernel
MC> ran lilo
MC> depmod -a 2.2.5 then returned Unresolved symbol(s) for everything I had
MC> setup as a module.
The answer here is quite simple. The 2.2.x kernels will not work
with the modutils that come with 2.0.x. You need modutils 2.1.121 (check
your version with insmod -V). Get that version of modutils and your
problem is gone :).
While your at it check /usr/src/linux/Documentation/Changes for
all the other things you'll need to upgrade to get your 2.2.x system
running properly.
Upgrading from 2.0.x to 2.2.x isn't as straight forward as getting
the kernel source and compiling it. A fair bit has changed in the new
kernels which means a lot of new utils and software and (as I'm
discovering) new ways of doing things.
Just a quick question...
MC> I have recently recompiled my kernel in an attempt to utilize APM the
MC> following occurred:
If this was your motivation for upgrading from 2.0.36 to 2.2.5
then why did you do it?? 2.0.36 has APM support in it.
Regards, Steve Youngs <[EMAIL PROTECTED]> ICQ: 34307457
����������������������������������������������������������
� __ �
�Isn't it good to know that / / __ ___ __ ____ __�
�There _IS_ an alternative! / /__ / // _ \/ // /\ \/ /�
� /____//_//_//_/\_,_/ /_/\_\�
����������������������������������������������������������
Windows Error: 002 - No error yet ...
