-   Linux - General (
-   -   kernel modules when recompiling kernel (

prozac 04-12-2006 02:59 AM

kernel modules when recompiling kernel
I have just compiled myself a new linux-2.6.5 kernel. I am using slackware-10.2 with the default bare.i kernel previously. While in 'make menuconfig', i saw so many modules and parameters to check in/out before making the kernel. Since, I used my old config file there were so many options checked already and I was kinda thinking "I donot need all these modules!". Maybe the default kernel shipped with my OS has checked all these just to make sure this kernel could run in most of the machines out there. But since I am not reusing this kernel and want to optimize and configure it just to suit my own needs I did my best to select only those options I thought I would need. There were so many that I didn't even recognized like the I20s and so many others. Whats the issue here. The kernel I compiled worked like a charm except for network ( I think I missed out something there). The new kernel works fine right now but I can't say if this is the best for me. Does compiling with only the exact things I will need make my kernel faster? Or, Is it a bad idea? The HOW2S only talk about the process and not about the specific modules or their use. Where am i going?

Alien_Hominid 04-12-2006 07:19 AM

It's good thing to compile things which you only need. The common rule is to compile essential things into the kernel (like filesystem support) while other required things to build as modules. Unnecessary things should not be compiled at all unless you plan to add new hardware.

vkmgeek 04-12-2006 08:27 AM

One can always know that what option is doing what...
When u r doin make menu config....It has option "?"..wenever u press it, it will give u guide lines so that u can decide whether it is required it or not in your case...
And if u r working with embedded device, u have to strive for space...and u have to save it in making a very specific kernel image is in fact a strong point for Linux masters...

prozac 04-13-2006 02:06 AM

i feel good to hear that i am in the right path. i have compiled the 2.6.5 kernel 4 times since yesterday and each one of them has been different than others. i guess i am just practicing. i think if i only don't mess up my old kernel images and the and config file and can keep my lilo untangeable, i can keep on compiling new ones till i get what i want. i have space in my harddrive, lots of time in hand and a great system to work upon. one thing though, i cannot make my network card work on any of the 4 kernels. i am not sure why. i choose the correct option in the network setup menu and still the problem. this nic works fine under my default 2.4.31 but under 2.6.5 it just doesn't works. it doesnot even detects the nic. i am trying few more times with the kernel to make it work, also now the 'make mproper' returns "make:*** no rule to blah blah.." and ditto with 'make bzimage. i think i messed up my kernel source tree or something like that. now i am just doing straight'make menuconfig' and 'make' to make the works but is this the right way. meanwhile any relative suggestions would be nice to keep in mind if you guys may so please..

SlackerDex 04-13-2006 04:52 AM


i choose the correct option in the network setup menu and still the problem. this nic works fine under my default 2.4.31 but under 2.6.5 it just doesn't works.
Perhaps taking a look at your 2.4.31 configuration file might help?
-cd /usr/src/linux-2.4.31 ; make xconfig
Or updating packages such as module-init-tools, mkinitrd?
Just a thought.

binay_gupta 04-13-2006 05:31 AM

wen i boot the new compiled kernel i get the error saying
"Kernel Panic- no Init found"
need Help

vishamr2000 04-13-2006 06:23 AM

Two main reasons for the "kernel panic" msg to appear:

1) EXT3 FS was not compiled statically in the new kernel, but rather as a module. You can correct that by changing the CONFIG_EXT_FS=m entry to CONFIG_EXT_FS=y

2) Correct parameters need to be passed to root and not the LABEL. So instead of having root=/LABEL/1 (sth like this), change it to root=/dev/hda* where the * is the partition number on which your linux OS is running. YOu can get the info by running the 'df' command and choose the hda entry for root i.e "/"

Hope it helps..

Warm regards,

vishamr2000 04-13-2006 07:00 AM

It should be "CONFIG_EXT3_FS=m to CONFIG_EXT3_FS=y in the .config file of the new kernel folder"

Sorry for the mistake

prozac 04-13-2006 07:17 AM

have fun guys. from tommorow its a NEW YEAR here. I will be gone for sometime so. he he ;)

All times are GMT -5. The time now is 02:46 PM.