akmods

akmods [options]

akmods checks installed akmod packages and rebuilds out-of-tree kernel modules when they are missing, outdated, or broken for a given kernel. It is the Fedora/RHEL-family counterpart to frameworks like DKMS: an akmod package ships module sources and build metadata; akmods compiles them on the local system (often into a matching kmod-* RPM) whenever a new kernel appears.Typical use is after installing or updating drivers from RPM Fusion (for example NVIDIA via akmod-nvidia). A systemd unit may run akmods at boot so modules for the current kernel are ready before they are needed. Manual runs are common when a build failed, kernel-devel was missing during an earlier attempt, or you need modules for a kernel other than the one currently running.Builds need a compiler toolchain and matching kernel headers/devel packages for each target kernel. Secure Boot setups may also need module signing keys under /etc/pki/akmods.

--force

Try all akmods, including ones that failed on earlier runs.

Build and install only for the given kernel version string (same format as uname -r).

Rebuild all modules even when they already appear up to date.

Build and install only the named akmod package.

Reduce output.

Increase output.

Failed builds often leave no usable kmod until headers, compiler tools, and enough disk space are available, then akmods --force or --rebuild is re-run. On ostree-based systems (Silverblue/Kinoite) module signing and rebuild timing can differ from classic package installs. The man page is sparse; log output under the akmods service and journal is usually the best diagnostic trail.

dkms(1), modprobe(8), uname(1)

Documentation