LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 04-12-2006, 01:59 AM   #1
prozac
Member
 
Registered: Oct 2005
Location: Australia
Distribution: slackware 12.1
Posts: 753

Rep: Reputation: 32
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?
 
Old 04-12-2006, 06:19 AM   #2
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
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.
 
Old 04-12-2006, 07:27 AM   #3
vkmgeek
Member
 
Registered: Feb 2006
Location: Ahmedabad
Distribution: rhel5
Posts: 185
Blog Entries: 2

Rep: Reputation: 31
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 anyway...so making a very specific kernel image is in fact a strong point for Linux masters...
 
Old 04-13-2006, 01:06 AM   #4
prozac
Member
 
Registered: Oct 2005
Location: Australia
Distribution: slackware 12.1
Posts: 753

Original Poster
Rep: Reputation: 32
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 system.map 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 bzimage.it works but is this the right way. meanwhile any relative suggestions would be nice to keep in mind if you guys may so please..

Last edited by prozac; 04-13-2006 at 01:08 AM.
 
Old 04-13-2006, 03:52 AM   #5
SlackerDex
Member
 
Registered: Mar 2006
Location: localdomain.localhost
Distribution: Arch-0.7.2, Slack-11.0
Posts: 56

Rep: Reputation: 15
Quote:
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?
-http://www.kernel.org/pub/linux/kern.../rusty/modules
Just a thought.

Last edited by SlackerDex; 04-13-2006 at 04:05 AM.
 
Old 04-13-2006, 04:31 AM   #6
binay_gupta
LQ Newbie
 
Registered: Sep 2004
Location: indore
Distribution: red hat
Posts: 5

Rep: Reputation: 0
wen i boot the new compiled kernel i get the error saying
"Kernel Panic- no Init found"
need Help
 
Old 04-13-2006, 05:23 AM   #7
vishamr2000
Member
 
Registered: Aug 2004
Posts: 210

Rep: Reputation: 31
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,
Visham
 
Old 04-13-2006, 06:00 AM   #8
vishamr2000
Member
 
Registered: Aug 2004
Posts: 210

Rep: Reputation: 31
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
 
Old 04-13-2006, 06:17 AM   #9
prozac
Member
 
Registered: Oct 2005
Location: Australia
Distribution: slackware 12.1
Posts: 753

Original Poster
Rep: Reputation: 32
have fun guys. from tommorow its a NEW YEAR here. I will be gone for sometime so. he he
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Increasing Kernel stack size to 8k without recompiling the Kernel deathman Linux - Software 2 04-08-2006 04:39 AM
kernel: No module symbols loaded - kernel modules not enabled. Qucho Debian 9 05-26-2004 02:50 AM
can i compile just one kernel module whithout recompiling the whole kernel? edman007 Linux - Software 3 02-17-2004 03:05 PM
How to keep modules/drivers across kernel recompiles and kernel versions? Pisces107 Linux - General 5 01-21-2004 08:29 PM
recompiling kernel goes fine, problem with make modules fritex Linux - Software 4 11-07-2002 10:17 PM


All times are GMT -5. The time now is 09:14 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration