Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Linux - Kernel This forum is for all discussion relating to the Linux kernel.


  Search this Thread
Old 05-23-2009, 09:18 PM   #1
LQ Newbie
Registered: May 2009
Posts: 13

Rep: Reputation: 0
Detect what built-in kernel components (not modules) are actually being used?

Okay, I'm running my kernel as monolithic as I can make it-- no initrd, and only three modules (which refuse to compile directly into the kernel for some reason.) Sure, it's not as elegant, but it runs faster that way.

However, when I build stuff into the kernel, I have to err on the side of caution, and I probably have more stuff compiled into it than I need.

I know that lsmod will tell me what modules I'm using, but I need to know what built-in stuff is being used. My current workflow is:
  • Disable something in xconfig.
  • Compile kernel.
  • Reboot.
  • If I get a kernel panic, or sound/internet gets disabled, re-enable whatever I disabled.
  • Repeat from step one.
This trial-and error method is time-consuming, and I was wondering if there was a faster way.

I am using Debian Sid/Squeeze/Experimental, kernel 2.6.30-rc6-git6.
Old 05-24-2009, 06:18 AM   #2
Senior Member
Registered: Mar 2005
Location: Earth bound to Helios
Distribution: Custom
Posts: 2,524

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
See the content of /proc/config or /proc/config.gz file.
It has the settings used when during build.
Or if it's not available you have to see the .config file used for kernel build. .config file is present in the source code directory of the kernel.
Old 05-24-2009, 08:44 AM   #3
LQ Guru
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 8,629
Blog Entries: 4

Rep: Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001Reputation: 3001
I run a similar kernel, and I am frankly not in agreement that "it runs faster that way."

Now, "bumming code" is a legendary and noble enterprise ... ... but at this point, that's really all that you're doing.

When I built my kernel, I selected the options for the hardware that I am actually using on a machine, then added removable-device support, crypto-algorithms and so on as modules. I very carefully save the ".config" files so that they cannot get lost.

The machine, of course, "runs like a bandit," booting all the way to ready-to-use in about 40 seconds.


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 Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Determining Which Modules are needed for boot if all modules are built-in? LinuxGeek Linux - General 4 06-29-2007 11:25 AM
Kernel upgrade: built-in or modules ? sl4ckw4re Slackware 6 07-16-2006 12:22 PM
kernel: modules or built in? sh4d0w13 Linux - Newbie 1 10-31-2005 08:00 PM
new kernel modules linuxhippy Slackware 11 03-10-2005 04:54 PM
loadable modules vs built-in modules nuzzy Linux - Hardware 1 07-21-2003 05:16 PM > Forums > Linux Forums > Linux - Software > Linux - Kernel

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

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