PowerPC: Virtual Open Firmware

Before the kernel is started, PowerPC systems are controlled by one of two types of read-only-memory firmware:

• Conventional Open Firmware (OF) - built into the PowerPC system.
• Virtual Open Firmware (VOF) - an implementation provided by SunSoft for PowerPC systems without built-in firmware. VOF is loaded onto fdisk partition 0x41 during installation.

PowerPC: The Boot Process

This section describes the details of the boot process for PowerPC systems with conventional Open Firmware and Virtual Open Firmware.

PowerPC: Conventional Firmware

PowerPC: Open Firmware

PowerPC: The Boot Process Details

The following boot process information describes the illustrations on the previous pages.

PowerPC: The Diagnostic Monitor Phase

When the system is powered on, a PowerPC system runs self-test diagnostics to verify that the system's hardware and memory are operational.

On systems with OF ...

• Control is transferred to the resident OF.
• The OF builds a device tree consisting of both permanently installed devices and plug-in devices.
• The OF loads and executes the contents of the active DOS12 fdisk partition, which is bootblk, the primary boot program.

On systems with VOF ...

• VOF, which is loaded in fdisk partition 0x41, is executed.
• VOF builds a device tree consisting of both permanently installed devices and plug-in devices.
• VOF loads and executes boot block code from the active DOS12 fdisk partition.

PowerPC: Boot Programs Phase

During the boot programs phase, the primary boot program loads and executes ufsboot, the secondary boot program. The ufsboot program loads and executes the kernel.

PowerPC: Kernel Initialization Phase

During the kernel initialization phase, the kernel initializes itself and begins loading modules, using ufsboot to read the files. When the kernel has loaded enough modules to mount the root file system, it unmaps the ufsboot program and continues, using its own resources.

The kernel creates a user process and starts the /sbin/init process, which starts other processes by reading the /etc/inittab file.

PowerPC: The init Phase

During the init phase, the /sbin/init process starts the run control (rc) scripts, which execute a series of other scripts. These scripts (sbin/rc*) check and mount file systems, start various processes, and perform system maintenance tasks.

PowerPC: The VOF Interface

The VOF has commands and configuration variables--similar to a SPARC system's PROM monitor--that are used to either display or reset the way the system behaves before the operating system is loaded.

PowerPC: VOF Terminology

VOF terminology includes:

• Packages--Represent various support components, such as the obp-tftp package, that provide the protocols used by network device drivers.

  Packages can be activated to display their properties using the dev command.

• Properties--Describe hardware and software characteristics that users may display and modify.
• Device Aliases--Represent user-friendly names for the fully-qualified names for buses, manufacturer names, and unit addresses.

Table 4-1 describes some basic keys for using the VOF interface.

Table 4-1

Use ...	To ...
Enter	Execute VOF commands
Backspace	Erase previous characters
Control-U	Erase the current line

Use the following syntax to issue VOF commands:

ok command argument

Table 4-2 describes some helpful VOF commands.

Table 4-2

Command	Function
dev	Makes the specified device the active package.
.properties	Lists the properties of the active package.
help	Displays a list of VOF commands.
reset-all	Resets and reboots the system. This has the same effect as turning system power off and on.
show-devs	Prints the device tree of attached devices. Use this command to verify that devices are connected properly.
printenv	Displays configuration variables. See Table 4-3 for a description of configuration variables.
setenv config-variable value	Sets a configuration variable. See Table 4-3 for a description of configuration variables.
set-default config-variable	Resets a configuration variable back to the default setting.
set-defaults	Resets all configuration variables back to their default settings.

Table 4-3 describes some helpful configuration parameters.

Table 4-3

Configuration Parameter	Description
auto-boot?	If true, boot after turning power on or reset; otherwise, displays ok prompt.
boot-device	Sets default boot device.
boot-file	Sets default boot file.
input-device	Sets console input device.
output-device	Sets console output device.

PowerPC: Using the VOF Interface

The VOF interface is used to:

• Display information about default VOF settings.

  This is helpful when you want to determine how a system is set up--such as what is the default boot file or device. This information also helps you verify changed VOF settings.

• Change the default boot device.

  This is necessary when converting a standalone system to a diskless or Solstice^(TM) AutoClient^(TM) system that now needs to boot from the network rather than a local disk.

• Display a list of attached devices.

  After connecting devices it is a good idea to see if the system recognizes the new device before loading the operating system.

• List properties of attached devices.

Automatic Booting

The VOF interface is set up so a PowerPC system boots automatically by default. This means that if you use the init 0 or shutdown command to bring the system to the VOF prompt, the system will start booting within five seconds.

