xref: /openbsd/distrib/notes/hppa/install (revision a6445c1d)
1dnl	$OpenBSD: install,v 1.26 2014/03/19 01:59:48 tedu Exp $
2dnl lots of texts coming from {mvme68k,vax}/install initially
3OpenBSDInstallPrelude
4
5Bootstrapping the installation ramdisk kernel is supported
6from either the network or a CD-ROM.
7
8
9Booting from CD-ROM installation media:
10
11  To boot from SCSI CD-ROM, simply insert the CD into the drive before power
12  up, then during the computer's self-test cycle, press the space bar.
13  Subsequently at the PROM prompt issue a command:
14
15	BOOT_ADMIN> search
16
17  to initiate a search for all bootable devices available.  This procedure
18  may take a few minutes and should you have configured network boot services
19  present may find those too.  A sample output might be:
20
21   Path Number        Device Path              Device Type
22   -----------        -----------------        -----------
23   P0                 SESCSI.2.0               TOSHIBA CD-ROM XM-6201TA
24   P1                 LAN.10.0.0.5.3.254       boron
25   P2                 FWSCSI.5.0               IBM     DDRS-34560WS
26   P3                 FWSCSI.0.0               SEAGATE ST318436LW
27   P4                 SESCSI.6.0               HP     HP35480A
28
29  To boot from your CD-ROM type:
30
31	BOOT_ADMIN> boot p0
32
33
34Booting from Network:
35
36  In order to bootstrap via the network, you must provide a second system to
37  act as a boot server. It is convenient if this is a second OpenBSD machine
38  as the necessary services are already installed, although source code for
39  such programs as dhcpd can be found in OpenBSD's source tree, and should be
40  reasonably portable to other UN*X-like operating systems. More information
41  on diskless booting can be found in the OpenBSD diskless(8) manual page.
42
43  Your MACHINE expects to be able to download a LIF (``Logical
44  Interchange Format'') image, containing both the boot code and the kernel,
45  via the HP rboot protocol, for older firmware, or via the bootp protocol,
46  for more recent firmware.
47
48  Old firmware operation
49
50    Most of the 7xx models (except the 712, the second generation of 715, i.e.
51    715/64/80/100/100XC, and the 74x) have an older version of PDC. There are
52    two levels of interactive commands in this version.
53    The first level is a short menu:
54
55	b)   Boot from specified device
56	s)   Search for bootable device
57	a)   Enter Boot Administration mode
58	x)   Exit and continue boot sequence
59
60	Select from menu:
61
62    In this case, you will need to setup rbootd on the server. Start by
63    creating an /etc/rbootd.conf file on the bootserver. The format of this
64    file is the ethernet address followed by the LIF filename. Here is an
65    example:
66
67	08:00:09:70:c4:11		lif{:--:}OSrev.fs
68
69    Then start rbootd (or configure /etc/rc.conf to always start rbootd). Once
70    rbootd is running, the server name will then appear on the MACHINE as part
71    of the possible boot choices in a boot device search (``s'' command).
72
73  Modern firmware operation
74
75    More recent machines mostly those based on the 7100LC, 7200 and 7300LC CPU
76    types have a different PDC version.  There is only one interactive mode,
77    with a BOOT_ADMIN> prompt, which provides both boot settings and commands.
78
79    In this case, you will need to set up dhcpd on the server, which can
80    serve bootp protocol requests.  Start by editing the /etc/dhcpd.conf on
81    the bootserver, and declare an information block. Here is an example:
82
83	subnet 10.0.0.0 netmask 255.0.0.0 {
84		host boron {
85			filename "lif{:--:}OSrev.fs";
86			hardware ethernet 08:00:09:70:c4:11;
87			fixed-address 10.42.42.42;
88		}
89	}
90
91    Do not forget to enable dhcpd.
92
93    You will also need to enable tftpd, for the MACHINE to download the
94    installation kernel (`filename' entry) from the server in its tftp
95    directory.
96
97  Common operation
98
99    You are now ready to bootstrap the installation kernel. On your machine,
100    escape to a prompt and boot from the network by entering ``boot lan isl''.
101    On old PDC firmware, you will need to enter administration mode first.
102
103
104Installing using the netboot procedure:
105
106OpenBSDInstallPart2
107
108	Boot your machine from the installation media as described above.
109
110	It will take a while to load the installation kernel, especially from
111	a slow network connection or a CD-ROM, most likely more than a minute.
112	If some action doesn't eventually happen, or the spinning cursor
113	has stopped and nothing further has happened, either your boot
114	media is bad, your diskless setup is incorrect, or you may have
115	a hardware or configuration problem.
116
117OpenBSDInstallPart3(,"sd0")
118
119OpenBSDInstallPart4
120
121OpenBSDInstallPart5(,{:-
122	Due to prom limitations, you should make sure the whole 'a'
123	partition is CONTAINED WITHIN THE FIRST 2GB of the disk if
124	you intend to boot from it.-:})
125
126	Since the target disk will become the boot disk for your new
127	OpenBSD/MACHINE installation, the disklabel program will restrict
128	the available disk area to keep the first cylinder, which will
129	contain the bootblock, safe from being overwritten. If you don't
130	plan to install a bootblock on this disk, you can reclaim this
131	space with the 'b' command.
132
133OpenBSDInstallPart6({:-CD-ROM, -:})
134
135OpenBSDURLInstall
136
137OpenBSDCDROMInstall
138
139OpenBSDNFSInstall
140
141OpenBSDDISKInstall(,{:-only -:})
142
143OpenBSDCommonInstall
144
145OpenBSDInstallWrapup
146
147OpenBSDCongratulations
148
149
150
151OpenBSDUnattendedInstallation
152