hello

i was trying to upgrade the kernel from 2.6.9 to 2.6.20.4 but when we go through menuconfig it gives me error like these:

/boot/config-2.6.9-42.ELsmp:590:warning: trying to assign nonexistent symbol SCSI_SATA_ULI
/boot/config-2.6.9-42.ELsmp:591:warning: trying to assign nonexistent symbol SCSI_SATA_VIA
/boot/config-2.6.9-42.ELsmp:592:warning: trying to assign nonexistent symbol SCSI_SATA_VITESSE
/boot/config-2.6.9-42.ELsmp:593:warning: trying to assign nonexistent symbol SCSI_SATA_INTEL_COMBINED
/boot/config-2.6.9-42.ELsmp:607:warning: trying to assign nonexistent symbol SCSI_ISCSI_SFNET
/boot/config-2.6.9-42.ELsmp:617:warning: trying to assign nonexistent symbol SCSI_SYM53C8XX_IOMAPPED


thanks in advance

You forgot to mention the steps leading up to this point, it does look like you made a mistake or forgot to do something.

1. It is not possible to use such an old kernel config file (from the 2.6.9 kernel) and apply it to the current 2.6.20.4 kernel source.

2. It sounds like you did not use 'make oldconfig' first.

3. Yes you will get errors like your posting, simply because this SATA/PATA SCSI fairly new and the differences between the kernel layout changes from 2.6.9 to 2.6.20

'make oldconfig' won't work, kernel config tree has been changed since 2.6.9.

we did use the 'make oldconfig'. i have no idea about what im supposed to do.

do you know what's wrong with the kernel that is giving these errors?

Since this is for a server I'd recommend removing your .config file, starting with 'make allnoconfig' and enabling only things you need. This is the cleanest way to build a stable kernel. At least this is what I'd do.

Edit: And read the README file in your kernel source directory.

Another option might be to run make oldconfig, hold the enter key down to accept all the defaults (sometimes the defaults are right), ignore the errors, and then run make menuconfig to tidy it up for your installation. I believe that the config that comes with an installation has everything enabled that might likely be on *someone's* computer. For the most part, configuring is turning stuff off that you don't want - though not always.

Added:
"silentoldconfig" and "defconfig" are also options. See the README file like Emerson suggests.

1 - make distclean
2 - make clean
3 - make mrproper
4 - make oldconfig -> then keep pressing Enter
5 - make
6 - make modules
7 - make modules_install
8 - make install
9 - lilo -R 2.6.20.4
10 - shutdown -r now


these are what i did. but after uname -a it's still 2.6.9-42.0.10.ELsmp

any other options? i did all the steps said on my last post but still 2.6.9

I don't see any errors, I only see warnings here. They should not be fatal. This is normal, options have been removed.

You only need to run 'make clean' or 'make mrproper' not both.

Red Hat (and the clones) use grub as the default bootloader not lilo, but in either case one needs to select the new kernel to boot with.

Why do you think you need the vanilla 2.6.20.4 kernel?? Red Hat typically backports many security and other important fixes into the kernels they supply from the upstream source.

Please read: http://www.kernel.org/pub/linux/kern...kn_pdf.tar.bz2
Please see: http://wiki.centos.org/HowTos/Custom_Kernel

how we can make lilo as the default boot loader ?

Hope it doesn't seem like I deserted you! Unfortunately, I use grub and debian, so I can't help you with adding a new kernel to lilo.

If it is not already install then first install the lilo rpm package, then read: man lilo

Usually it something like typing; lilo -v

FYI: The last command {make install) when building a new kernel automatically places the files needed to boot the new kernel and updates either grub or lilo whichever is the default bootloader.

sorry, i didn't understand u at my previous post !
I've installed lilo on the server and the new kernel has been added to lilo.conf !

here's my lilo information :

Reading boot sector from /dev/sda
Merging with /boot/boot.b
Mapping message file /boot/message
Boot image: /boot/vmlinuz-2.6.20.4
Mapping RAM disk /boot/initrd-2.6.20.4.img
Added 2.6.20.4
Boot image: /boot/vmlinuz-2.6.9-42.0.10.ELsmp
Mapping RAM disk /boot/initrd-2.6.9-42.0.10.ELsmp.img
Added 2.6.9-42.0.10.E *

as you see 2.6.20.4 is installed !
meanwhile i've set panic_timeout on 5 seconds in kernel/panic.c, so if it got in trouble lilo should run the default kernel !
since i'm working on a remote server i can't see what's going on and kernel panic status !

it was necessary to say these at my first post, pardon.

So what's the problem? Is it just that the 2.6.20.4 kernel isn't the default kernel, and since you're booting remotely you can't get it to run?