Practical commands to list, inspect and manage loaded kernel modules on a running system. 16.11.2025 | reading time: 2 min Want to know which kernel drivers are active and what they do? Use `lsmod` to list loaded modules, `modinfo` to query metadata, and `modprobe` to test or change module state while you investigate. Hands-on Investigation Run this sequence to see, inspect and simulate changes: first list modules with `lsmod`, then read metadata with `modinfo`, and finish with a dry run via `modprobe -n -v` to avoid surprises; example session: ``` $ lsmod Module Size Used by snd_hda_intel 225280 1 e1000e 286720 0 ipv6 497664 12 $ modinfo snd_hda_intel filename: /lib/modules/5.15.0-xyz/kernel/sound/pci/hda/snd-hda-intel.ko license: GPL description: Intel HDA driver author: ALSA developers $ sudo modprobe -n -v snd_hda_intel install /sbin/modprobe --ignore-install snd_hda_intel ``` Digging Deeper Look beyond the simple list: read `/proc/modules` for the kernel view and `/sys/module` for per-module attributes, use `modinfo` to check parameters and dependencies, try `modprobe -n` for a safe dry run, and remember `rmmod` and `insmod` exist for direct removal and insertion when you know what you are doing. Related Observability Check kernel messages with `dmesg` or `journalctl -k` to see load and unload events and driver errors, use `depmod` to rebuild module dependency maps after installs, and inspect systemd services such as systemd-modules-load.service for module autoloading at boot. Final Note Inspecting modules is a fast way to connect symptoms to drivers and to fix hardware or boot issues; keep practicing these commands and consider formal study toward certifications like CompTIA Linux+ or LPIC-1, and intensive exam preparation at bitsandbytes.academy. Join Bits & Bytes Academy First class LINUX exam preparation. utilities boot-process troubleshooting
