Availability is not binding
modinfo reads metadata for a named module in the selected kernel module tree. It may describe aliases, firmware names and the module version. Those fields explain a build; they do not certify that a device has initialized. Some names are PCI driver names for built-in code rather than independently installable module packages.
modinfo MODULEuname -rBuilt in and loadable differ
A kernel option set to y builds the driver into the kernel; m creates a loadable module when the option permits that choice. Built-in code need not appear in lsmod. If modinfo fails, inspect the local kernel configuration and binding before treating the absence of a module file as a missing driver. Distribution configurations can differ from the upstream source snapshot.
lsmodLoading failures need exact evidence
Authentication errors, mismatched vermagic and unresolved symbols are different paths. Save the running kernel version and the relevant log before choosing a remedy. This tool never loads, unloads, blacklists or force-loads modules. Unloading a display, network or storage driver can interrupt the session or data access; such changes require device-specific planning and recovery.
journalctl -b -k --no-pagerReferences
Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.
- Linux driver binding
Project or distribution documentation
- Linux module implementation
Project or distribution documentation