Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-12-2009, 02:54 PM   #1
LQ Newbie
Registered: Apr 2009
Posts: 16

Rep: Reputation: 0
Post significance of * and M in menuconfig

when we will use * and when we use M in the menuconfig..............
i tried like enabling in the drivers eeprom by using * but i am not able to see my device......
I changed to M and compiled i found it ............
Old 06-12-2009, 02:58 PM   #2
Registered: Jul 2007
Location: Scunthorpe, UK
Distribution: Ubuntu 8.10; Gentoo; Debian Lenny
Posts: 961

Rep: Reputation: 69
M means module; so you can load and unload. We generally make parts of the kernel modules for when the code for them is likely to be updated or upgraded by an outside developer and so could be on a different time scale to the kernel.

You ought to do some research before playing with the kernel if you're not sure
Old 06-12-2009, 04:13 PM   #3
Senior Member
Registered: Jul 2004
Distribution: Ubuntu 7.04
Posts: 1,991

Rep: Reputation: 76
* means that the code is compiled in, and statically available in the kernel all the time, while M means that at least some (usually all) of the code for that option resides on disk as a module.

Modules are often used in your distribution's default kernel, since they take up much less space in memory when not being used, while still allowing a good range of hardware to be supported. There are also advantages as you don't need to reboot the system to change any module settings (or even to change and reload the module code).

In general, if a module is compiled in then it will load faster than a module, and you may also save a few bytes of memory space (as you don't need to load the code to load the module).

I don't know why your driver wouldn't show when it was compiled in. It's possible that the new kernel wasn't installed properly, or even that the computer wasn't rebooted, or that there is some difference between the module and the compiled-in driver that prevented your device from being recognised. Without more information it's hard to tell.
Old 06-13-2009, 03:36 AM   #4
LQ Guru
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288
I recommend this free online book on the Linux kernel, it is quite detailed on the kernel compile process:
a good resource, I usually refer back to it myself.


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
significance of noeol hank43 Linux - General 1 04-14-2007 05:51 AM
What is the Significance of Distributions edwin11 Linux - Distributions 2 12-23-2005 12:10 PM
Significance of *BSD kool_kid *BSD 3 12-15-2005 05:04 PM
What is the significance of 256? Cyberian General 9 02-13-2005 03:41 AM
Significance of Upcoming 2.6.x Kernel...? TheOneAndOnlySM Linux - General 6 12-10-2003 08:03 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 01:26 PM.

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