| Installation GuidePart II.
IBM Power Systems - Installation and BootingThis part of the Red Hat Enterprise Linux Installation Guide includes information about installation and basic post-installation troubleshooting for IBM Power Systems servers. IBM Power Systems servers include IBM PowerLinux servers and POWER7 and POWER6 Power Systems servers running Linux. For advanced installation options, refer to Part IV, "Advanced installation options". Previous releases of Red Hat Enterprise Linux supported 32-bit and 64-bit Power Systems servers (ppc and ppc64 respectively). Red Hat Enterprise Linux 6 supports only 64-bit Power Systems servers (ppc64). Chapter 11. Planning for installation on Power Systems servers11.1. Upgrade or Install?11.2. Supported Installation HardwareFor installation of Red Hat Enterprise Linux on IBM Power Systems servers, Red Hat supports hard drives connected by a standard internal interface, such as SCSI, SATA, or SAS. Fibre Channel Host Bus Adapters and multipath devices are supported. Vendor-provided drivers may be required for certain hardware. Virtualized installation on Power Systems servers is also supported when using Virtual SCSI (vSCSI) adapters in virtual client LPARs. Note that Red Hat does not support installation to USB drives or SD memory cards. IBM Installation Toolkit is an optional tool that speeds up the installation of Linux and is especially helpful for those unfamiliar with Linux. Use the IBM Installation Toolkit for the following actions: Install and configure Linux on a non-virtualized Power Systems server. Install and configure Linux on servers with previously-configured logical partitions (LPARs, also known as virtualized servers). Install IBM service and productivity tools on a new or previously installed Linux system. The IBM service and productivity tools include dynamic logical partition (DLPAR) utilities. Upgrade system firmware level on Power Systems servers. Perform diagnostics or maintenance operations on previously installed systems. Migrate a LAMP server (software stack) and application data from a System x to a System p system. A LAMP server is a bundle of open source software. LAMP is an acronym for Linux, Apache HTTP Server, MySQL relational database, and PHP (Perl or Python) scripting language.
PowerLinux service and productivity tools is an optional set of tools that include hardware service diagnostic aids, productivity tools, and installation aids for Linux operating systems on IBM servers based on POWER7, POWER6, POWER5, and POWER4 technology. 11.4. Preparation for IBM Power Systems serversEnsure that the real-base boot parameter is set to c00000, otherwise you might see errors such as: DEFAULT CATCH!, exception-handler=fff00300
IBM Power Systems servers offer many options for partitioning, virtual or native devices, and consoles. If you are using a non-partitioned system, you do not need any pre-installation setup. For systems using the HVSI serial console, hook up your console to the T2 serial port. If using a partitioned system the steps to create the partition and start the installation are largely the same. You should create the partition at the HMC and assign some CPU and memory resources, as well as SCSI and Ethernet resources, which can be either virtual or native. The HMC create partition wizard steps you through the creation. If you are using virtual SCSI resources, rather than native SCSI, you must configure a 'link' to the virtual SCSI serving partition, and then configure the virtual SCSI serving partition itself. You create a 'link' between the virtual SCSI client and server slots using the HMC. You can configure a virtual SCSI server on either Virtual I/O Server (VIOS) or IBM i, depending on which model and options you have. Once you have your system configured, you need to Activate from the HMC or power it on. Depending on what type of install you are doing, you may need to configure SMS to correctly boot the system into the installation program. 11.5. RAID and Other Disk Devices Red Hat Enterprise Linux 6 uses mdraid instead of dmraid for installation onto Intel BIOS RAID sets. These sets are detected automatically, and devices with Intel ISW metadata are recognized as mdraid instead of dmraid. Note that the device node names of any such devices under mdraid are different from their device node names under dmraid. Therefore, special precautions are necessary when you migrate systems with Intel BIOS RAID sets. Local modifications to /etc/fstab, /etc/crypttab or other configuration files which refer to devices by their device node names will not work in Red Hat Enterprise Linux 6. Before migrating these files, you must therefore edit them to replace device node paths with device UUIDs instead. You can find the UUIDs of devices with the blkid command. RAID, or Redundant Array of Independent Disks, allows a group, or array, of drives to act as a single device. Configure any RAID functions provided by the mainboard of your computer, or attached controller cards, before you begin the installation process. Each active RAID array appears as one drive within Red Hat Enterprise Linux. On systems with more than one hard drive you may configure Red Hat Enterprise Linux to operate several of the drives as a Linux RAID array without requiring any additional hardware. 11.5.3. FireWire and USB Disks Some FireWire and USB hard disks may not be recognized by the Red Hat Enterprise Linux installation system. If configuration of these disks at installation time is not vital, disconnect them to avoid any confusion. You can connect and configure external FireWire and USB hard disks after installation. Most such devices are recognized by the kernel and available for use at that time. 11.6. Do You Have Enough Disk Space?Nearly every modern-day operating system (OS) uses disk partitions, and Red Hat Enterprise Linux is no exception. When you install Red Hat Enterprise Linux, you may have to work with disk partitions. If you have not worked with disk partitions before (or need a quick review of the basic concepts), refer to Appendix A, An Introduction to Disk Partitions before proceeding. The disk space used by Red Hat Enterprise Linux must be separate from the disk space used by other OSes you may have installed on your system. Before you start the installation process, you must 11.7. Choose a boot methodInstalling from a DVD requires that you have purchased a Red Hat Enterprise Linux product, you have a Red Hat Enterprise Linux 6 DVD, and you have a DVD drive on a system that supports booting from it. Refer to Chapter 2, Making Media for instructions to make an installation DVD. Other than booting from an installation DVD, you can also boot the Red Hat Enterprise Linux installation program from minimal boot media in the form of a bootable CD. After you boot the system with boot CD, you complete the installation from a different installation source, such as a local hard drive or a location on a network. Refer to Section 2.2, "Making Minimal Boot Media" for instructions on making boot CDs. Chapter 12. Preparing for Installation12.1. Preparing for a Network InstallationThe eHEA module fails to initialize if 16 GB huge pages are assigned to a system or partition and the kernel command line does not contain the huge page parameters. Therefore, when you perform a network installation through an IBM eHEA ethernet adapter, you cannot assign huge pages to the system or partition during the installation. Large pages should work. Make sure no installation DVD (or any other type of DVD or CD) is in your system's CD or DVD drive if you are performing a network-based installation. Having a DVD or CD in the drive might cause unexpected errors. Ensure that you have boot media available on CD, DVD, or a USB storage device such as a flash drive. The Red Hat Enterprise Linux installation medium must be available for either a network installation (via NFS, FTP, HTTP, or HTTPS) or installation via local storage. Use the following steps if you are performing an NFS, FTP, HTTP, or HTTPS installation. The NFS, FTP, HTTP, or HTTPS server to be used for installation over the network must be a separate, network-accessible server. It must provide the complete contents of the installation DVD-ROM. anaconda has the ability to test the integrity of the installation media. It works with the DVD, hard drive ISO, and NFS ISO installation methods. Red Hat recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned DVDs). To use this test, type the following command at the yaboot: prompt: linux mediacheck
The public directory used to access the installation files over FTP, NFS, HTTP, or HTTPS is mapped to local storage on the network server. For example, the local directory /var/www/inst/rhel6 on the network server can be accessed as http://network.server.com/inst/rhel6. In the following examples, the directory on the installation staging server that will contain the installation files will be specified as /location/of/disk/space/publicly_available_directory. For example, /location/of/disk/space/var/isos. /publicly_available_directory/var/www/html/rhel6, for an HTTP install. In the following, you will require an ISO image. An ISO image is a file containing an exact copy of the content of a DVD. To create an ISO image from a DVD use the following command: dd if=/dev/dvd of=/path_to_image/name_of_image.iso
where dvd is your DVD drive device, name_of_image is the name you give to the resulting ISO image file, and path_to_image is the path to the location on your system where the resulting ISO image will be stored. 12.1.1. Preparing for FTP, HTTP, and HTTPS installationExtract the files from the ISO image of the installation DVD and place them in a directory that is shared over FTP, HTTP, or HTTPS. Next, make sure that the directory is shared via FTP, HTTP, or HTTPS, and verify client access. Test to see whether the directory is accessible from the server itself, and then from another machine on the same subnet to which you will be installing. 12.1.2. Preparing for an NFS installationFor NFS installation it is not necessary to extract all the files from the ISO image. It is sufficient to make the ISO image itself, the install.img file, and optionally the product.img file available on the network server via NFS. Transfer the ISO image to the NFS exported directory. On a Linux system, run: mv /path_to_image/name_of_image.iso /publicly_available_directory/
where path_to_image is the path to the ISO image file, name_of_image is the name of the ISO image file, and publicly_available_directory is a directory that is available over NFS or that you intend to make available over NFS. Use a SHA256 checksum program to verify that the ISO image that you copied is intact. Many SHA256 checksum programs are available for various operating systems. On a Linux system, run: $ sha256sum name_of_image.iso
where name_of_image is the name of the ISO image file. The SHA256 checksum program displays a string of 64 characters called a hash. Compare this hash to the hash displayed for this particular image on the Download Software page on the Red Hat Network (refer to Chapter 1, Obtaining Red Hat Enterprise Linux). The two hashes should be identical. Copy the images/ directory from inside the ISO image to the same directory in which you stored the ISO image file itself. Enter the following commands: mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o loop,rocp -pr /mount_point/images /publicly_available_directory/umount /mount_point
where path_to_imagename_of_imagemount_point mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,rocp -pr /mnt/tmp/images /var/isos/umount /mnt/tmp
The ISO image file and an images/ directory are now present, side-by-side, in the same directory. Verify that the images/ directory contains at least the install.img file, without which installation cannot proceed. Optionally, the images/ directory should contain the product.img file, without which only the packages for a Minimal installation will be available during the package group selection stage (refer to Section 16.19, "Package Group Selection"). install.img and product.img must be the only files in the images/ directory.
Ensure that an entry for the publicly available directory exists in the /etc/exports file on the network server so that the directory is available via NFS. To export a directory read-only to a specific system, use: /publicly_available_directory client.ip.address (ro)
To export a directory read-only to all systems, use: /publicly_available_directory * (ro)
On the network server, start the NFS daemon (on a Red Hat Enterprise Linux system, use /sbin/service nfs start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload). Be sure to test the NFS share following the directions in the Red Hat Enterprise Linux Deployment Guide. Refer to your NFS documentation for details on starting and stopping the NFS server.
anaconda has the ability to test the integrity of the installation media. It works with the DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned DVDs). To use this test, type the following command at the boot: prompt: linux mediacheck
12.2. Preparing for a Hard Drive InstallationHard drive installations only work from ext2, ext3, ext4, or FAT file systems. You cannot use a hard drives formatted for any other file system as an installation source for Red Hat Enterprise Linux. To check the file system of a hard drive partition on a Windows operating system, use the Disk Management tool. To check the file system of a hard drive partition on a Linux operating system, use the fdisk tool. You cannot use ISO files on partitions controlled by LVM (Logical Volume Management). Use this option to install Red Hat Enterprise Linux on systems without a DVD drive or network connection. Hard drive installations use the following files: an ISO image of the installation DVD. An ISO image is a file that contains an exact copy of the content of a DVD. an install.img file extracted from the ISO image. optionally, a product.img file extracted from the ISO image.
Ensure that you have boot media available on CD, DVD, or a USB storage device such as a flash drive. To prepare a hard drive as an installation source, follow these steps: Obtain an ISO image of the Red Hat Enterprise Linux installation DVD (refer to Chapter 1, Obtaining Red Hat Enterprise Linux). Alternatively, if you have the DVD on physical media, you can create an image of it with the following command on a Linux system: dd if=/dev/dvd of=/path_to_image/name_of_image.iso
where dvd is your DVD drive device, name_of_image is the name you give to the resulting ISO image file, and path_to_image is the path to the location on your system where the resulting ISO image will be stored. Transfer the ISO image to the hard drive. The ISO image must be located on a hard drive that is either internal to the computer on which you will install Red Hat Enterprise Linux, or on a hard drive that is attached to that computer by USB. Use a SHA256 checksum program to verify that the ISO image that you copied is intact. Many SHA256 checksum programs are available for various operating systems. On a Linux system, run: $ sha256sum name_of_image.iso
where name_of_image is the name of the ISO image file. The SHA256 checksum program displays a string of 64 characters called a hash. Compare this hash to the hash displayed for this particular image on the Download Software page on the Red Hat Network (refer to Chapter 1, Obtaining Red Hat Enterprise Linux). The two hashes should be identical. Copy the images/ directory from inside the ISO image to the same directory in which you stored the ISO image file itself. Enter the following commands: mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o loop,rocp -pr /mount_point/images /publicly_available_directory/umount /mount_point
where path_to_imagename_of_imagemount_point mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,rocp -pr /mnt/tmp/images /var/isos/umount /mnt/tmp
The ISO image file and an images/ directory are now present, side-by-side, in the same directory. Verify that the images/ directory contains at least the install.img file, without which installation cannot proceed. Optionally, the images/ directory should contain the product.img file, without which only the packages for a Minimal installation will be available during the package group selection stage (refer to Section 9.18, "Package Group Selection"). install.img and product.img must be the only files in the images/ directory.
anaconda has the ability to test the integrity of the installation media. It works with the DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned DVDs). To use this test, type the following command at the boot: prompt: linux mediacheck
Chapter 13. Updating drivers during installation on IBM Power Systems serversIn most cases, Red Hat Enterprise Linux already includes drivers for the devices that make up your system. However, if your system contains hardware that has been released very recently, drivers for this hardware might not yet be included. Sometimes, a driver update that provides support for a new device might be available from Red Hat or your hardware vendor on a driver disc that contains rpm packages. Typically, the driver disc is available for download as an ISO image file. Often, you do not need the new hardware during the installation process. For example, if you use a DVD to install to a local hard drive, the installation will succeed even if drivers for your network card are not available. In situations like this, complete the installation and add support for the piece of hardware afterward - refer to Section 35.1.1, "Driver update rpm packages" for details of adding this support. In other situations, you might want to add drivers for a device during the installation process to support a particular configuration. For example, you might want to install drivers for a network device or a storage adapter card to give the installer access to the storage devices that your system uses. You can use a driver disc to add this support during installation in one of two ways: place the ISO image file of the driver disc in a location accessible to the installer: on a local hard drive a USB flash drive
create a driver disc by extracting the image file onto:
If Red Hat, your hardware vendor, or a trusted third party told you that you will require a driver update during the installation process, choose a method to supply the update from the methods described in this chapter and test it before beginning the installation. Conversely, do not perform a driver update during installation unless you are certain that your system requires it. Although installing an unnecessary driver update will not cause harm, the presence of a driver on a system for which it was not intended can complicate support. 13.1. Limitations of driver updates during installationUnfortunately, some situations persist in which you cannot use a driver update to provide drivers during installation: - Devices already in use
You cannot use a driver update to replace drivers that the installation program has already loaded. Instead, you must complete the installation with the drivers that the installation program loaded and update to the new drivers after installation. - Devices with an equivalent device available
Because all devices of the same type are initialized together, you cannot update drivers for a device if the installation program has loaded drivers for a similar device. For example, consider a system that has two different network adapters, one of which has a driver update available. The installation program will initialize both adapters at the same time, and therefore, you will not be able to use this driver update. Again, complete the installation with the drivers loaded by the installation program and update to the new drivers after installation, or use an initial RAM disk driver update.
13.2. Preparing for a driver update during installationIf a driver update is necessary and available for your hardware, Red Hat or a trusted third party such as the hardware vendor will typically provide it in the form of an image file in ISO format. Some methods of performing a driver update require you to make the image file available to the installation program, while others require you to use the image file to make a driver update disk: - Methods that use the image file itself
local hard drive USB flash drive
- Methods that use a driver update disk produced from an image file
13.2.1. Preparing to use a driver update image file13.2.1.1. Preparing to use an image file on local storageTo make the ISO image file available on local storage, such as a hard drive or USB flash drive, you must first determine whether you want to install the updates automatically or select them manually. For manual installations, copy the file onto the storage device. You can rename the file if you find it helpful to do so, but you must not change the filename extension, which must remain .iso. In the following example, the file is named dd.iso: Note that if you use this method, the storage device will contain only a single file. This differs from driver discs on formats such as CD and DVD, which contain many files. The ISO image file contains all of the files that would normally be on a driver disc. For automatic installations, you will need to extract the ISO to the root directory of the storage device rather than simply copy it. Copying the ISO is only effective for manual installations. You must also change the file system label of the device to OEMDRV. 13.2.2. Preparing a driver discYou can create a driver update disc on CD or DVD. 13.2.2.1. Creating a driver update disc on CD or DVDCD/DVD Creator is part of the GNOME desktop. If you use a different Linux desktop, or a different operating system altogether, you will need to use another piece of software to create the CD or DVD. The steps will be generally similar. Make sure that the software that you choose can create CDs or DVDs from image files. While this is true of most CD and DVD burning software, exceptions exist. Look for a button or menu entry labeled burn from image or similar. If your software lacks this feature, or you do not select it, the resulting disc will hold only the image file itself, instead of the contents of the image file. Use the desktop file manager to locate the ISO image file of the driver disc, supplied to you by Red Hat or your hardware vendor.
Right-click on this file and choose Write to disc. You will see a window similar to the following:
Click the Write button. If a blank disc is not already in the drive, CD/DVD Creator will prompt you to insert one.
After you burn a driver update disc CD or DVD, verify that the disc was created successfully by inserting it into your system and browsing to it using the file manager. You should see a single file named rhdd3 and a directory named rpms: If you see only a single file ending in .iso, then you have not created the disc correctly and should try again. Ensure that you choose an option similar to burn from image if you use a Linux desktop other than GNOME or if you use a different operating system. 13.2.3. Preparing an initial RAM disk updateThis is an advanced procedure that you should consider only if you cannot perform a driver update with any other method. The Red Hat Enterprise Linux installation program can load updates for itself early in the installation process from a RAM disk - an area of your computer's memory that temporarily behaves as if it were a disk. You can use this same capability to load driver updates. To perform a driver update during installation, your computer must be able to boot from a yaboot installation server, and you must have one available on your network. Refer to Chapter 30, Setting Up an Installation Server for instructions on using a yaboot installation server. To make the driver update available on your installation server: Place the driver update image file on your installation server. Usually, you would do this by downloading it to the server from a location on the Internet specified by Red Hat or your hardware vendor. Names of driver update image files end in .iso. Copy the driver update image file into the /tmp/initrd_update directory. Rename the driver update image file to dd.img. At the command line, change into the /tmp/initrd_update directory, type the following command, and press Enter: find . | cpio --quiet -o -H newc | gzip -9 >/tmp/initrd_update.img Copy the file /tmp/initrd_update.img into the directory the holds the target that you want to use for installation. This directory is placed under the /var/lib/tftpboot/yaboot/ directory. For example, /var/lib/tftpboot/yaboot/rhel6/ might hold the yaboot installation target for Red Hat Enterprise Linux 6. Edit the /var/lib/tftpboot/yaboot/yaboot.conf file to include an entry that includes the initial RAM disk update that you just created, in the following format: image=target/vmlinuzlabel=target-ddinitrd=target/initrd.img,target/dd.img Where target is the target that you want to use for installation.
Example 13.1. Preparing an initial RAM disk update from a driver update image file In this example, driver_update.iso is a driver update image file that you downloaded from the Internet to a directory on your installation server. The target on your installation server that you want to boot from is located in /var/lib/tftpboot/yaboot/rhel6/ At the command line, change to the directory that holds the file and enter the following commands: $ cp driver_update.iso /tmp/initrd_update/dd.img$ cd /tmp/initrd_update$ find . | cpio --quiet -c -o -H newc | gzip -9 >/tmp/initrd_update.img$ cp /tmp/initrd_update.img /tftpboot/yaboot/rhel6/dd.img Edit the /var/lib/tftpboot/yaboot/yaboot.conf file and include the following entry: image=rhel6/vmlinuzlabel=rhel6-ddinitrd=rhel6/initrd.img,rhel6/dd.img 13.3. Performing a driver update during installationYou can perform a driver update during installation in the following ways: let the installer automatically find a driver update disk. let the installer prompt you for a driver update. use a boot option to specify a driver update disk.
13.3.1. Let the installer automatically find a driver update diskAttach a block device with the filesystem label OEMDRV before starting the installation process. The installer will automatically examine the device and load any driver updates that it detects and will not prompt you during the process. Refer to Section 13.2.1.1, "Preparing to use an image file on local storage" to prepare a storage device for the installer to find. 13.3.2. Let the installer prompt you for a driver updateBegin the installation normally for whatever method you have chosen. If the installer cannot load drivers for a piece of hardware that is essential for the installation process (for example, if it cannot detect any network or storage controllers), it prompts you to insert a driver update disk:
13.3.3. Use a boot option to specify a driver update diskThis method only works to introduce completely new drivers, not to update existing drivers. Type linux dd at the boot prompt at the start of the installation process and press Enter. The installer prompts you to confirm that you have a driver disk:
Insert the driver update disk that you created on CD, DVD, or USB flash drive and select Yes. The installer examines the storage devices that it can detect. If there is only one possible location that could hold a driver disk (for example, the installer detects the presence of a DVD drive, but no other storage devices) it will automatically load any driver updates that it finds at this location.
13.3.4. Select an installation server target that includes a driver updateConfigure the computer to boot from the network interface by selecting Select Boot Options in the SMS menu, then Select Boot/Install Device. Finally, select your network device from the list of available devices. In the yaboot installation server environment, choose the boot target that you prepared on your installation server. For example, if you labeled this environment rhel6-dd in the /var/lib/tftpboot/yaboot/yaboot.conf file on your installation server, type rhel6-dd at the prompt and press Enter.
13.4. Specifying the location of a driver update image file or driver update diskIf the installer detects more than one possible device that could hold a driver update, it prompts you to select the correct device. If you are not sure which option represents the device on which the driver update is stored, try the various options in order until you find the correct one. If the device that you choose contains no suitable update media, the installer will prompt you to make another choice. If you made a driver update disk on CD, DVD, or USB flash drive, the installer now loads the driver update. However, if the device that you selected is a type of device that could contain more than one partition (whether the device currently has more than one partition or not), the installer might prompt you to select the partition that holds the driver update. The installer prompts you to specify which file contains the driver update: Expect to see these screens if you stored the driver update on an internal hard drive or on a USB storage device. You should not see them if the driver update is on a CD or DVD. Regardless of whether you are providing a driver update in the form of an image file or with a driver update disk, the installer now copies the appropriate update files into a temporary storage area (located in system RAM and not on disk). The installer might ask whether you would like to use additional driver updates. If you select Yes, you can load additional updates in turn. When you have no further driver updates to load, select No. If you stored the driver update on removable media, you can now safely eject or disconnect the disk or device. The installer no longer requires the driver update, and you can re-use the media for other purposes. Chapter 14. Booting the InstallerBecause Power Systems servers primarily use text consoles, anaconda will not automatically start a graphical installation. However, the graphical installer offers more features and customization and is recommended if your system has a graphical display. On some machines yaboot may not boot, returning the error message: Cannot load initrd.img: Claim failed for initrd memory at 02000000 rc=ffffffff
To work around this issue, change real-base to c00000. You can obtain the value of real-base from the OpenFirmware prompt with the printenv command and set the value with the setenv command. To boot an IBM System p system from a DVD, you must specify the install boot device in the System Management Services (SMS) menu. To enter the System Management Services GUI, press the 1 key during the boot process when you hear the chime sound. This brings up a graphical interface similar to the one described in this section. On a text console, press 1 when the self test is displaying the banner along with the tested components: Once in the SMS menu, select the option for . In that menu, specify Select Install or Boot a Device. There, select CD/DVD, and then the bus type (in most cases SCSI). If you are uncertain, you can select to view all devices. This scans all available buses for boot devices, including network adapters and hard drives. Finally, select the device containing the installation DVD. Yaboot is loaded from this device and you are presented with a boot: prompt. To begin a graphical installation, pass the vnc boot option now. Otherwise. press Enter or wait for the timeout to expire for the installation to begin. Use yaboot with vmlinuz and ramdisk to boot your system over a network. You cannot use the ppc64.img to boot over a network; the file is too large for TFTP. The installer displays the boot: prompt. For example: IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM /Elapsed time since release of system processors: 276 mins 49 secsSystem has 128 Mbytes in RMAConfig file read, 227 bytesWelcome to the 64-bit Red Hat Enterprise Linux 6.0 installer!Hit <TAB> for boot options.Welcome to yaboot version 1.3.14 (Red Hat 1.3.14-35.el6)Enter "help" to get some basic usage informationboot: To proceed with installation, type linux and press Enter. You can also specify boot options at this prompt; refer to Chapter 28, Boot Options for more information. For example, to use the installer to rescue a previously installed system, type linux rescue and press Enter. The following example shows the vnc boot option being passed to begin a graphical installation: boot:* linux boot: linux vnc Please wait, loading kernel... 14.2. Installing from a Different Source You can install Red Hat Enterprise Linux from the ISO images stored on hard disk, or from a network using NFS, FTP, HTTP, or HTTPS methods. Experienced users frequently use one of these methods because it is often faster to read data from a hard disk or network server than from a DVD. The following table summarizes the different boot methods and recommended installation methods to use with each: Table 14.1. Boot methods and installation sources | Boot method | Installation source |
|---|
| Installation DVD | DVD, network, or hard disk | | Installation USB flash drive | Installation DVD, network, or hard disk | | Minimal boot CD or USB, rescue CD | Network or hard disk |
14.3. Booting from the network using a yaboot installation serverTo boot with a yaboot installation server, you need a properly configured server, and a network interface in your computer that can support an installation server. For information on how to configure an installation server, refer to Chapter 30, Setting Up an Installation Server. Configure the computer to boot from the network interface by selecting Select Boot Options in the SMS menu, then Select Boot/Install Device. Finally, select your network device from the list of available devices. Once you properly configure booting from an installation server, the computer can boot the Red Hat Enterprise Linux installation system without any other media. To boot a computer from a yaboot installation server: Ensure that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on. Switch on the computer. A menu screen appears. Press the number key that corresponds to the desired option.
If your PC does not boot from the network installation server, ensure that the SMS is configured to boot first from the correct network interface. Refer to your hardware documentation for more information. |
| |
