Load, inspect and remove kernel modules cleanly and reliably from the command line. 11.04.2026 | reading time: 2 min Ever needed to add driver support on a running system or remove a misbehaving kernel module without rebooting? The command `modprobe` is the standard tool for inserting and removing kernel modules while resolving dependencies and honoring system configuration. Quick demonstration Follow this short session that shows modprobe in action: ```bash $ sudo modprobe dummy $ sudo modprobe dummy numdummies=2 $ lsmod | grep dummy dummy 16384 2 $ sudo modprobe --show-depends dummy insmod /lib/modules/$(uname -r)/kernel/drivers/net/dummy.ko $ sudo modprobe -r dummy ``` This loads the "dummy" network module, passes a parameter to create two instances, shows the module in the loaded list, displays dependency loading, and finally removes the module. Options that matter Use `-r` to remove modules, `-v` for verbose output, and `-n` for a dry run that prints what would happen; `--show-depends` reveals which objects would be insmodded; module parameters are passed on the command line like `modprobe modulename param=value`; configuration files in `/etc/modprobe.d/` let the admin blacklist modules or set default options so behavior survives reboots. When things get tricky If a module fails to load, run `depmod` to regenerate dependencies, consult `modinfo` for symbol and parameter details, and check dmesg for kernel messages; use `insmod` and `rmmod` only when bypassing dependency resolution is required, and prefer `modprobe` for everyday module management and scripts. Next steps Mastering modprobe ties into automated boot behavior, udev-driven device handling, and troubleshooting driver issues; experiment in a safe environment, document module options in `/etc/modprobe.d/`, and consider preparing for certification to formalize knowledge and skills. Join Bits & Bytes Academy First class LINUX exam preparation. utilities boot-process troubleshooting scripting
