14.3. Problems After Installation
14.3.1. Trouble With the Graphical Boot Sequence
Procedure 14.3. Disabling Graphical Boot Temporarily
- 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.
- 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.
- In the list of options, find the kernel line - that is, the line beginning with the keyword
linux. On this line, locate the
rhgboption and delete it. The option might not be immediately visible; use the cursor keys to scroll up and down.
- Press F10 or Ctrl+X to boot your system with the edited options.
Procedure 14.4. Disabling Graphical Boot Permanently
- Log in to the
rootaccount using the
- Use the grubby tool to find the default GRUB2 kernel:
- Use the grubby tool to remove the
rhgbboot option from the default kernel, identified in the last step, in your GRUB2 configuration. For example:
#grubby --remove-args="rhgb" --update-kernel /boot/vmlinuz-3.10.0-229.4.2.el7.ppc64
--remove-args="rhgb"parameter with the
--args="rhgb"paramter. This will restore the
rhgbboot option to the default kernel in your GRUB2 configuration.
14.3.2. Booting into a Graphical Environment
startxcommand. Note, however, that this is just a one-time fix and does not change the log in process for future log ins.
graphical.target. When you are finished, reboot the computer. You will presented with a graphical login prompt after the system restarts.
Procedure 14.5. Setting Graphical Login as Default
- Open a shell prompt. If you are in your user account, become root by typing the
- Change the default target to
graphical.target. To do this, execute the following command:
systemctl set-default graphical.target
systemctl set-default multi-user.target
14.3.3. No Graphical User Interface Present
14.3.4. X Server Crashing After User Logs In
/homepartition. The following is a sample output of the
Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_rhel-root 20G 6.0G 13G 32% / devtmpfs 1.8G 0 1.8G 0% /dev tmpfs 1.8G 2.7M 1.8G 1% /dev/shm tmpfs 1.8G 1012K 1.8G 1% /run tmpfs 1.8G 0 1.8G 0% /sys/fs/cgroup tmpfs 1.8G 2.6M 1.8G 1% /tmp /dev/sda1 976M 150M 760M 17% /boot /dev/dm-4 90G 90G 0 100% /home
/homepartition 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
dfand an explanation of the options available (such as the
-hoption used in this example), see the
14.3.5. Is Your System Displaying Signal 11 Errors?
rd.live.checkboot option at the boot menu. See Section 23.2.2, “Verifying Boot Media” for details.
14.3.6. Unable to IPL from Network Storage Space (*NWSSTG)
PRePpartition. In this case, you must reinstall the system and make sure to create this partition during the partitioning phase or in the Kickstart file.
14.3.7. The GRUB2
next_entry variable can behave unexpectedly in a virtualized environment
next_entrygrub environment variable after a system reboot. The SLOF firmware does not support block writes at boot time by design thus the bootloader is unable to clear this variable at boot time.