Errors When Installing Brocade_Driver_Linux_<Versions>.Tar.gz; Operating System Crashes After Invalid Hcm Operand; Uefi Boot Problems; Package - Brocade Communications Systems CNA 1010 Troubleshooting Manual

Errors when installing brocade_driver_linux_<versions>.tar.gz package
If errors occur when installing the no architecture (noarch) brocade_driver_linux_<versions>.tar.gz
driver package, refer to the following descriptions of possible causes and recommended actions to
help resolve the problem.
Possible Cause: Appropriate distribution kernel development packages are not installed on your
host system for the currently running kernel.
Action: If you are installing the brocade_driver_linux_<versions>.tar.gz driver package, the driver
module compiles on the system during installation. If driver build errors result when you install the
package, verify that the appropriate distribution kernel development packages are installed on your
host system for the currently running kernel. These packages should include the gcc compiler and
the kernel sources. If these are not installed, you may need to reinstall the operating system before
continuing installation. Be sure to "install everything" including the developer library options.

Operating system crashes after invalid HCM operand

The Linux RHEL 4 update 7 system (kernel 2.6.9-78) crashes after an invalid operand from the
HCM agent process.
Possible Cause: There may issues with the kernel regarding the system time.
Action: Upgrade the kernel to the latest patch 2.6.9-78.0.5.

UEFI boot problems

This section describes problems that may occur when using the Brocade adapter and unified
extensible firmware interface (UEFI) for booting a host system from a remote storage device (boot
over SAN). Possible causes and recommended actions to help resolve the problems are provided.
System will not boot over SAN or on local disk in Legacy BIOS mode
On some IBM UEFI based systems, Hard Disk 0 is not present after Legacy Only option in boot
manager and system will not boot as local disk or over SAN.
Possible Cause: Hard Disk are not present in the boot manager list.
Action: Follow these steps:
1. Press F1 to enter System Setup during early phase of booting.
2. Select Boot Manager and press Enter.
3. Select Add Boot Option and press Enter.
4. Select Legacy Only and press Enter.
5. Press Esc to return to Boot Manager.
6. Select Change Boot Order and press Enter.
7.
8. Select Legacy Only and press the + key to promote the boot order to a position above the local
Brocade Adapters Troubleshooting Guide
53-1001582-01
Select the existing Boot Order and press Enter.
device that contains the operating system (typically, this would be above Hard Disk 0). Press
Enter.
General HBA and CNA problems
2
15