Can't compile 2.4-series kernels after trying to compile 2.5

gcostanz

I tried to compile the 2.5-65 kernel without success. I installed module-init-tools.

Later, after having problems with 2.5.65 I unmerged the development kernel and module-init-tools. I guess this was a mistake, because I now don't seem to have /sbin/depmod anymore. My old kernel (2.4-19) still boot's, but all of my modules are missing or won't load.

So, I figured this was a good time to install the latest stable module anyway. But when I try to compile 2.4-20 I end with an error:

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

Make sure you have a copy of modutils installed

emerge modutils

gcostanz · Posted: Sun Mar 23, 2003 5:30 pm Post subject:

Thanks. I rebuilt modutils and I now have a working 2.4.-20 kernel. But I still have a problem.

I compiled the kernel with soundcard support as a module for use with ALSA. I then re-emerged alsa-driver and compiled the sound.o kernel module without problems. But when I boot the new kernel my sound modules do not load, and generates errors like:

[code]
/lib/modules/2.4.20-gentoo-r2/kernel/drivers/sound/soundcore.o: unresolved symbol kfree
/lib/modules/2.4.20-gentoo-r2/kernel/drivers/sound/soundcore.o: unresolved symbol sprintf
etc...
[\code]

There is a soundcore.o module in the proper directory.

Any ideas what may be causing this problem? The sound card worked fine under kernel 2.4-19

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

1) save your kernel's .config files. For every version. Always

2) re-compile your kernel and modules, but before you do that, type: make mrproper. This will clean out all remains of previous kernels.
My guess would be that that's the cause of your problem.

gcostanz · Posted: Sun Mar 23, 2003 10:19 pm Post subject:

Ok. I've switched back to 2.4.19 and re-emerged alsa-drivers and I now have a working system again. It's been a long day-- and I don't like stress on a Sunday. But I've learned a great deal about compiling new kernels, and I want to see this through to a success. Thanks again for you help.

Now, I did not do a make mrproper before I compiled either the 2.4-20 or the 2.5-65 kernels and I had problems with both. I will try again with 2.4-20 following the steps that you recommend. BTW, I was following the step-by-step instructions by IWBCMAN in another thread. The mrproper step was not included. Is this something that must be performed every time a kernel is compiled?

Before I do that, will mrproper prevent me from booting back to 2.4-19? And in particular, if I do need to fall back to the older kernel, will I have to emerge the alsa modules again?

Thanks again for you help...