If lsmod is to see all the modules that are loaded at the instance, and during menuconfig, we can choose which to be compiled into the kernel(y) or as modules(m).

.config files is only created when make menuconfig or similar is run and saved.

If there is TOTALLY NO existing .config file from the initial installation, how do i generate a .config file based on the current or initial installation?

This will be a BIG help if possible.
Best to be done in commands, not through GUI
thanks in advance.

If you are lucky then you'll find it in /proc/config.gz.

There is often a config-<version>.gz file saved in /boot that matches an installed pre-configured and compiled kernel. Also check if /proc/config.gz exists.

This psuedo file is generated by the kernel if the kernel option to generate it was enabled in a 2.6 kernel. Running "make oldconfig" will use this file to create a new .config file based on the current options and prompt you for any new options in a newer kernel source. This is a good baseline to use before running "make xconfig" where you can tweak it as desired.

ooohhhhhh.....

thats a something i have never seen b4 ...
thanks a million. i will try all the solution out!!!

Which option, how and where do i choose or activate this option ?

If you don't have a /proc/config.gz file, then the kernel wasn't compiled with that option. It is something that I think you would need to recompile the kernel to enable. Also make sure that you have a 2.6 kernel and not a 2.4 kernel.

On my kernel, I think these options are:
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y

Dear khaos83, whatever you build from sources, always read README file.

You mean, you're suppose to actually read those files called README?

Yes, sir! There is no other way to find out why they call them README.

Yet another option to get it directly from the bzimage, again if it's compiled in the kernel: On my system
<code>
cd /usr/src/linux

./scripts/extract-ikconfig /boot/vmlinuz-huge-2.6.21.5
</code>

I bet more people would read a DONTREADME file then a README file.

Sir,
While you all are at the README , I have been going through the documentation for the last few days and am lost in the maze of files! There are a number of xxxxxx.config files - may I use xxxxxx686.config to start with?(The source rpm was downloaded from the fedora update site)

There are a number of patches also - I sincerely hope that I do not need them!

I have installed the sources properly with the last command being mrproper in the README (I hope!). I seem to have all the tools with Fedora7 and kernel-2.6.23.8 installed, I have dared to run 'make menuconfig' and the shell had a lot to tell, when I fled without saving. It was using the configuration from /boot and had to report a lot of things (config options) that were not available with the 2.6.23.12 kernel sources. May I Ignore those options and continue further and save the .config .

With regards,

P.S.
I seemed to have all the necessary 'system requirements' as detailed in 'linux_sources/Documentation/Changes' but was not sure - the great utility script in 'linux_sources/scripts/ver_linux' has now made me confident that I have everything required. The inclusion of a reference to this script in the 'Software Requirements' section of the "README" would be a great help to beginners like me.