New Kernel install ?

[brunix]

I have compiled a new kernel (2.4.22) to be used on my nvidia all in one board. I have slack 9.0 with 2.4.20 working on it now.

I compiled the kernel in /usr/src/linux-2.4.22 and it made 2 files,[b]System.map, vmlinux [\b] I cp /boot /boot2422 and cp'ed System.map and vmlinus to /boot2422. Edit lilo.conf to add
image = /boot2422/vmlinuz
root = /dev/dha2
label = SlackWare2.4.22
read-only
and ran lilo

now when I boot to 2.4.22 I still get a welcome to linux 2.4.20 I think it should be 2.4.22 Right?

In the /boot2422 I copied from /boot I used the same config. I am thinking this is where my problem is but I can't find a config for 2.4.22

every how to kernel I read seems different from what I see on my PC. Does someone see my error?

[krohnjw]

use uname to get the name of the kernel, see if you are actually booting the correct kernel. The config wouldnt do that.
you should have copied vmlinux and System.map to the new folder, and then bzImage as vmlinuz.

[IQB]

You need to start over.

cd to /boot and rename the files vmlinuz and Syste.map to vmliuz.old and System.map.old.

There should be a stanza in lilo.conf that looks like this.

image = vmliuz
root = /dev/hdax (x being the / partition)
label = linux
read-only

Add a stanza that looks like this.

image = vmlinuz.old
root = /dev/hdax
label = linux.old
read-only

Save the file and exit the editor.

There should be a symlink in /usr/src for the current kernel called Linux. Rename that link Linux.old.

Unpack the kernel source and it will automatically build a new directory in /usr/src called Linux-2.4.22.

Make a new symlink to the new directory with this ln -s /usr/src/linux-2.4.22 /usr/src/linux.

[b]cd to /usr/src/linux

do make mrproper && make clean && make menuconfig && make dep && make bzImage.

Get some Coffee.


Once the compile is done, do make modules followed by make modules_install

Now, copy the new kernel image to /boot with this.
cp arch/i386/boot/bzImage /boot/vmlinuz Copy the System.map file with cp System.map /boot. Copy .config to /boot with cp .config /boot/config

Re-install LILO with /sbin/lilo -v and reboot.

LILO should come up with a menu and give you a choice of which version of the kernel you'd like to boot, either linux or linux.old. linux is using the new kernel and linux.old uses the old.

[brunix]

Thanks for the help I had failed to follow pbharris's directions to the letter and did not change bzImage to vmlinuz just as IQB stated. I think I have got the kernel to boot now because I am now getting a kernel panic in monting the root fs. It looks as though I will be remaking my kernel to find what I need to fix.

This is getting to be fun. now all I need to do is learn to read and follow directions

One note. a install of slackware from CD does not make a dir at /usr/src/linux

[IQB]

One note. a install of slackware from CD does not make a dir at /usr/src/linux

No it doesn't. You make the linux directory under /usr/src when you create the symlink to the new kernel directory. The install should have created one for the old kernel. That's why you rename it.

[brunix]

I have managed to compile kernels 2.4.20 & 2.4.22, both of which have a kernel panic on startup. I have done this several time, with both kernels. I am trying to slim down but seem to becoming anorexic. My latest panic seem to be No Socket Drivers Loaded I know the process but would like to get one to load.

Would the config of 2.4.20 boot with no changes. I have been looking at config files

I need Duron CPU, No SMP, I810 for sound, Nvidia onbpoard chip, TCP/IP, USB but not nessery. That doesn't seem like so much. It is all in the config choses but won't boot

[IQB]

Would the config of 2.4.20 boot with no changes.

All of the stock kernels should boot with the stock config. Some of your peripherals might not work as intended but you ought to be able to get a minimal system booted.

Go back a check lilo.conf and double check the boot= statement to make sure it's pointing to the right hard drive, and the root= statement to make sure it points to the right partition.

Don't forget to re-run lilo everytime you make a change.