Ignite-UX Installation Booting
22
When the function completes, the “In Progress ...” gets erased and replaced with:
Init[ 11]:0xe0000000010599d0: io_memory_config - DONE (0x00001cbf9196 iticks)
To enable this output, you should perform the following actions when booting the IINSTALL install
kernel (these instructions assume that you are booting from a CD or DVD):
1. At the EFI shell, choose one of the following options:
• If you have configured an option to boot from the CD or DVD drive, select that option. The system
starts to boot automatically.
• Otherwise, quit to the EFI shell, and then change your EFI partition to the CD drive containing the
installation media. If the system does not automatically boot, type startup then press Enter.
2. Interrupt the boot sequence at the message Press Any Key to interrupt Autoboot by
pressing a key.
fs0:\> startup
...
HP-UX Bootloader for IA64 Revision 1.713
Press Any Key to interrupt Autoboot
AUTO ==> boot :IINSTALL
Seconds left till autoboot - 7
type ‘help’ for help
HPUX>
3.
At the HPUX> prompt, enter boot :IINSTALL –v and then press Enter so the bootloader
loads the kernel and installation file system into memory, and then passes control to the kernel.
Note that the information about what routines are being called during initialization will appear
only on the console of the system.
The “pre_reboot_cmd” command hook
The following information about the command hook "pre_reboot_cmd" is not intended for general
use and should only be used when requested by HP support personnel. This new keyword is only
available from Ignite-UX version C.7.2 onwards and it provides no functionality that is useful for
installing systems.
The purpose of the
pre_reboot_cmd command hook is to execute the given command early in an
installation or recovery session prior to a reboot. The reason this command hook is documented in
this white paper is to provide convenient instructions on how to use it when you need it.
The most common reason HP might ask you to use this command hook is to provide a shell prompt
after an error that would have led to a reboot and failed installation or recovery. The shell can then
be used to gather information that will aid in the investigation and resolution of the problem.
The following is an example of how to use the
pre_reboot_cmd command hook to run a shell after
an error that would have caused a reboot early during an installation or recovery session.