Originally Posted by liquidtenmilion
I use these rules.
1. Compile IN the the modules that you need to boot. These are IDE Chipset support, Filesystem support, and anything else you need.
2. Compile IN any other IDE chipset that you think you may use in the future.(Just in case you ever buy a new motherboard, there is literally no performance decrease from building in ALL the chipsets)
3. Compile as MODULES other hardware that you ALWAYS have in your PC(Sound card, USB support, etc.
4. Compile as modules any other hardware that you _think_ you _may_ install one day in the future, becuase having to do a kernel recompile whenever you install new hardware is not a good thing(Not to mention the subsequent rebuild of Nvidia/kqemu/wireless chips/etc.
i wonder why you would recompile a kernel ?
If one of the standard kernels can boot on your system, there is no need to
recompile, as all of your rules are followed there.
when you recompile a kernel, only compile in the support *your machine* needs
at boot time. all stuff that's not needed makes the kernel larger and slows
down the boot process. Besides the things mentioned earlier ( filesystem, chipset-support, IDE/SCSI/SATA )pick the VESA framebuffer-support, to prevent
the "black screen" at boot. ( ...and no other framebuffer support ).
The rest can be build as modules.
When you add new hardware, you can just compile the module(s) it needs.
( no need to recompile everything or anything else )
I believe that alsa (almost) allways has to be modular.
When you run "alsaconfig", a few aliasses are added in /etc/modprobe.conf.
Those are used when loading the module(s), and cannot be set if alsa is build-in.
AFAIK this was allways the case...( not sure...)