📷 Image Suggestion

Insert a screenshot of a real terminal showing make menuconfig running — the blue ncurses UI with menu items visible. Caption: “The make menuconfig interface running on Linux 6.x — your control panel for the kernel”. Alt text: make menuconfig terminal interface Linux kernel configuration.

💡 Pro Tip: The / Search Key is Your Best Friend

Inside menuconfig, press / and type a CONFIG symbol like IKCONFIG. menuconfig instantly shows you the full menu path, the current value, and any dependencies. This works across all kernel versions — even when menu positions change between releases.

📷 Image Suggestion

Insert a screenshot of the General Setup submenu inside menuconfig, with “Kernel .config support” highlighted. Alt text: menuconfig General Setup Kernel .config support highlighted. Caption: “Navigating to Kernel .config support inside the General Setup submenu of make menuconfig”.

Step 1 — Go to the Kernel Source Directory

Navigate to the root of your Linux kernel source tree. This is wherever you extracted or cloned the kernel source.

cd /path/to/linux-source

Verify you are in the right place — you should see files like Makefile, Kconfig, and directories like arch/, drivers/, init/.

Step 2 — Create a Starting Config with localmodconfig

Rather than starting from a huge distribution config with thousands of options, use localmodconfig to create a lean starting point based on what your current system actually uses.

lsmod > /tmp/lsmod.now
make LSMOD=/tmp/lsmod.now localmodconfig

lsmod lists all kernel modules currently loaded. Piping that list into localmodconfig tells the build system: only enable the modules this machine is actually using. The result is a much smaller .config and much faster build times compared to a full distribution config.

Step 3 — Launch menuconfig

make menuconfig

This opens the ncurses-based full-screen menu in your terminal. It reads your current .config and displays all options. Use arrow keys to move, Enter to select or enter a submenu, Esc to go back, and Spacebar to toggle options.

Step 4 — Enter General Setup

On the main menu, use the down arrow to highlight General Setup and press Enter. This is usually near the top of the list on x86-64 systems. All the basic kernel identity and behavior options are in here.

Step 5 — Find “Kernel .config support”

Inside General Setup, scroll down using the down arrow. You are looking for an item that says:

<M> Kernel .config support

The <M> prefix means it is currently set as a module. If you cannot find it by scrolling, press / and type IKCONFIG to jump to it directly.

Step 6 — Read the Help Text

With the item highlighted, press the right arrow key until the bottom toolbar cursor is on < Help >, then press Enter. The help screen for CONFIG_IKCONFIG explains exactly what it does and what the sub-options mean. This is a good habit to build — many config options have very informative help text. Press Enter on < Exit > when done.

Step 7 — Toggle to Built-In Using Spacebar

Press Spacebar once. The display changes from:

<M> Kernel .config support

to:

<*> Kernel .config support
[ ]   Enable access to .config through /proc/config.gz (NEW)

The <*> means this feature is now baked directly into the kernel image — always on, no module loading needed. A new child option also appeared: Enable access to .config through /proc/config.gz. Toggle this on too with Spacebar if you want to read the config from a running kernel.

Step 8 — Save and Exit

Press Esc twice to go back to the main menu. Navigate right with the arrow key to highlight < Save > and press Enter to save. Then select < Exit >. Your choices are now written to the .config file in the kernel source root.

📷 Image Suggestion

A terminal screenshot showing zcat /proc/config.gz | grep IKCONFIG output on a running Linux system, proving that the config is accessible. Alt text: reading kernel config from /proc/config.gz on running Linux system.

📷 Image Suggestion

A clean annotated diagram or screenshot of the menuconfig bottom toolbar showing the Save, Load, Help, and Exit buttons highlighted. Alt text: menuconfig toolbar buttons keyboard shortcuts Linux kernel.

What is make menuconfig and why do I need it?

make menuconfig is the standard interactive tool for configuring the Linux kernel before building it. It reads all the kernel’s Kconfig files and presents the options as a navigable menu. You need it because the Linux kernel has thousands of configuration options and you must produce a .config file before compilation. Without a valid .config, the build will either fail or use defaults that may not suit your hardware or use case.

Is there a difference between make menuconfig and make xconfig?

They configure the same options but use different interfaces. make menuconfig uses a text-based ncurses UI that runs in any terminal — this is the most widely used option for server and embedded development. make xconfig opens a Qt-based graphical window and requires a desktop environment. make nconfig is another text-based alternative with a slightly different look. All three read and write the same .config file.

