Dell Update Package 6.5 (BLD_131)
Copyright (c) 2003-2010 Dell, Inc. All Rights Reserved.
Release Title:
Dell Server BIOS 11G, 1.6.3

Release Date:
February 13, 2011

Default Log File Name:
R296752

Supported System(s):
PowerEdge R410

Description:
PowerEdge R410, BIOS, 1.6.3 for Q1CY11

Supported Device(s):
Server BIOS 11G

Fixes / Enhancements:
1. Added support for Dell(TM) Lifecycle Controller version 1.5.
2. Added support for S100(SWRAID 2.0).


Important Device Information:
* Do not run other applications while executing Dell Update Packages.

* The software contained in a Dell Update Package for Linux is an aggregate
of third party programs as well as Dell programs.  Use of the software is
subject to designated license terms.  All Software that is designated as
"under the terms of the GNU GPL" may be copied, distributed and/or modified in
accordance with the terms and conditions of the GNU General Public License,
Version 2, June 1991.  All software that is designated as "under the terms
of the GNU LGPL" (or "Lesser GPL") may be copied, distributed and/or modified
in accordance with the terms and conditions of the GNU Lesser General Public
License, Version 2.1, February 1999.  Under these GNU licenses, you are
also entitled to obtain the corresponding source files by contacting Dell at
1-800-WWW-DELL.  Please refer to the Open Manage Open Source DVD.  There may
be a nominal fee charged to you for the physical act of transferring a copy.

* If the following error occurs, "Error while loading shared libraries:
libstdc++.so.5: cannot open shared object file: No such file or directory",
you must install the compatibility libraries from the vendor OS repository
or from the OS installation media. To install the compatibility libraries,
use the following command: "RPM -ih compat-libstdc++-33-3.2.3-47.3.i386.rpm"

* When Update Packages stop abruptly due to a power outage or abnormal
termination, perform the following steps:
   - Remove the lock file.
     Type the following command: rm -f /var/lock/.spsetup
   - Run the Update Package again to reapply the update.

* A BIOS update requires enough free physical memory to load the entire BIOS
image into physical memory. If there is insufficient free physical memory
available on the system to load the BIOS image, the Dell Update Package for
BIOS may fail. In this instance, you may attempt running the Dell Update
Package immediately after reboot or after adding more memory. If this does
not resolve the issue, update the BIOS using the diskette method.

* If you run into the above memory limitation on VMWare ESX, the problem
is because the console OS available memory is only 272M by default. Please
increase the console OS memory to 800M temporarily and perform the FW
update. During ESX server boot up please perform the below steps to increase
the memory available.
1. While booting, press 'e' on the VMware ESX line (Grub option display
screen).
2. Press 'e' again on the 'uppermem=' line and edit uppermem=819200. Press
Enter.
3. Press 'e' on the kernel line (Just below the uppermem line). Edit the
kernel line with mem=800M and press Enter.
4. Press 'b' to boot with these options.
5. Perform the FW update.

* BIOS update may issue the following kernel messages on the console and in
"/var/log/messages":
    dcd***: disagrees about version of symbol struct_module
    dcd***: Unknown symbol get_user_size
    dcd***: Unknown symbol put_user_size
  Ignore these messages because they do not refer to errors in BIOS update.

* The USB arbitration service of VMWare ESX 4.1 makes the USB devices invisible

to the Hypervisor. So, when DUPs or the Inventory Collector runs on the MN, the

 partitions exposed as USB devices are not shown, and it reaches the timeout

 after 15 to 20 minutes. This timeout occurs in the following cases:

* If you run DUPs or Inventory Collector on VMware ESX 4.1, the partitions
exposed as USB devices are not visible due to the USB arbitration service
of VMware ESX 4.1 and timeout occurs. The timeout occurs in the following
instances:

•	When you start “DSM SA Shared Service” on the VMware ESX 4.1 managed
node, it runs Inventory Collector. To work around this issue, uninstall
Server Administrator or wait until the Inventory Collector completes execution
before attempting to stop the “DSM SA Shared Service”.
•	When you manually try to run the Inventory Collector on the VMware ESX
4.1 managed node while USB arbitration service is running. To fix the issue,
stop the USB arbitration service and run the DUPs or the Inventory Collector.
To stop the USB arbitration service:
1.	Use the “ps aux|grep usb”  to check if the USB arbitration service
is running.
2.	Use the “chkconfig usbarbitrator off” command to prevent the USB
arbitration service from starting during boot.
3.	After you stop the usbarbitrator, reboot the server to allow the
DUPs and/or the Inventory collector to run.

 Note: If you require the usbarbitrator, enable it manually. To enable the
 usbarbitrator, run the command - chkconfig usbarbitrator on.