If more convenient, you can change the auto-boot? setting to false to have the system stop at the ok prompt after halting the system.

This section assumes that the auto-boot? setting is set to true, so you will have to press a key to stop the automatic boot process after you see the following message:

Automatically booting in 5 seconds. Hit any key to abort.

· PowerPC: How to Change the auto-boot Setting

1. Become root.

2. Halt the system by using the init 0 command.

# init 0 . . . Automatically booting in 5 seconds. Hit any key to abort.

3. Press any key to stop the automatic boot process after the Hit any key to abort prompt.

   The ok prompt is displayed.

4. Change the auto-boot setting to false by using the setenv command.

ok setenv auto-boot? false

In this command:

auto-boot?	Identifies the parameter for modifying the automatic boot process.
false	Identifies the value for disabling the automatic boot process.

5. Verify that the auto-boot setting has been changed.

ok printenv auto-boot?

Example--Changing the auto-boot Setting

In the following example, the auto-boot feature is disabled.

ok setenv auto-boot? false ok printenv auto-boot? auto-boot?="false" (default value = "true") ok

· PowerPC: How to Change the Default Boot Device

1. Become root.

2. Halt the system by using the init 0 command.

# init 0 . . . Automatically booting in 5 seconds. Hit any key to abort.

3. Press any key to stop the automatic boot process after the Hit any key to abort prompt.

   The ok prompt is displayed.

4. Change the boot-device setting by using the setenv command.

ok setenv boot-device value

In this command:

boot-device	Identifies the parameter for setting the device from which to boot.
value	Identifies the boot-device value. These are boot net for booting over the network, boot diskn for booting from a local disk.

Use the show-devs command if you need help identifying the disk number.

5. Verify the change by using the printenv command.

ok printenv boot-device

Example--Changing the Default Boot Device

In the following example, the default boot device is changed to boot net for booting over the network.

ok setenv boot-device boot net ok printenv boot-device boot-device="boot net" (default value "/pci/pci1000,1@1/disk@6,0:\solaris.elf") ok

· PowerPC: How to Reset the Default VOF Settings

1. Become root.

2. Halt the system by using the init 0 command.

# init 0 . . . Automatically booting in 5 seconds. Hit any key to abort.

3. Press any key to stop the automatic boot process after the Hit any key to abort prompt is displayed.

   The ok prompt is displayed.

4. Reset the default VOF settings by using the set-defaults command.

ok set-defaults

5. Verify the default VOF settings.

ok printenv

Example--Resetting Default VOF Settings

In the following example, the default VOF settings are reset.

ok set-defaults ok printenv auto-boot?="true" (default value = "true") boot-device="boot net" (default value = "/pci/pci1000,1@1/disk@6,0:,\solaris.elf") boot-file="" (default value = "") fdc-debug="00000000" (default value = 00000000) display-mode="" (default value = "") input-device="" (default value = "keyboard") little-endian?="true" (default value = "true") load-base="00000000" (default value = 00100000) output-device="" (default value = "screen") real-base="00007000" (default value = 00000000) real-mode?="false" (default value = "false") real-size="000f9000" (default value = 00100000) virt-base="fe000000" (default value = fe000000) virt-size="01f00000" (default value = 01f00000)

PowerPC: Booting a System

Table 4-4 describes the boot types covered in this chapter.

Table 4-4

Booting the System ...	Is Usually Done ...	See an Example On ...
To run level 3 (multiuser state)	After shutting down the system or performing some system hardware maintenance task. This is the default boot level where all resources are available and users can log into the system.	page 36
From the network to run level 3 (multiuser state)	After shutting down a diskless or AutoClient system to perform some system maintenance task.	page 40
To run level S (single-user state)	After performing some system maintenance task such as backing up a file system. At this level only some file systems are mounted and users cannot log into the system.	page 38
Interactively	After making temporary changes to the system file or the kernel for testing. This type of boot allows you to recover easily if there are problems with the system file or kernel by supplying an alternative path name to these files when prompted. Use the default settings for the other system prompts.	page 42
From local CD-ROM or the network for recovery purposes	To repair an important system file that is preventing the system from booting successfully. This type of boot is also used for installing (or upgrading) a new release of the operating system.	page 45
Reboot the system to run level 3 (multiuser state)	After changing kernel parameters in the /etc/system file.	page 34

· PowerPC: How to Reboot the System

1. Become root.

2. Reboot the system by using the init 6 command.

# init 6

3. Verify the system boots to run level 3.

   The login prompt is displayed when the boot process has finished successfully.

