Error while compiling the kernel

[pinga123]

Downloaded the stable kernel 2.6.36.4 from kernel.org/ (Current Kernel:2.6.18-92.el5)

However i have extracted the source code .
ran
make mrproper
copied the old configuration file and selected it by using make menuconfig .

However after selecting it and clicking ok i m getting following error.

.config:656:warning: symbol value 'm' invalid for IP_DCCP_CCID3
.config:657:warning: symbol value 'm' invalid for IP_DCCP_TFRC_LIB
#config:1353:warning: symbol value 'm' invalid for FIXED_PHY
# configuration written to .config 'm' invalid for IWL4965
#config:1619:warning: symbol value 'm' invalid for ISDN
.config:2721:warning: symbol value 'm' invalid for RTC_INTF_SYSFS
.config:2722:warning: symbol value 'm' invalid for RTC_INTF_PROC
*** End of Linux kernel configuration. invalid for RTC_INTF_DEV
*** Execute 'make' to build the kernel or try 'make help'._LOCKING_DLM

I m not sure why this error messages poped up.

Shall i ignore them and do something about it?

[MikeTbob]

I think the problem is stemming from the fact that you used a .config file from 2.6.18 to 2.6.36, that's too big of a jump for using an old .config file. You might have better luck just starting the kernel build from scratch.
From the Gentoo howtos:

10. Advanced: Using your old kernel .config to configure a new one

It is sometimes possible to save time by re-using the configuration file from your old kernel when configuring the new one. Note that this is generally unsafe -- too many changes between every kernel release for this to be a reliable upgrade path.

The only situation where this is appropriate is when upgrading from one Gentoo kernel revision to another. For example, the changes made between gentoo-sources-2.6.9-r1 and gentoo-sources-2.6.9-r2 will be very small, so it is usually OK to use the following method. However, it is not appropriate to use it in the example used throughout this document: upgrading from 2.6.8 to 2.6.9. Too many changes between the official releases, and the method described below does not display enough context to the user, often resulting in the user running into problems because they disabled options that they really didn't want to.

[pinga123]

I think the problem is stemming from the fact that you used a .config file from 2.6.18 to 2.6.36, that's too big of a jump for using an old .config file. You might have better luck just starting the kernel build from scratch.
From the Gentoo howtos:

thats seems logical However it also makes all old kernel upgradation task very complex.

If building it from old configuration file is considered to be unsafe which method should i use for the up gradation.

BTW i was thinking it to upgrade to new 3.0 version

[MikeTbob]

The old fashioned way is the best way. Just browse the menuconfig options and remove things you don't need and add the things you do. I like to do it in several sessions so I don't get too careless.

[pinga123]

The old fashioned way is the best way. Just browse the menuconfig options and remove things you don't need and add the things you do. I like to do it in several sessions so I don't get too careless.

I thought the old fashioned and safest way is to first build it using old kernel config file in this way you are atleast sure that you will be able to retain the old configuration later if the build is successful then go for adding new feature of new kernel.

Correct me if i m wrong.

[atreyu]

i always had probs using make mrproper...

here's what I always do, which works for me:

wget -O /tmp/linux-2.6.whatev.tar.gz http://kernel.org/kernel-2.6.whatev.tar.gz
tar -C /usr/src/kernels/ -zxf /tmp/linux-2.6.whatev.tar.gz
mkdir -p /usr/src/kernels/build-2.6.whatev
cp /boot/config-`uname -r` /usr/src/kernels/build-2.6.whatev/.config
cd /usr/src/kernels/linux-2.6.whatev
make O=../build-2.6.whatev/ oldconfig
make O=../build-2.6.whatev/ menuconfig
make O=../build-2.6.whatev/ -j5
make O=../build-2.6.whatev/ modules_install install

hth

[pinga123]

Did exactly you have mentioned above but after doing oldconfig it asks 1000's of questions.
I choose to stay with default by pressing enter everytime.

One more time i hit with an error will post the output screen shot.
lh4.googleusercontent.com/-28JhiUsq8Lo/Te8VMNLAQ2I/AAAAAAAAAN4/Gev8wXsXc8w/s640/ExactKernelError2.jpg
I m running the linux machine with Sun virtual box will this make any difference compiling the kernel as the error says it is unable to find filesystem /dev/root.

[MikeTbob]

The reason it is asking you 1000's of questions is because it failed and it completely started from the beginning.

[pinga123]

The reason it is asking you 1000's of questions is because it failed and it completely started from the beginning.

What should i do ? I think i will never able to see the new Kernel update .
There must be a way out.

[MikeTbob]

I think the only way is to do like I said and start from the beginning. If you really in a hurry, just select the options that you need and leave all the rest.