I'm compiling a custom 2.6.3.-16mdk kernel under Mandrake 10 and having a bit of a problem. I'm doing the usual procedure:

make menuconfig
make clean
make bzlilo
make modules
make modules_install

Problem is, when I boot the new kernel "uname -r" is returning 2.6.3-16mdk, not 2.6.3-16mdkcustom like it should despite the fact that I'm sure LILO is loading the correct (/vmlinuz) image. This means, of course, that modprobe is looking for modules in /lib/modules/linux-2.6.3-16mdk/ instead of /lib/modules/linux-2.6.3-16mdkcustom and the boot process basically explodes hideously as many important modules fail to load.

The top-level Makefile does, in fact, set EXTRAVERSION = -16mdkcustom, so I don't know what the bejesus is going on here. Is there something unique to Mandrake kernels I'm missing here?

hi there

i do not think there is anything new the kernels for manrake
for more info on compling kernel there one goood thread here
have a look

http://www.linuxquestions.org/questi...ghlight=Dr+Ozz

regards

I usually do:

make xconfig
make make bzImage
make modules
make modules_install

cp bzImage to /boot
edit lilo
and so forth...

And you might as well use a newer kernel... Either mdk or generic...

I'm on generic 2.6.9-rc2 with mdk 10, tho you need the latest k3b to run on this kernel.