Users Guide

130 Installing Managed System Software on Supported Linux Operating Systems
Using Dynamic Kernel Support After Server Administrator Installation
To enable Server Administrator to support a kernel that is not supported by
a precompiled device driver and is loaded after Server Administrator has been
installed, perform the following steps: Ensure that the DKS prerequisites are
met on the system to be managed and boot the new kernel on the system.
Server Administrator builds a device driver for the kernel running on the
system the first time that Server Administrator starts after the kernel is loaded.
By default, Server Administrator starts during system startup.
Copying a Dynamically Built Device Driver to Systems Running the Same Kernel
When Server Administrator dynamically builds a device driver for the
running kernel, it installs the device driver into the
/lib/modules/<kernel>/kernel/drivers/firmware directory, where <kernel> is
the kernel name (returned by typing uname -r). If you have a system
running the same kernel for which a device driver was built, you can copy the
newly built device driver to the /var/omsa/dks/<kernel> directory on the other
system for use by Server Administrator. This action allows Server
Administrator to use DKS on multiple systems without having to install the
kernel source on every system.
An example is the following scenario: System A is running a kernel that is not
supported by one of the Server Administrator precompiled device drivers.
System B is running the same kernel. Perform the following steps to build a
device driver on system A and copy the device driver to system B for use by
Server Administrator:
1
Ensure that the DKS prerequisites are met on system A.
2 Start Server Administrator on system A.
Server Administrator builds a device driver for the kernel running on
system A during startup.
3 Ty p e uname -r on system A to determine the name of the running
kernel.