On Friday 09 February 2001 05:42 am, Craig Hagerman wrote:
> I have compiled the new 2.4 kernel and everything seems to have gone
> OK, but I can't boot into it.
do you have modutils-2.4.2-1mdk ?
> Downloaded the source for kernel 2.4.1 to my /root directory
> extracted the tarball with> % tar -zxvf linux-2.4.1.tar.gz
When you re-compile you'll need to 'make mrproper' before 'make
xconfig' and edit the Makefile to at least uncomment the line
export INSTALL_PATH=/boot
> % make xconfig
> and then:
> % make dep
> % make clean
> % make bzImage
you didn't do a 'make install' here
> % make modules
> % make modules_install
it's much easier to just paste this line into a term and hit <Enter>
(the ampersands mean 'do the next step if the last step was successful')
make dep && make clean && make bzImage && make install && make modules
&& make modules_install
>
> then I moved and renamed both bzImage and System.map
> % mv /arch/i386/boot/bzImage /boot/vmlinuz-2.4.1
> % mv System.map /boot/System.map-2.4.1
> and finally deleted the existing symlinks for System.map and vmlinuz
> and made new ones linked to those new files:
> % rm System.map
> % rm vmlinuz
> % ln -s System.map-2.4.1
> % ls -s vmlinuz-2.4.1 vmlinuz
all that would be unnecessary. I usually clean up uneeded links
and files in /boot, after I get the new kernel to boot successfully.
> So far everything proceeded just fine with no complaints. I figured
> that the grub menu.lst just needed a bit of tweaking (to removed
> references to initrd that I don't need) and I would be good to go.
If you need/want ramdisk support, you do need a initrd if you want a
to be able to boot the kernel. 'man initrd' if so, after 'make
modules_install' the next step is
mkinitrd /boot/initrd-2.4.1.img 2.4.1
http://mandrakeuser.org/install/kupgrade3.html has info on editing
lilo/grub to boot the new kernel.
--
Tom Brinkman [EMAIL PROTECTED] Galveston Bay
