Quickly inspect which kernel modules are loaded and why they matter for systems and troubleshooting. 26.11.2025 | reading time: 2 min Want to know which kernel drivers are active right now on a Linux host and which ones other modules depend on? The `lsmod` command shows loaded kernel modules in a compact table and is the first tool to reach for when investigating hardware drivers, module dependencies, or boot-time problems. Hands-on demonstration Run `lsmod` and inspect the table: ```bash $ lsmod Module Size Used by intel_rapl_msr 20480 0 intel_rapl_common 28672 1 kvm_intel 200704 0 kvm 1200128 1 snd_hda_intel 53248 2 snd_hda_codec 163840 1 ``` This output shows the module name, its size, and how many users or dependent modules reference it; pipe to `grep` to filter results, for example `lsmod | grep kvm`. Read deeper than the table Remember that `lsmod` reads `/proc/modules` and only lists modules actually loaded as separate objects; it does not show drivers compiled into the kernel image, nor detailed metadata like author or parameters; for that use `modinfo` and check `/sys/module` when you need attribute-level information or live parameter values. Combine with other commands For practical workflows combine `lsmod` with `grep` to spot suspects, use `modinfo` to learn about a module, and use `modprobe`, `insmod` or `rmmod` to add or remove modules when testing; when a module fails to load check `dmesg` for kernel messages and `depmod` to rebuild dependency maps. Next steps and skills Use `lsmod` early in troubleshooting to confirm what the kernel actually has loaded, then follow traces into `modinfo`, `dmesg`, and `/proc` to find root causes; if you want structured preparation for production work consider deepening your knowledge toward certifications such as CompTIA Linux+ or LPIC-1 and try intensive exam preparation at bitsandbytes.academy where practical lab work sharpens your command-line skills. Join Bits & Bytes Academy First class LINUX exam preparation. utilities boot-process troubleshooting processes
