HP-UX System Administrator's Guide: Configuration Management

Each kernel module in the currently running configuration has a state, which describes
how the module is being used. The possible states are:
unused
The module is installed on the system but not in use.
static
The module is statically bound into the kernel executable. This is the most
common state. Moving a module into or out of this state requires relinking
the kernel executable and rebooting.
loaded
The module is dynamically loaded into the kernel. Newer modules support
this state. Such modules may be added to the kernel configuration or
removed from it without rebooting.
auto
The module will be dynamically loaded into the kernel when it is first
needed, but it hasn’t been needed yet.
When kcmodule is giving information about the currently running system, and there
are configuration changes being held for next boot, kcmodule will list both the current
state and the state at next boot. For next boot, the same states are used, with
complementary meanings:
The module will not be used.
unused
The module will be statically bound into the kernel executable.
static
The module will be dynamically loaded into the kernel during the boot process.
loaded
The module will be dynamically loaded into the kernel when it is first needed after
each boot.
auto
When kcmodule is giving information about a saved configuration, the same states
are used.
Next to each module state is a Cause that tells why the module is (or will be) in that
state. The causes are:
explicit
The system administrator explicitly chose the state.
best
The system administrator chose to use the module, but didn’t choose a
specific state, so the module is in its best state as determined by the
module developer.
auto
The module was in auto state, and was automatically loaded when
something tried to use it.
required
The module was marked required by its developer.
depend
The module is in use because some other module in the configuration
depends on it.
Different modules can support different states. Nearly all modules can be in static
state, but only a few support loaded or auto states. Many modules can be in unused
state, but required modules cannot. The Capable line in the output shows which
states a module supports.
Managing Kernel Modules with kcmodule 163