Unresolved Symbols After Kernel Upgrade

Hello, I've been trying to upgrade RedHat 6.1 to the 2.2.14 kernel. I've dl'ed the kernel, and ran a make menuconfig which was based on a sample config file that came with the Redhat Source.

Did a make clean dep modules_modules_install bzImage , depmod -a 2.2.14

I copied overy System.map to /boot (Actually made System.map a symlink to System.map-2.2.14) and updated lilo.

The new Kernel boots, and even runs to a good degree, but I have about 50 modules that complain about unresolved symbols, including the MSDOS fs type module.

I'm running all this on a dual Pentium 3 500 , with only 1 CPU, 256 ram. I've tried compiling the kernel without SMP support, and with, but still these errors.

Does anyone know whats happening here?

Aaron McNeal
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It sounds like you might not have gotten all of the proper modules to recompile.  Verify that your config includes all the modules that are complaining of unresolved symbols.
It is common for distributions to pre-compile modules and
place these modules in the /lib/modules/`uname -r` tree.
If some of these modules are not enabled in your kernel a
depmod -a will result in some error messages.

The fix is to mv /lib/modules/`uname -r` to a backup (something like 'mv /lib/modules/`uname -r`  /lib/modules/`uname -r`-old' and 'make modules;make modules install' in /usr/src/linux.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I'm noticing the underscore character you used when stating the steps you followed.  Also, do the make clean before you do the configuration, not after.  I'm not sure what make clean does, but make mrproper will delete your .config file which holds the configuration.  For all I know, make clean might do the same.  Then the steps should be:

make dep
make bzImage
make modules
make modules_install

These can be combined into one line as:

make dep bzImage modules modules_install

Then, of course, copy the new bzImage into the /boot directory (or, depending on the distribution,) /, modify /etc/lilo.conf to add the new image and run /sbin/lilo.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.