System Firmware Memory Map; System Firmware I/O Support - IBM BladeCenter QS20 Problem Determination And Service Manual

After you have modified environment variables, run nvupdate and reboot the
operating system with boot or reset-all.

System firmware memory map

The BladeCenter QS20 system firmware resides in the memory range between
16MB and 32MB for internal usage. Any secondary boot loader (OF client program)
has its own memory map but is required to respect that given range. Further
information about the system configuration can be read from the Open firmware
device-tree. For information about Cell BE register mappings please refer to the
appropriate specifications and data sheets.

System firmware I/O support

BladeCenter QS20 system firmware supports:
v ATA Controller SIL 0680A
v Mellanox InfiniBand MHEA28-1TCSB
v Flash Module
Table 11. Supported commands (continued)
Command Description
set-defaults Writes associated default values into all the environmental variables.
Attention:
command.
Use only if the system does not boot anymore.
Note: Use nvupdate to commit the changes
boot Loads the operating system based on setting in Management Module
boot sequence. No additional arguments supported.
reset-all Reboots the blade server.
netboot Boot from network using BOOTP/TFTP. This is a special implementation
of the boot net command, which is not supported with this version of
firmware.
Table 12. Environment variables
Environment
variable Description
boot-file For disk boot. Contains the yaboot image label and kernel command line
for Linux. For example:
setenv boot-file linux root=/dev/hda3 console=rtas0
Note: Newer kernels can require console=hvc0.
boot-device Specifies the device for the yaboot loader. Must contain a valid device
node from the device tree or a valid device alias. For example:
setenv boot-device /pci@24004000000/ata@d/disk@
Note: This is the default.
boot-command Contains the term which is used to boot the operating system. This is
boot by default and is not intended to be changed. The variable can be
used by system test to execute test cases in the firmware context.
Note: You can always bypass the boot-command by pressing s early
during the boot process.
Customization of firmware is removed when you use this
Chapter 3. Configuring the blade server
35