Table of Contents
Advertisement
Tip: All the EFI executable files have an extension of .EFI. The executables
may be run only from within EFI, not from within any operating system.
Access to the file system on a device is done through the FSn: command (where
n is the file system number shown in the device mapping table). This is similar in
concept to changing drive letters in DOS. You can use the map command at any
time to remind yourself of the available file systems.
Tip: Adding or removing media may cause arbitrary reassignments of the FSx
designations. Always make sure that you access the right media by issuing the
map command or map -r if media has been added or removed.
As an example of the capability of accessing file systems, the following are the
steps to access data stored on the USB memory key device:
1. Insert the USB memory key into the USB port (can be hot-added).
2. Start the EFI shell from the EFI Firmware Boot Manager menu.
3. Use the map command to identify the appropriate mapping for the USB device
the EFI automatically created. Sample output of the command is in
Figure 4-4.
If the appropriate mapping does not appear, run map -r, where parameter -r
forces EFI to refresh the device mapping table.
Shell> map
Device Mapping Table
fs0 : MemMap(0:FF000000-FFFFFFFF)
fs1 : MemMap(0:FF800200-FFBFFFFF)
fs2 : Acpi(PNP0A03,0)/Pci(5|2)/Usb(0, 0)/HD(Part1,Sig00000000)
blk0 : MemMap(0:FF000000-FFFFFFFF)
blk1 : MemMap(0:FF800200-FFBFFFFF)
blk2 : Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Master)
blk3 : Acpi(PNP0A03,0)/Pci(5|1)/Ata(Primary,Slave)
blk4 : Acpi(PNP0A03,1)/Pci(3|0)/Scsi(Pun0,Lun0)
blk5 : Acpi(PNP0A03,0)/Pci(5|2)/Usb(0, 0)
blk6 : Acpi(PNP0A03,0)/Pci(5|2)/Usb(0, 0)/HD(Part1,Sig00000000)
Figure 4-4 Map command
IBM Eserver xSeries 455 Planning and Installation Guide
98
Advertisement
Table of Contents