hostname console login:

Example--Rebooting a PowerPC System

In the following example, the system pluto rebooted to run level 3.

# init 6 # INIT: New run level: 6 The system is coming down. Please wait. System services are now being stopped. Print services stopped. Stopping BOOTP/DHCP Service. Stopping the syslog service. The system is down. syncing file systems... [8] [5] done Automatically booting in 5 seconds. Hit any key to abort. Boot device: /pci/pci1000,1@1/disk@6,0:,\solaris.elf Boot args: SunOS Release 5.5.1 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1996, Sun Microsystems, Inc. NOTICE: The serial number of this system must be set. configuring network interfaces: elx0. Hostname: pluto The system is coming up. Please wait. checking ufs filesystems /dev/rdsk/c0t6d0s7: is clean. NIS domainname is solar.com starting router discovery. starting rpc services: rpcbind keyserv ypbind kerbd done. Setting netmask of elx0 to 255.255.255.0 Setting default interface for multicast: add net 224.0.0.0: gateway pluto syslog service starting. Print services started. volume management starting. The system is ready. pluto console login:

· PowerPC: How to Boot a System to Run Level 3 (Multiuser State)

1. Boot to run level 3 by using the boot command.

ok boot

The automatic boot procedure displays a series of startup messages and brings the system to run level 3.

2. Verify the system boots to run level 3.

   The login prompt is displayed when the boot process has finished successfully.

hostname console login:

Example--Booting a PowerPC System to Run Level 3

In the following example, the system pluto is booted to run level 3.

ok boot Boot device: /pci/pci1000,1@1/disk@6,0:,\solaris.elf Boot args: SunOS Release 5.5.1 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1996, Sun Microsystems, Inc. NOTICE: The serial number of this system must be set. configuring network interfaces: elx0. Hostname: pluto The system is coming up. Please wait. checking ufs filesystems /dev/rdsk/c0t6d0s7: is clean. NIS domainname is solar.com starting router discovery. starting rpc services: rpcbind keyserv ypbind kerbd done. Setting netmask of elx0 to 255.255.255.0 Setting default interface for multicast: add net 224.0.0.0: gateway pluto syslog service starting. Print services started. volume management starting. The system is ready. pluto console login:

· PowerPC: How to Boot a System to Run Level S (Single-User State)

1. Boot the system to run level S by using the boot -s command.

ok boot -s

2. Enter the root password when the following message is displayed.

INIT: SINGLE USER MODE Type Ctrl-d to proceed with normal startup, (or give root password for system maintenance): xxx

3. To bring the system up to the multiuser state after the system maintenance task is performed, press Control-d.

4. Verify the system is at run level S by using the who -r command.

# who -r . run-level S Nov 10 13:59 S 0 ?

Example--Booting a PowerPC System to Run Level S

In the following example, the system pluto is booted to run level S.

ok boot -s Boot device: /pci/pci1000,1@1/disk@6,0:,\solaris.elf Boot args: -s SunOS Release 5.5.1 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1996, Sun Microsystems, Inc. DEBUG enabled NOTICE: The serial number of this system must be set. configuring network interfaces: elx0. Hostname: pluto INIT: SINGLE USER MODE Type Ctrl-d to proceed with normal startup, (or give root password for system maintenance): Entering System Maintenance Mode Sun Microsystems Inc. SunOS 5.5.1 May 1996 Perform some maintenance task # Press Control-d to bring the system to run level 3 INIT: New run level: 3 The system is coming up. Please wait. checking ufs filesystems /dev/rdsk/c0t6d0s7: is clean. NIS domainname is solar.com starting router discovery. starting rpc services: rpcbind keyserv ypbind kerbd done. Setting netmask of elx0 to 255.255.255.0 Setting default interface for multicast: add net 224.0.0.0: gateway pluto syslog service starting. Print services started. volume management starting. The system is ready. pluto console login:

· PowerPC: How to Boot a System From the Network

To boot a diskless or AutoClient system:

1. Use the boot net command to boot a system to run level 3 from the network.

ok boot net

2. Verify the system boots to run level 3.

   The login prompt is displayed when the boot process has finished successfully.

hostname console login:

Example--Booting a PowerPC System From the Network

In the following example, the system neptune is booted from the network to run level 3.

