I'm trying to understand how Linux supports such a wide range of computers and peripherals without becoming unnecessarily bloated. Does a typical kernel actually contain drivers for nearly every possible device, or are drivers downloaded dynamically when hardware is detected? How do kernel modules, built-in drivers, and firmware packages fit into this, and what happens on minimal or embedded systems?
5 Answers
There is still some storage overhead in a general-purpose distribution. A typical installation may keep hundreds of megabytes of compressed modules and firmware for hardware you will never use. That is an intentional tradeoff: generic desktop and server installations prioritize compatibility and convenience. Embedded systems and specialized appliances usually select a small kernel configuration and remove everything unnecessary, sometimes producing images only a few megabytes in size.
Most distributions ship a broad set of drivers, but many are compiled as loadable kernel modules rather than being permanently active. When the system detects hardware, it selects and loads the matching module—usually automatically. Unused modules remain on disk, so they consume storage but not meaningful RAM or boot time. Drivers needed to access the root filesystem, such as storage and certain chipset drivers, may be built directly into the kernel.
The terms can be confusing because “Linux” may refer to the kernel source, while a distribution chooses its own configuration and packages. The source tree supports many architectures and optional features, but a normal installed kernel is compiled for a particular architecture and may omit plenty of code. So the accurate answer is that Linux can support a huge range of hardware, while each running system uses only a selected subset of that support.
A lot of hardware can share one driver because the driver targets the underlying chipset or standard interface rather than each product brand. One USB-storage, Wi-Fi, or graphics driver may support many different models. Also, Linux drivers generally provide the kernel interface only; large control panels, update tools, and other companion software are separate, which keeps the driver packages relatively modest compared with some proprietary bundles.
The kernel source tree is definitely large, and drivers make up a substantial portion of it. That is different from the size and memory usage of the particular kernel and module set installed on one machine.
Linux does not download a driver every time hardware appears. The kernel and its modules normally come from the distribution’s packages. The package manager installs them ahead of time, and the kernel loads the appropriate ones when needed. Some devices also require firmware: small binary programs sent to the device during initialization. Packages such as linux-firmware contain those blobs, but they are not the actual kernel drivers.
You can also build a custom kernel or use tools such as `make localmodconfig` to include only modules detected on your current machine. That saves space, but hardware you haven’t included won’t work until you rebuild or install the appropriate module.