Here's the info on copying dynamic esm driver to other system s

Shaw, Marco marco.shaw at nbtel.nb.ca
Tue Nov 26 14:09:00 CST 2002


Assuming I'm not the only one getting this error:

[root at localhost misc]# modprobe esm
Warning: loading /lib/modules/2.4.9-31enterprise/misc/esm.o will taint the kerne
l: no license
  See http://www.tux.org/lkml/#export-tainted for information about tainted modu
les
Module esm loaded, with warnings

I wonder if this is causing my problem(s)?

Marco

-----Original Message-----
From: Steve_Boley at dell.com [mailto:Steve_Boley at dell.com] 
Sent: Tuesday, November 26, 2002 3:41 PM
To: Linux-Poweredge at dell.com
Subject: Here's the info on copying dynamic esm driver to other systems


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 directory 
  "/lib/modules/<kernel>/misc", 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 directory "/var/omsa/dks/<kernel>" on the 
  other system for use by Server Administrator. This action allows 
  Server Administrator to use its Dynamic Kernel Support feature on 
  multiple systems without having to install the kernel source on 
  every system.

  For example: System A is running a kernel that is not supported by 
  one of the Server Administrator prebuilt 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 Dynamic Kernel Support prerequisites are met on 
     system A.

  2. Install Server Administrator on system A.

     Server Administrator builds a device driver for the kernel 
     running on system A during installation.

  3. Type "uname -r" on system A to determine the name of the 
     running kernel.

  4. Copy the file "/lib/modules/<kernel>/misc/esm.o" from system A 
     to the directory "/var/omsa/dks/<kernel>" on system B, where 
     <kernel> is the kernel name returned by typing "uname -r" in 
     step 3.

     NOTE: You might have to create the directory 
     "/var/omsa/dks/<kernel>" on System B. For example, if the kernel 
     name is "1.2.3-4smp", you can create the directory by typing 
     "mkdir -p /var/omsa/dks/1.2.3-4smp".

  5. Install Server Administrator on system B.

     Server Administrator detects that the device driver you copied to 
     the directory "/var/omsa/dks/<kernel>" supports the running 
     kernel and uses that device driver.

  NOTE: If this procedure is used to install Server Administrator, 
  this procedure must be used to upgrade Server Administrator if the 
  new version of Server Administrator does not support the running 
  kernel with a prebuilt device driver.

  NOTE: When Server Administrator is uninstalled from System B, the 
  process does not remove the "/var/omsa/dks/<kernel>/esm.o" file that 
  you copied to system B. You must remove the file if it is no longer 
  needed.

Steve Boley
Dell Enterprise Expert Center
Senior Network Technician/Analyst
Poweredge, PowerApp, PowerConnect, 
and PowerVault Trained Technician
      

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq or search the list archives at http://lists.us.dell.com/htdig/




More information about the Linux-PowerEdge mailing list