G'day, and me again :}

I d/led a kernel 2.4.18 (tgz) and am now wondering
how to make that work with my slackware. Yes, I've
rebuilt Kernels before, no, I'm not that new ...

When I run make menuconfig and make all my selections
for the newer kernel, then run my make dep and make
bzImage I am presented with make config instead of
just getting the kernel compiled, and after the second
(superfluous) configuration the compile ends with errors.

What have I done wrong? :) Do I need a special archive
that's suitable for Slack, which files in the archive from
kernel.org do I have to touch to make the make work on
Slack?

Cheers,
Tink

I dont know what you might have done, but i just downloaded the tar.gz, ran menuconfig. than the standered make dep clean bzimage........ it worked fine for me then.

sonikntails

yeap it sounds crazy . .

follow the details of README file . . .

It worked for me too..

make dep ; make clean ; make bzImage

Kernel 2.4.18 will work on even slack 7.1 the way to get it going is first to untar it. Then you copy the .config file from your old kernel directory to the new one.
#cp /usr/src/linux-2.4.5/.config /usr/src/linux-2.4.18

Then make menuconfig then make dep if you have to. Then make clean, make install, make modules, make modules_install.

Each step in the kernel compile is optional depending on what you have to do.

If you are trying to get new Nvidia drivers working you probably need make dep. If you haven't added anything but a new kernel option you don't really need make dep again. If you have just added a new module you don't need to recompile all the kernel or reboot you just need make modules, make modules_install.

You don't even have to compile your kernel as the root user or in /usr/src/linux you only need to run lilo, copy bzImage to vmlinuz, and make modules as root.

You can compile a kernel on one machine and copy it to another if you do it the right way.

Not to accuse of making one of the dinky errors, but this is indicative of one of the most common mistakes... did you remember to rm the symlink from linux to linux-2.2.19 in /usr/src before you un'tar'ed the 2.4.18 package? Otherwise you dumped all of the new source in with the old source and well... if your base kernel was 2.2.19, you can accidently create 2 configs... er, yeah its a mess.

Cheers,

Finegan

Hehe ... thanks, I not THAT daft

Actually Richards tip to copy the .config of the 2.4.5
kernel to the 2.4.18's directory solved the problem

Thanks Richard!

Cheers,
Tink