Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


  • The platform:
    anisha@linux-dopx:~/> uname -a
    Linux linux-dopx 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 x86_64 x86_64 x86_64 GNU/Linux

  • The kernel downloaded is the latest stable one from kernel.org.

  • We let the defaults remain (make no changes) in the options of make menuconfig.
  • Simply type make, make install, grub-update, and reboot.

Now, following these assumptions, are we still required to make some additional changes to files or compile some extra drivers to ensure a error free reboot?

If yes, then on what things do those changes depend on?


anisha@linux-dopx:/> sudo /sbin/lspci -n
00:00.0 0600: 8086:29c0 (rev 10)
00:02.0 0300: 8086:29c2 (rev 10)
00:1b.0 0403: 8086:27d8 (rev 01)
00:1c.0 0604: 8086:27d0 (rev 01)
00:1c.1 0604: 8086:27d2 (rev 01)
00:1d.0 0c03: 8086:27c8 (rev 01)
00:1d.1 0c03: 8086:27c9 (rev 01)
00:1d.2 0c03: 8086:27ca (rev 01)
00:1d.3 0c03: 8086:27cb (rev 01)
00:1d.7 0c03: 8086:27cc (rev 01)
00:1e.0 0604: 8086:244e (rev e1)
00:1f.0 0601: 8086:27b8 (rev 01)
00:1f.1 0101: 8086:27df (rev 01)
00:1f.2 0101: 8086:27c0 (rev 01)
00:1f.3 0c05: 8086:27da (rev 01)
01:00.0 0200: 10ec:8136 (rev 01)

share|improve this question
That is entirely dependent on the hardware being used. – Chris Down Jan 19 '12 at 12:06
@ChrisDown Should I post more info other than uname? – TheIndependentAquarius Jan 19 '12 at 12:08
The entirety of hardware contained in your computer, yes. lspci -n would be helpful. – Chris Down Jan 19 '12 at 12:11
@ChrisDown Edited. – TheIndependentAquarius Jan 19 '12 at 12:16

It is not recommended just a bare make menuconfig. The required config depends on three things:

 the hardware being used
 the features used by the OS/distribution
 the features by you (file-systems, raid, ..etc)

So the recommended "default" config in my view is:

cd your_kernel_src
cp /boot/your-distribution-config .config
make localmodconfig
make menuconfig

See also Kernel configuration for distributions. The first paragraph:

Configuring a kernel was once a fairly straightforward process, only requiring knowledge of what hardware needs to be supported. Over time, things have gotten more complex in general, but distributions have added their own sets of dependencies on specific kernel features—dependencies that can be difficult for regular users to figure out. That led Linus Torvalds to put out an RFC proposal to add distribution-specific kernel configuration options.

share|improve this answer
To put this more succinctly: There's no working "default" or "just what Linus intended" kernel config. If you just download and compile without configuring anything it is expected that you end up with a broken and/or barely functional kernel. – bahamat Jul 31 '12 at 18:02
The default configuration is just that. It used to be whatever Linus was running at the time. Get the configuration for your distribution, and use that as a starting point. – vonbrand Jan 18 '13 at 1:04

As mentioned by @Lai , anything that is not distribution tuned may not work in subtle ways.

But if you just want to play around without much thought, on 4.0 you might get away with:

make defconfig

which detects your architecture and uses for example arch/x86/configs/x86_64_defconfig as a basis.

make help also shows other interesting default related targets like alldefconfig and savedefconfig which may be useful.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.