Part II. IBM Power Systems — Installation and Booting
Procedure 12.3. Disabling Graphical Boot Temporarily
1. Start your computer and wait until the boot loader menu appears. If you set your boot loader timeout period to 0, hold down the Esc key to access it.
2. When the boot loader menu appears, use your cursor keys to highlight the entry you want to boot and press the e key to edit this entry's options.
3. In the list of options, find the kernel line - that is, the line beginning with the keyword linux. On this line, locate the rhgb option and delete it. The option may not be immediately visible; use the cursor keys to scroll up and down.
4. Press F10 or Ctrl+X to boot your system with the edited options.
If the system started successfully, you can log in normally. Then you will need to disable the graphical boot permanently - otherwise you will have to perform the previous procedure every time the system boots. To permanently change boot options, do the following.
Procedure 12.4 . Disabling Graphical Boot Permanently
1. Log in to the root account using the su - command:
$ su
-2. Open the /etc/default/grub configuration file using a plain text editor such as vim.
3. Within the grub file, locate the line beginning with GRUB_CMDLINE_LINUX. The line should look similar to the following:
GRUB_CMDLINE_LINUX="rd.lvm.lv=rhel/root rd.md=0 rd.dm=0 vconsole.keymap=us $([
-x /usr/sbin/rhcrashkernel-param ] && /usr/sbin/rhcrashkernel-param || :) rd.luks=0 vconsole.font=latarcyrheb-sun16 rd.lvm.lv=vg_rhel/swap rhgb quiet"
On this line, delete the rhgb option.
4. Save the edited configuration file.
5. Refresh the boot loader configuration by executing the following command:
# grub2-mkconfig --output=/boot/grub2/grub.cfg
After you finish this procedure, you can reboot your computer. Red Hat Enterprise Linux will not use the graphical boot sequence any more. If you wish to enable graphical boot, follow the same procedure, add the rhgb option to the GRUB_CMDLINE_LINUX line in the /etc/default/grub file and refresh the boot loader configuration again using the grub2-m kconfig command.
See the Red Hat Enterprise Linux 7 System Administrator's Guide for more information about working with the GRUB2 boot loader.
12.3.2. Booting into a Graphical Environment
If you have installed the X Window System but are not seeing a graphical desktop environment once you log into your system, you can start it manually using the startx command. Note, however, that this is just a one-time fix and does not change the log in process for future log ins.
To set up your system so that you can log in at a graphical login screen, you must change the default systemd target to graphical.target. When you are finished, reboot the computer. You will presented with a graphical login prompt after the system restarts.
Procedure 12.5. Setting Graphical Login as Default
1. Open a shell prompt. If you are in your user account, become root by typing the su - command.
2. Change the default target to graphical.target. To do this, execute the following command:
# systemctl set-default graphical.target
Graphical login is now enabled by default - you will be presented with a graphical login prompt after the next reboot. If you want to reverse this change and keep using the text-based login prompt, execute the following command as root:
# systemctl set-default multi-user.target
For more information about targets in systemd, see the Red Hat Enterprise Linux 7 System Administrator's Guide.
12.3.3. No Graphical User Interface Present
If you are having trouble getting X (the X Window System) to start, it is possible that it has not been installed. Some of the pre-set base environments you can select during the installation, such as Minim al install or Web Server, do not include a graphical interface - it has to be installed manually.
If you want X, you can install the necessary packages afterwards. See the Knowledgebase article at https://access.redhat.com/site/solutions/5238 for information on installing a graphical desktop environment.
12.3.4. X Server Crashing After User Logs In
If you are having trouble with the X server crashing when a user logs in, one or more of your file systems may be full (or nearly full). To verify that this is the problem you are experiencing, execute the following command:
$ df -h
The output will help you diagnose which partition is full - in most cases, the problem will be on the /hom e
partition. A sample output of the df command may look similar to the following:
In the above example, you can see that the /hom e partition is full, which causes the crash. You can make some room on the partition by removing unneeded files. After you free up some disk space, start X using the startx command.
For additional information about df and an explanation of the options available (such as the -h option used in this example), see the df(1) man page.
12.3.5. Is Your System Displaying Signal 11 Errors?
A signal 11 error, commonly known as a segmentation fault, means that a program accessed a memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware.
If you receive a fatal signal 11 error during the installation, first make sure you are using the most recent installation images, and let Anaconda verify them to make sure they are not corrupted. Bad installation media (such as an improperly burned or scratched optical disk) are a common cause of signal 11 errors.
Verifying the integrity of the installation media is recommended before every installation.
For information about obtaining the most recent installation media, see Chapter 1, Downloading Red Hat Enterprise Linux. To perform a media check before the installation starts, append the rd.live.check boot option at the boot menu. See Section 20.2.2, “Verifying Boot Media” for details.
Other possible causes are beyond this document's scope. Consult your hardware manufacturer's documentation for more information.
12.3.6. Unable to IPL from Network Storage Space (*NWSSTG)
If you are experiencing difficulties when trying to IPL from Network Storage Space (*NWSSTG), in most cases the reason is a missing PReP partition. In this case, you must reinstall the system and make sure to create this partition during the partitioning phase or in the Kickstart file.