Q: A newly compiled kernel module is not loading, with `modprobe` returning "module not found." The `.ko` file exists. What is wrong?
Linux kernel modules must reside in the correct directory and be indexed by depmod before modprobe can find them.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "We encountered this OS-level bottleneck during peak traffic and diagnosed it down to kernel and filesystem metrics. The interviewer is testing: Kernel module system, depmod, module paths.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Linux kernel modules must reside in the correct directory and be indexed by depmod before modprobe can find them.
- Wrong directory: Modules must be placed under
/lib/modules/$(uname -r)/. If the.kofile was compiled for a different kernel version, it will be in the wrong directory tree. - Missing dependency index: After placing the module in the correct path, you must run
depmod -ato rebuild the module dependency database (modules.dep). Without this,modprobecannot locate the module. - Version mismatch: The module was compiled against a different kernel version. The kernel enforces version magic matching. Check with
modinfo mymodule.koand comparevermagicagainstuname -r.
Remediation & Permanent Safeguards
Common causes: Correct workflow: Place module → depmod -a → modprobe mymodule.
- Force loading (dangerous):
insmod /path/to/mymodule.kobypasses dependency resolution and loads the module directly, but risks kernel panics if dependencies are unmet.
- Wrong directory: Modules must be placed under /lib/modules/$(uname -r)/. If the .ko file was comp...
- Missing dependency index: After placing the module in the correct path, you must run depmod -a to...
- Version mismatch: The module was compiled against a different kernel version. The kernel enforces...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring newly compiled kernel SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring newly compiled kernel
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring newly compiled kernel Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring newly compiled kernel
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).