Man page for apt-get dkms Command
This tutorial shows the man page for man dkms in linux.
Open terminal with 'su' access and type the command as shown below:
Result of the Command Execution shown below:
dkms Dynamic Kernel Module Support
dkms [action] [options]
dkms is a framework which allows kernel modules to be dynamically built
for each kernel on your system in a simplified and organized fashion.
add Adds a module/version combination to the tree for builds and
installs. Requires source in /usr/src/
sion>/ as well as a properly formatted dkms.conf file.
remove Removes a module/version or module/version/kernel combination
from the tree. If the modules is currently installed, it first
uninstalls it and if applicable, will replace it with its origi
nal_module. Use the all option in order to remove all
instances for every kernel at once.
build Builds the specified module/version combo for the specified ker
nel. If no kernel is specified it builds for the currently run
ning kernel. All builds occur in the directory
Installs a built module/version combo onto the kernel it was
built for. If the kernel option is not specified it assumes the
currently running kernel.
Uninstalls an installed module/version combo from the kernel it
was installed upon. After uninstall completion, the driver will
be left in the built state. To completely remove a driver, the
remove action should be utilized.
match Match installs modules onto the specified kernel by looking at
the configuration of the specified templatekernel. Every module
that is installed on the templatekernel within dkms is then
installed on that specified kernel.
Creates a floppy driver disk image for use when updated drivers
are needed to install an OS. Currently, the supported distribu
tions are redhat, suse and UnitedLinux. For Red Hat driver
disks, necessary driver disk files are looked for in the red
hat_driver_disk subdirectory of your module source directory.
You must specify the distro while using this action. Driver
disks can be made for single kernels or can be made to support
multiple kernels. To create a driver disk image with modules
for multiple kernels, just specify multiple k parameters on the
command line ( k kernel1 k kernel2 a arch1 a arch2).
Red Hat began supporting multi arched driver disks in RHEL3. To
force creation of a driver disk with arch information, specify
d redhat2 or if you specify multiple architectures on the com
mand line and use d redhat , DKMS will create a version 2
driver disk. By specifying d redhat1 , you can force a version
1 driver disk image.
Note that redhat1 driver disks actually supported multiple
architectures when the second arch was i386 and the kernel mod
ule was for the BOOT kernel. DKMS allows for this, and as such
you can create a redhat1 style driver disk if the only other
arch is i386 and the kernel name ends in BOOT.
See http://people.redhat.com/dledford for more information on
the Red Hat driver disk standards and which files are necessary
to make a driver disk.
Fedora Core 5 and higher, RHEL5 and higher require DKMS version
2.0.14 or higher to generate a proper driver disk image.
For suse/UnitedLinux driver disks, /usr/share/YaST2/modules/Ven
dor.ycp will also be copied to the driver disk; no other files
are needed. However, for these distros, you must specify a r
release. For SuSE 9.1, it would be d suse r 9.1. For SLES9, it
would be d suse r sles9.
By default the disk image it creates is 1440 (k) in size. This
can be overridden by specifying a different size