Users Guide

Installing Managed System Software on Supported Linux Operating Systems 137
If you see the following message during Server Administrator Device Drivers
startup, then Server Administrator has attempted to use its DKS feature, but
was unable to use the feature because certain prerequisites were not met:
Building <driver> using DKS... [FAILED]
where
<driver>
is
dcdbas
or
dell_rbu
NOTE: Server Administrator logs messages to the /var/log/messages log file.
To use DKS, identify which kernel is running on the managed system, and
check the DKS prerequisites.
Determining the Running Kernel
1
Log in as
root
.
2
Type the following command at a console and press <Enter>:
uname -r
The system displays a message identifying the running kernel. If it is not one of
those listed in the managed system software readme file, then the managed
system software may need to use DKS to support it.
Dynamic Kernel Support Prerequisites
For managed system software to use DKS, the following dependencies must
be met before starting Server Administrator.
The running kernel must have loadable module support enabled.
The source for building kernel modules for the running kernel must be
available from
/lib/modules/`uname –r`/build
. On systems running SUSE
Linux Enterprise Server (versions 9 and 10), the
kernel-source
RPM
provides the necessary kernel source. On systems running Red Hat
Enterprise Linux (version 4), the
kernel -devel
RPMs provide the
necessary kernel source for building kernel modules.
The GNU make utility must be installed. The
make
RPM provides this utility.
The GNU C compiler (gcc) must be installed. The
gcc
RPM provides this
compiler.
The GNU linker (ld) must be installed. The
binutils
RPM provides this linker.
When these prerequisites have been met, DKS will automatically build a
device driver when needed during Server Administrator startup.