In fact I did follow the below steps ,It did work .
Before mailing I checked it .
We know that make mrproper cleans everything .
I did the same - just to make sure I moved the /boot/config-*** files away .Then did a make oldconfig . It never asked me a question .Acoording to the standard kernel doc what you said is correct .I wonder why did it work for me then. Where did it pick all the options from .
why did it work??
The reason for doing bzImage is once in a while compilation failed for "make modules" if I did not do the bzImage , In the initial process of bzImage I assume it creates some dependancy files , we dont need to go through the entire process of bzImage.
-------------------------------
Surya Prabhakar N
Wipro Technologies - UK.
-------------------------------
-----Original Message-----
From: Jan Hudec on behalf of Jan Hudec
Sent: Mon 17/01/2005 22:12
To: Surya Prabhakar (WT01 - UTILITIES)
Cc: nguyenhoangchung@xxxxxxxxxxxxxxxx; kernelnewbies@xxxxxxxxxxxx
Subject: Re: how to recover the kernel configuration in a running kernel without /usr/src
On Mon, Jan 17, 2005 at 14:45:38 +0530, surya.prabhakar@xxxxxxxxx wrote:
> You distribution should be normally providing a file in you boot directory with the config options
> like /boot/config-xxx
>
> IF it is not there also no problem try these below steps
>
> Install kernel source closest to your source from kernel.org(check uname -r)
> untar it in /usr/src
> Match the Version name in the Makefile to the exact name of your current running kernel .
> enter directory ,
> make mrproper
> make oldconfig
This combo is bound to be useless! make mrproper removes .config, even
if there have been one. Then make oldconfig asks all questions that are
not answered in .config. There are none (.config was removed, and in
fact it never existed), so it will ask all of them. In an ugly
command-line interface.
> make menuconfig (and select the option for the module you wanted and save)
Now, all questions were already asked. Only useful if you want to fix
something/
> make dep clean bzImage modules ( dont do modules_install - it will overwrite)
Why are you doing bzImage, when you are not going to use it???
> latter do a find for your module in the kernel source and copy it to approriate path (just in case try insmoding it first)
> in /lib/modules/<current-kernel-path>/kernel/drivers/<your mod dir> or where ever
> then do a depmod -ae
> update your modules.conf
I'd doubt this would work. Under some circumstances, like if the kernel
had CONFIG_MODVERSIONS, it is bound not to.
> that's all .
> enjoy.....
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@xxxxxx>