Can I edit the .config file manually instead of using menuconfig?

Technically yes, but it is risky. The .config file is plain text and human-readable, so you can open it in any text editor. However, many kernel options have dependencies — enabling option A may require option B to also be enabled. menuconfig enforces these dependencies automatically. If you edit .config manually and break a dependency, the build may fail with cryptic errors. If you do edit manually, always run make oldconfig afterwards to validate and fix the dependency chain.

What happens if I run make without a .config file?

The build will fail with an error saying the configuration is missing. On some kernel versions it may ask you interactively about each option (like make config). The safe approach is to always generate a starting .config first — either with make localmodconfig, make defconfig, or by copying your distribution’s config from /boot/config-$(uname -r).

What does n -> m mean in a kernel config change table?

It means: change this config option from its current value of n (disabled/not compiled) to m (built as a loadable kernel module). So if a tutorial says a config change is n -> m, open menuconfig, find that option, and press Spacebar until it shows <M>.

How do I upgrade my .config when moving to a newer kernel version?

Run make oldconfig in the new kernel source directory with your old .config copied to it. This command reads all existing settings from the old file and then asks you interactively only about the new config symbols introduced in the new kernel version. If you want to skip the questions and just accept the defaults, run make olddefconfig instead.

Does enabling CONFIG_IKCONFIG make my kernel significantly larger?

No. The .config data is stored compressed inside the kernel image. For a typical configuration the size increase is around 10–30 KB — negligible in practice. The benefit of always being able to recover the exact build configuration far outweighs this tiny overhead. This is why most embedded and production teams enable it.

Q1: What is the difference between CONFIG_IKCONFIG=y and CONFIG_IKCONFIG=m?

When set to y, the kernel configuration data is embedded directly into the kernel binary itself using the IKCFG_ST / IKCFG_ED markers. It is always accessible without loading anything. When set to m, the same data is packaged into a kernel module called configs.ko. You must first run modprobe configs before /proc/config.gz becomes available. For embedded systems and production kernels, y is preferred because it removes the dependency on module loading.

Q2: A running Linux system has no .config file in /boot. How do you find out what options it was built with?

There are three approaches in order of preference. First, check if /proc/config.gz exists — if yes, CONFIG_IKCONFIG_PROC=y was set and you can run zcat /proc/config.gz to read the full config. Second, use the scripts/extract-ikconfig script on the kernel binary in /boot/vmlinuz-$(uname -r) — this works if CONFIG_IKCONFIG=y was set. Third, if neither works, the kernel was built without IKCONFIG — you can only infer the config by inspecting loaded modules with lsmod and checking /sys/module/.

Q3: What does make localmodconfig do and why is it better than make defconfig for a development machine?

make localmodconfig takes the list of kernel modules currently active on the running system (from lsmod) and generates a .config that enables only those modules. make defconfig on the other hand generates a generic configuration with broad hardware support — resulting in hundreds of unnecessary drivers being compiled. For a development machine, localmodconfig produces a kernel that compiles in a fraction of the time (sometimes 10x faster) because only the modules actually needed by that specific machine are included.

Q4: What is the purpose of CONFIG_LOCALVERSION and where is it set?

CONFIG_LOCALVERSION appends a custom string to the kernel release version shown by uname -r. It is set in menuconfig under General Setup → Local version – append to kernel release. This is extremely useful when multiple custom kernels are deployed — the suffix immediately identifies which build is running. Common patterns include -dev01, -embedded-v2, or -rt for real-time patched kernels.

Q5: How does the kernel’s build system use the .config file?

The .config file is processed by the kernel’s Kbuild system. It is converted into a C header file called include/generated/autoconf.h which contains #define macros for every enabled option. Every C source file in the kernel can then use #ifdef CONFIG_X to conditionally compile code for that feature. Options set to m cause separate object files to be produced and packaged into loadable .ko module files.

Q6: Why might running make on a new kernel version with an old .config file fail or produce a broken kernel?

New kernel releases often introduce new config symbols that do not exist in the old .config. If the build system encounters an unknown symbol, it may assign an unpredictable default. More critically, renamed symbols may silently disable features that were previously enabled. The correct fix is to run make oldconfig which explicitly prompts you for each new symbol, or make olddefconfig which accepts defaults for all new symbols automatically without prompting.