| blob | 60847c81a005a8800ff0f2126038390b5cbc5b7a |
1 .\" $NetBSD: prep,v 1.14 2009/01/26 00:14:43 snj Exp $
2 .
3 .Ss2 Deciding on partition sizes
4 .
5 If you're installing
6 .Nx*M
7 for the first time it's a good idea
8 to look at the partition sizes of the disk you plan to install
9 .Nx
10 on. Will you be installing
11 .Nx
12 onto the same disk as
13 .Tn Solaris ,
14 on its own disk,
15 or will you be netbooting? While
16 .Nx
17 can work just fine on a disk shared with
18 .Tn Solaris ,
19 the
20 .Nx
21 installer does not currently support this. The limitation is that the
22 .Nx
23 .Xr disklabel 8
24 writes partition info that
25 .Tn Solaris
26 is not familiar with. Therefore, if you are sharing a disk with
27 .Tn Solaris ,
28 any time you change a partition table, you must do it from
29 .Tn Solaris .
30 .Pp
31 Assuming a classic partition scheme with
32 .Pa /
33 (root) and
34 .Pa /usr
35 file systems, a comfortable size for the
36 .Nx
37 .Pa /
38 partition is about 200 MB.
39 A full binary installation including X takes over 600 MB in
40 .Pa /usr .
41 Since the pkgsrc binaries are typically installed in
42 .Pa /usr/pkg
43 you may want a significantly larger
44 .Pa /usr
45 partition.
46 A good initial size for the swap partition is the amount of physical
47 memory in your machine if you've got more than 128 MB RAM. If you've got
48 less RAM, you may want swap to be at least 128 MB.
49 .Pp
50 Note that the OBP on Ultra 1 and Ultra 2 machines can only boot from the first
51 4Gb of the disk, so this limits the size of the root partition on these models.
52 .
53 .Ss2 Setting up Open Firmware
54 .
55 First, you need to stop your system from automatically booting when
56 powered on. Pressing the
57 .Key STOP
58 key (sometimes called the
59 .Key L1
60 key, found on the left side of your keyboard) and the
61 .Key a
62 key will halt your system and give you the
63 .Dq Li ok
64 prompt. If you are using a serial console, send a
65 .Dq BREAK
66 signal from your terminal (the method of sending
67 .Dq BREAK
68 varies from terminal to terminal).
69 .Pp
70 If the ethernet address of your \*M system is
71 .Li ff:ff:ff:ff:ff:ff
72 (check with the Open Firmware
73 .Dq banner
74 command),
75 then your NVRAM battery is dead and you will have trouble using
76 ethernet (among other problems). Read the Sun NVRAM/Hostid FAQ.
77 .Lk http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html
78 .Pp
79 If you have a valid ethernet address and you plan to netboot, write down
80 your system's ethernet address.
81 .Pp
82 You cannot use the security modes of the SPARC OpenFirmware.
83 .(disp
84 .No ok Ic "setenv security-mode none"
85 .disp)
86 .Pp
87 If you are using a serial console, the
88 .Nx*M
89 installer defaults to using 9600 bps, 8N1 settings. You may want to
90 configure your system and serial terminal like this prior to booting the
91 installer. A new installation of
92 .Nx*M
93 will default to these settings as well.
94 .Pp
95 SCSI devices are specified by an Open Firmware
96 .Ic devalias
97 which provides simple mnemonics for the full path to the device. Type
98 .Ic devalias
99 to get a list of all of the available aliases.
100 At a minimum, the alias and partition are necessary when booting.
101 .Pp
102 Therefore, to boot from the swap partition on the internal hard drive
103 one would use:
104 .Pp
105 .(disp
106 .No ok Ic "boot disk:b"
107 .disp)
108 .Pp
109 To boot from a CD-ROM (Open Firmware assumes SCSI CD-ROMs are at target 6),
110 one would use:
111 .Pp
112 .(disp
113 .No ok Ic "boot cdrom"
114 .disp)
115 .Pp
116 And to boot from a kernel named
117 .Li netbsd-GENERIC
118 on the fourth partition (
119 .Sq Li d ,
120 often the
121 .Pa /usr
122 partition) on an external SCSI hard drive (target 2, partition 3), one
123 would use:
124 .Pp
125 .(disp
126 .No ok Ic "boot disk2:d netbsd-GENERIC"
127 .disp)
128 .Pp
129 If you get
130 .Dq .... Fast Data MMU Miss
131 when booting after the NetBSD installation, your OpenBoot PROM may
132 need updating. It has been reported that version 3.31 lead to a
133 successful boot on an Ultra Enterprise 420R, while version 3.23 did
134 not. Exact values may vary, depending on your hardware, current
135 OpenBoot PROM version and moon phase.
136 .Pp
137 .
138 .Ss2 Determining how to boot from an SBUS or PCI card
139 .
140 Some SBUS and PCI cards have firmware that lets you use them as boot
141 devices. These cards do not automatically create
142 .Ic devalias
143 entries, so you must traverse the device tree to figure out what
144 Open Firmware calls your card. You will be using Open Firmware commands
145 at the
146 .Sq Li ok
147 prompt. First `cd' to the top of the device tree and list the
148 nodes there. The following is the procedure to boot from an IDE card in
149 an UltraSPARC 30.
150 .(disp
151 .No ok Ic "cd /"
152 .No ok Ic "ls"
153 f006cf08 SUNW,ffb@1e,0
154 f006c32c SUNW,UltraSPARC-II@0,0
155 f006002c counter-timer@1f,1c00
156 f005f410 pci@1f,2000
157 f005eb54 pci@1f,4000
158 f004cf84 virtual-memory
159 f004c9a4 memory@0,0
160 f002ce38 aliases
161 f002cdc8 options
162 f002cc90 openprom
163 f002cc24 chosen
164 f002cbb4 packages
165 .disp)
166 Usually, you can simply type in the name before the at (@) sign and
167 OpenFirmware will fill in the rest.
168 .(disp
169 .No ok Ic "cd pci@1f,4000"
170 .No ok Ic "ls"
171 f0081524 ide@2
172 f007be50 scsi@3
173 f0074688 network@1,1
174 f0060324 ebus@1
175 .No ok Ic "cd ide@2"
176 .No ok Ic "ls"
177 0081fe4 cdrom
178 f0081938 disk
179 .No ok Ic "cd disk"
180 .No ok Ic "ls"
181 .No ok Ic "pwd"
182 /pci@1f,4000/ide@2/disk
183 .disp)
184 OK, now we know the path to the IDE device in this example. Now, we need
185 to determine if it's capable of booting. If it is, it will have the
186 .Ic word
187 `open'.
188 .(disp
189 .No ok Ic "words"
190 close load write read seek
191 open write-blocks read-blocks max-transfer
192 block-size dma-free dma-alloc spin-down spin-up
193 .disp)
194 Great!
195 Also, in case you're interested in further details about your
196 hardware, you can use the
197 .Ic .properties
198 command.
199 .Pp
200 So, when it's time to type in a boot command, use the shortened version of
201 the
202 .Ic pwd
203 command. You need to be more specific if there are two devices with the
204 same name (in this case, two /pci entries). In this example, you'd type:
205 .(disp
206 .No ok Ic "boot /pci@1f,4000/ide/disk@0,0"
207 .disp)
208 You can also store this device path across reboots using the
209 .Ic nvalias
210 command.
211 .(disp
212 .No ok Ic "nvalias wd0 /pci@1f,4000/ide/disk@0,0:a"
213 .disp)
214 .Pp
215 And when the kernel is done booting, it may not automatically use your
216 card as the root device -- you may need to type in the
217 .Nx*M
218 name for
219 that device:
220 .(disp
221 root on sd0a dumps on sd0b
222 no file system for sd0 (dev 0x700)
223 cannot mount root, error = 79
224 .No "root device (default sd0a):" Ic "?"
225 use one of: hme0 sd0[a-h] wd0[a-h] halt
226 .No "root device (default sd0a):" Ic "wd0a"
227 .No "dump device:" Ic "wd0a"
228 .No "file system (default generic):" Ic "ffs"
229 root on wd0a
230 .disp)
231 .Pp
232 The root device can also be specified in your kernel config file.
233 .
234 .Ss2 Configuration of network interfaces
235 .
236 Some network devices (i.e., certain SBus cards)
237 allow a choice between operating on a UTP or a AUI port.
238 The
239 .Li le
240 driver supports automatic detection of the port which is actually connected to
241 the wire.
242 If automatic detection is not available or not working properly in your
243 environment, you may have to specify the type connection using the
244 .Ar media
245 parameter of
246 .Xr ifconfig 8 .
247 During installation, you'll get the
248 opportunity to specify the appropriate medium.
249 Use
250 .Li 10base5/AUI
251 to select the AUI connector, or
252 .Li 10baseT/UTP
253 to select the UTP connector.