DragonFly On-Line Manual Pages

Search: Section:  

KLDLOAD(8)             DragonFly System Manager's Manual            KLDLOAD(8)


NAME

     kldload - load a file into the kernel


SYNOPSIS

     kldload [-nv] file ...


DESCRIPTION

     The kldload utility loads file.ko into the kernel using the kernel
     linker.  Note that if multiple modules are specified then an attempt will
     be made to load them all, even if some fail.  The .ko extension name is
     not mandatory when loading a given module using kldload.  It does not
     hurt to specify it though.

     If a bare filename is requested it will only be loaded if it is found
     within the module path as defined by the sysctl kern.module_path.  To
     load a module from the current directory it must be specified as a full
     or relative path.  The kldload utility will warn if a module is requested
     as a bare filename and is present in the current directory.

     The following options are available:

     -n      Do not try to load module if already loaded.

     -v      Be more verbose.


NOTES

     The kernel security level settings may prevent a module from being loaded
     by giving EPERM.  Refer to security(7) for details.


FILES

     /boot/kernel         directory containing loadable modules.  Modules must
                          have an extension of .ko.
     /boot/modules.local  directory for local loadable kernel modules and
                          wrapped external firmware images; see firmware(9)


EXIT STATUS

     The kldload utility exits 0 on success, and >0 if an error occurs.


EXAMPLES

     To load by module name:

           # kldload foo

     To load by file name within the module path:

           # kldload foo.ko

     To load by relative path:

           # kldload ./foo.ko

     To load by full path:

           # kldload /boot/kernel/foo.ko


AUTOMATICALLY LOADING MODULES

     Some modules (ipfw, etc.) may be automatically loaded at boot time by
     having their operation enabled in rc.conf(5).  Modules may also be auto-
     loaded through their addition to loader.conf(5).

     Only those modules necessary for booting the system, including those
     required for mounting the root filesystem, should be handled by
     loader.conf(5).


SEE ALSO

     kenv(1), kldload(2), loader.conf(5), rc.conf(5), security(7),
     kldconfig(8), kldstat(8), kldunload(8)


HISTORY

     The kldload utility first appeared in FreeBSD 3.0, replacing the lkm(4)
     interface.


AUTHORS

     Doug Rabson <dfr@FreeBSD.org>

DragonFly 6.5-DEVELOPMENT        May 11, 2026        DragonFly 6.5-DEVELOPMENT

Search: Section: