Mandrake 10.0 custom kernel problem
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:
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?
Last edited by pestie; 09-19-2004 at 12:35 AM.