Booting Into PC-BSD®/9.2
After installation, PC-BSD® will reboot and you will be prompted to configure your system and to login to a desktop.
Once the first boot is complete, the installer will attempt to set the optimal display settings. A pop-up menu will ask if you would like to accept these settings. Simply click "Yes" to continue. PC-BSD® will then play a short video before proceeding to the first post configuration screen. You can press Esc to skip the video. If you wish to watch the video at a later time, it is located in /usr/local/share/pcbsd/movies/.
Read through the rest of this section if your system hangs at boot time or if you have problems setting the display settings. If you are dual booting and your other operating system was not automatically added to the graphical boot menu by the installer, refer to Dual Booting.
Interrupting the Boot to Access the Boot Menu
By default, the graphical PC-BSD® bootloader menu shown in Figure 4.1a is not displayed at boot time.
This menu is used to display the installation of PC-BSD®, any boot environments created with Boot Manager, and other operating systems installed on a dual-boot system.To access this menu, you have to be quick. As soon as the boot process starts and you see a "GRUB loading" message in the upper left corner, press Esc. After the system boots, you can increase the timer value in Boot Manager if you find that the boot delay is too quick.
Once you access the graphical menu, it will pause for a few seconds then continue to boot PC-BSD®. If you wish to select a different operating system or specify how PC-BSD® boots, press a key to pause this screen. If multiple operating systems are available and you want to boot into PC-BSD®, make sure it is highlighted and press enter. This will load the PC-BSD® boot options screen shown in Figure 4.1b.
The following boot options are available:
- Normal Bootup: continues to boot PC-BSD®.
- Single User Mode: advanced users can select this option to fix critical system failures.
- Verbose Mode: select this option if you would like to see more detailed messages during the boot process. This can be useful if you are troubleshooting a piece of hardware.
- Run the Display Wizard: if you are unable to access the GUI due to a display setting, enable this option to boot into the display settings wizard.
- Run X in vesa mode: try this option if the screen goes black or the system freezes when booting into PC-BSD®.
Use the arrow keys to select an option then press enter to boot using that option.This menu is provided by GRUB. If you are familiar with editing GRUB, you can press e to access the GRUB editor or c to access the GRUB command line.
If Your Display is Not Automatically Detected
If the optimal display settings can not be determined during first boot, if you select “No” in the “Confirm Resolution” screen when asked to confirm the display settings, or if you select “Run the Display Wizard” from the boot menu, the “Display Settings” screen shown in Figure 4.1c will launch.
If you change any display settings, click the "Apply" button for the settings to be tested. If anything goes wrong during testing, you will be taken back to the "Display Settings" screen so that you can try another setting. Once you are happy with the tested setting, click the "Yes" button to save the setting and to proceed.
PC-BSD® uses a "fast boot" script to decrease the amount of time that it takes the system to boot to the login screen. When this script is enabled, which is the default, services are started in the background and the boot process does not wait for confirmation from each service as it starts. This is referred to as delayed mode.
The fast boot script is controlled by these lines in /etc/rc.conf.pcbsd:
fastboot_earlyrc="/etc/rc.d/moused /etc/rc.d/pefs /usr/local/etc/rc.d/dbus /usr/local/etc/rc.d/hald /usr/local/etc/rc.d/gdm"
The logfile /var/log/rc_delay.log shows the startup messages for the services which were started in delayed mode. If this log indicates that a delayed mode service is not starting correctly, become the superuser, copy the fastboot_earlyrc line to /etc/rc.conf, remove that service from that line, and reboot to see if that fixes the problem.
If a faster boot time is not important to you and you prefer to watch each service as it starts at boot time, you can disable fast boot by adding fastboot_enable="NO" to /etc/rc.conf.