ok boot net Booting "81986F1B.PREP" from server 129.152.111.47 (venus) Read 156 kbytes Boot device: /pci/pci8086,484@0/COMS,3C509@i300 Boot args: hostname: neptune domainname: solar.com root server: venus SunOS Release 5.5.1 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1996, Sun Microsystems, Inc. DEBUG enabled NOTICE: The serial number of this system must be set. configuring network interfaces: elx0. The system is coming up. Please wait. starting rpc services: rpcbind keyserv ypbind kerbd done. Setting netmask of elx0 to 255.255.255.0 Setting default interface for multicast: add net 224.0.0.0: syslog service starting. Print services started. volume management starting. The system is ready. neptune console login:

· PowerPC: How to Boot a System Interactively

1. Boot the system interactively by using the boot -a command.

ok boot -a

2. Answer the system prompts as described in Table 4-5.

Table 4-5

If the System Displays ...	Do the Following ...
Enter filename [kernel/unix]:	Provide the name of another kernel to use for booting. Or, press Return to use the default kernel (/platform/'uname -m'/kernel/unix).
Name of default directory for modules [/platform/'uname -m'/kernel /platform/prep/kernel /kernel /usr/kernel]:	Provide an alternate path for the modules directory and press Return. Or, press Return to use the default modules directory path.
Name of system file [etc/system]:	Provide the name of an alternate system file and press Return. Or, press Return to use the default /etc/system file.
root filesystem type [ufs]:	Specify ufs for local disk booting or nfs fordiskless clients. Or, press Return to use the default root file system type, UFS.
Enter physical name of root device [physical_device_name]:	Provide an alternate device name and press Return. Or, press Return to use the default physical name of the root device.

3. Verify the system boots to run level 3.

   The login prompt is displayed when the boot process has finished successfully.

hostname console login:

Example--Booting a PowerPC System Interactively

In the following example, system pluto is booted interactively.

ok boot -a Boot device: /pci/pci1000,1@1/disk@6,0:,\solaris.elf Boot args: -a Enter filename [kernel/unix]: Enter default directory for modules [/platform/IBM,PPS_Model_6015/kernel /platform/prep/kernel /kernel /usr/kernel]: SunOS Release 5.5.1 [UNIX(R) System V Release 4.0] Copyright (c) 1983-1996, Sun Microsystems, Inc. NOTICE: The serial number of this system must be set. Name of system file [etc/system]: root filesystem type [ufs]: Enter physical name of root device [/pci/pci1000,1@1/disk@6,0:a]: configuring network interfaces: elx0. Hostname: pluto The system is coming up. Please wait. checking ufs filesystems /dev/rdsk/c0t6d0s7: is clean. NIS domainname is rmtc.Central.Sun.COM starting router discovery. starting rpc services: rpcbind keyserv ypbind kerbd done. Setting netmask of elx0 to 255.255.255.0 Setting default interface for multicast: add net 224.0.0.0: gateway pluto syslog service starting. Print services started. volume management starting. The system is ready. pluto console login:

· PowerPC: How to Boot a System for Recovery Purposes

This procedure is needed when an important file, such as /etc/passwd, has an invalid entry and is causing the boot process to fail.

If you need help identifying a system's device names, see "Accessing Devices" in System Administration Guide, Volume I.

1. Follow the instructions below depending on whether you are booting from the Solaris 2.5.1 installation CD or the network.

If You are Booting From ...	Then ...
Solaris 2.5.1 installation CD	1. Insert the Solaris 2.5.1 installation CD into the CD caddy. 2. Insert the CD caddy into the CD-ROM drive. 3. Boot from the installation CD in single-user mode: ok boot cdrom -s
The network, and an installation server or remote CD drive is available	1. Use the following command: ok boot net -s

2. Mount the file system that has the file with an invalid entry.

# mount /dev/dsk/device-name /a

3. Change to the newly mounted directory.

# cd /a/directory

4. Set the terminal type.

# TERM=sun # export TERM

5. Remove the invalid entry from the file using an editor.

# vi filename

6. Change to the root (/) directory.

# cd /

7. Unmount the /a directory.

# umount /a

8. Reboot the system.

# init 6

9. Verify the system boots to run level 3.

   The login prompt is displayed when the boot process has finished successfully.

hostname console login:

Example--Booting a PowerPC System for Recovery Purposes

The following example uses the /etc/passwd,after booting from the network, as an example of repairing an important system file.

ok boot net -s # mount /dev/dsk/c0t3d0s0 /a # cd /a/etc # TERM=ppc_type # export TERM # vi passwd (The invalid entry is removed.) # cd / # umount /a # init 6

· PowerPC: How to Stop a System for Recovery Purposes

The specific stop key sequence depends on your system type. For example, press the reset button to stop the system. If your system doesn't have a reset button, turn the power off and back on again.