1 .\" $NetBSD: prep,v 1.23 2008/09/06 21:33:27 tsutsui Exp $
3 There are two installation tools available.
4 The traditional miniroot
5 installer is script-based and may be netbooted or may be dumped to a disk
7 The ramdisk kernel with the
9 installation utility is more flexible,
10 but can only be netbooted and has not been extensively tested.
12 There are several possible installation configurations described in this
14 Other configurations are possible, but less common.
15 If you are unable to install based on the information in this document,
17 .Mt port-hp300@NetBSD.org
19 The configurations described in this document are as follows:
28 or other server platforms (Linux, FreeBSD, SunOS, Solaris, HP-UX etc.) with
31 package and then runs the miniroot installation tools or a purely diskless
32 installation from a server on the same subnet (you must have root access).
33 For more information, refer to the NetBSD Diskless
35 .Lk http://www.NetBSD.org/docs/network/netboot/
37 .Lk http://www.NetBSD.org/docs/network/netboot/rbootd/
42 from a local disk, tape, or floppy
43 and then runs the miniroot installation tools or a purely diskless
44 installation from a server as described above.
47 on your \*M if it does not have a SCSI interface or a floppy drive.
53 You partition the drive
54 and then run the miniroot installation tools from that drive.
57 on your \*M if it does not have a SCSI interface.
59 The preferred method is to use another
61 server to netboot the \*M client.
62 This procedure will not
63 work on the handful of models which are incapable of netbooting.
64 In particular, the 320, 350, 330, 318, and
65 319 might not have a recent enough BootROM.
66 The BootROM revision is printed when your workstation is first powered on
68 Revision B or later will definitely work.
69 BootROMs with numeric revisions such as 1.1 (on a 400s) will netboot
71 You can netboot from any built-in or add-on ethernet board on
72 a model with a supported BootROM.
74 If you have access to a
78 easier to simply upgrade than to install from scratch.
79 Skip down to the section on
80 .Sx Upgrading a previously-installed NetBSD System
82 .Ss2 Formatting your hard drives
85 does not have the capability to perform a low-level format of hard
87 SCSI disks can be formatted on any platform with SCSI support and
90 HP-IB disks can only be formatted by the
94 You may need to first create the device nodes for your disk, as
96 was never very good about populating
100 .No # Ic "mknod /dev/dsk/IDs0 b 0 0xSCID00"
101 .No # Ic "mknod /dev/rdsk/IDs0 c 4 0xSCID00"
102 .No # Ic "mediainit -v /dev/rdsk/IDs0"
106 is the HP-IB address (a.k.a. slave) of the disk in hexadecimal.
107 This is usually between
117 is the Select Code of the disk controller.
120 for slow (i.e. built-in) HP-IB or
122 (14 decimal) for SCSI or fast HP-IB.
125 .Ss2 Designing your disk's partition table
127 This step can sometimes be a real pain, especially when using
129 It's best to calculate it ahead of time.
131 If you are installing to an HP-IB disk,
132 you will need information about your disk's geometry, based on 512-byte sectors.
134 .Pa installation/misc/HP-IB.geometry
135 in the distribution has geometry information for
136 several HP-IB disks, but may be incomplete.
137 Geometry may be calculated from an HP-UX
139 entry, but note that HP-UX geometry is based
140 on 1024 byte sectors, while
142 is based on 512 byte sectors.
143 You should have all partitions start on cylinder boundaries.
145 If you are installing to a SCSI disk, you don't need to worry about the
146 details of the geometry.
147 Just create a disklabel based on the total
148 number of sectors available on the disk.
150 .Em A quick note about partitions:
151 Since the target disk will become the boot
154 installation, you will need to treat the
158 partitions in a special manner.
159 Due to the size of the
161 boot program (it spills into the area after the disklabel),
162 it is necessary to offset the beginning of the
165 For HP-IB disks, it is best to offset it by one cylinder from
166 the beginning of the disk.
167 For SCSI disks, just offset it by 100 KB (200 sectors).
170 partition will be marked with the type
172 and may not be used for a file system.
173 (For those unfamiliar
176 partition conventions, the
178 partition is defined as the
181 .Sq raw partition . )
184 You will need at least a 6 MB swap partition (although 2-3*RAM is
185 recommended) if you are unable to netboot the installer, as the miniroot
186 is temporarily placed in this partition.
189 Here is an example disklabel from a 7959B HP-IB hard drive:
199 sectors/cylinder: 378
201 total sectors: 594216
206 headswitch: 0 # milliseconds
207 track-to-track seek: 0 # milliseconds
211 # size offset fstype [fsize bsize cpg]
212 a: 37800 378 4.2BSD 1024 8192 16 #
213 b: 66150 38178 swap 1024 8192 16 #
214 c: 594216 0 boot # (Cyl. 0 - 1571)
215 d: 489888 104328 4.2BSD 1024 8192 16 #
218 .Ss2 Installing the bootstrap program locally
220 For earlier models incapable of netbooting, you need to install the
221 bootstrap program on a bootable local device, such as a hard disk, floppy
223 If you will be booting the miniroot over the
224 network, then you will be installing
225 .Pa installation/misc/SYS_UBOOT .
227 If you do not have access to a netboot server to serve the miniroot
228 installer, you can use a primitive bootstrap program
229 .Pa installation/misc/SYS_INST
230 to load the miniroot from a locally attached device (such as a
232 This is not recommended, as
234 is difficult to use, buggy, and provides no error checking when
235 partitioning your disk.
237 If your system has SCSI, this is easy.
238 Just take a scratch SCSI disk (hard disk, zip disk, or CD-R)
239 and use any computer to dump the bootstrap program to it.
240 For example, to dump it to the
242 disk on a non-i386 platform:
244 .No # Ic "dd if=SYS_UBOOT of=/dev/sd1c"
247 If your system has a floppy drive, you can write the bootstrap program to
248 it using any computer with a floppy drive.
249 You will need to dump it using a utility like
253 Make sure to read back from the floppy to verify that the file has been
256 If your system does not have SCSI or a floppy drive, you will need a
257 bootable operating system on your \*M so you can write files to the HP-IB
259 You should probably write the bootstrap program to the disk you
266 to write to an HP-IB disk:
268 .No # Ic "dd if=SYS_UBOOT of=/dev/rdsk/IDs0"
272 is the HP-IB address (a.k.a. slave) of the disk in hexadecimal.
273 This is usually between
284 to write to an HP-IB tape:
286 .No # Ic "dd if=SYS_UBOOT of=/dev/rmt/0mnb obs=20b conv=osync"
289 .Ss2 Installing the miniroot file system locally
291 This step is only necessary if you are not loading the miniroot
292 installer from a netboot server.
293 Follow the same procedure for the bootstrap program, except use the
294 uncompressed miniroot file system
295 .No ( Pa installation/miniroot/miniroot.fs.gz No )
296 instead of the bootstrap program.
297 The only quirk is that you should place it at the offset of the swap
298 partition you calculated above in the disklabel.
299 In the example disklabel above, the offset is 38178 sectors of 512 bytes.
302 command would be something like:
304 .No # Ic "gunzip miniroot.fs.gz"
305 .No # Ic "dd if=miniroot.fs of=/dev/rdsk/IDs0 seek=38178b"
309 after the offset, which specifies blocks of 512 bytes.
311 By dumping the miniroot to disk where the swap partition will be, you're
312 saving a step later where
314 tries to download the miniroot over NFS.
315 Just make sure that when you enter the partition table into
317 you use the same block offset for the swap partition as you dumped the
320 .Ss2 Configuring the netboot server
322 This step will configure your netboot server to provide
324 and the miniroot installer to your \*M.
326 .so ../common/netboot
328 .Ss2 Put Series 400 systems in "HP-UX Compatible Boot Mode"
330 Series 400 systems can be configured to boot either
336 you must have your system configured in
337 .Sq Li "HP-UX Compatible Boot Mode" .
338 If, when you power on your machine, it does
340 present a menu like the following, then you need to change your
344 Hewlett-Packard Company.
347 BOOTROM Series 400 Rev. 1.1
348 MD12 REV 1.2 1990/08/07.14:27:08
352 Attach a Domain keyboard or an HIL keyboard.
354 The BootROM knows how to use either, even if
361 For a 4XXs, there's a toggle switch on the back of the machine (near the top).
362 For a 4XXt or 4XXdl, press the green button on the front, behind
364 For a 425e, there's a toggle switch on the back of the
365 machine (in the middle).
366 The second green LED should light up.
370 Press the reset button.
371 For a 4XXs, there's a small plunger on the back of
372 the machine (near the top).
373 For a 4XXt or 4XXdl, there's a white button
374 on the front, behind the silly door.
375 For a 425e, there's a button on the
380 to get the Domain boot prompt
381 .No ( Li \*[Gt] No ) .
385 to get a list of available commands.
387 Type the following sequence of commands to convert to
388 .Sq Li "HP-UX Compatible Boot Mode" .
392 .No "Type [key] RETURN ?" Ic 2
393 .No "Type [key] RETURN ?" Ic 2
394 .No "Type T or P RETURN ?" Ic P
395 .No "Type [key] RETURN ?" Ic E
402 It may prevent you from selecting which device to boot from.
404 See the FAQ for additional help.
405 .Lk http://www.NetBSD.org/ports/hp300/faq.html#domain
407 .Ss2 Searching for a bootable system
409 All the early hp300 Boot ROMs are very primitive and only allow a few
411 You can only interact with it after it is first powered on.
412 If you reboot the machine, it will ignore anything you type and
413 start loading the same OS you previously booted.
415 At any time after it recognizes the keyboard, while it is doing its self
416 test or searching for a bootable system, you can hit reset to return it to
417 a cold-boot configuration.
418 On HIL keyboards, this is
419 .Key control-shift-break ,
422 is the key in the upper left (where
423 escape is on sane keyboards).
424 There is no equivalent over serial terminal,
425 you'll need to power-cycle your machine.
427 After it beeps (i.e. recognizes the HIL keyboard), press
429 twice to get the list of bootable devices.
431 SEARCHING FOR A SYSTEM (RETURN To Pause)
434 The newer HP Boot ROM, present on Series 400 machines and some of the
435 later 300s (345, 375, 380, 382, 385) is capable of a little bit more.
436 To select which device to boot from, press
438 once after it beeps twice (i.e. recognizes the HIL keyboard) to get the
439 list of bootable devices.
441 RESET To Power-Up, SPACE clears input Select System, type RETURN ?
444 The FAQ lists additional things you can do with the BootROM and describes
445 the order the BootROM looks for bootable devices.
446 .Lk http://www.NetBSD.org/ports/hp300/faq.html
448 A normal power-on sequence (from a 400s) looks something like this:
451 Hewlett-Packard Company.
454 BOOTROM Series 400 Rev. 1.1
455 MD12 REV 1.2 1990/08/07.14:27:08
464 RESET To Power-Up, SPACE clears input
465 Select System, type RETURN
470 HP98644 (RS-232) at 9
472 HP98265 (SCSI S 32) at 14
473 HP98643 (LAN) at 21, AUI, 080009115DB3
474 Bit Mapped Video at 133 (Console)
476 :RODIME RO3000T, 1406, 0
478 :LAN080009115DB3, 2100, 0
488 You should see your bootstrap program somewhere in this list.
489 If it's not here, then your \*M can't boot it and there's a problem somewhere.
490 To boot from a particular device, type in the two character name for it
493 In this example, you'd type
495 to boot from the network.
497 .Ss2 Selecting ethernet port on Series 400
499 Series 400 machines have two ethernet media types built into the
501 You may only use one at a time.
502 When your Series 400 workstation goes through the self-test when
503 powered on or rebooted, it will say one of the following:
505 HP98643 (LAN) at 21, AUI
506 HP98643 (LAN) at 21, Thin
509 If the wrong type of network is selected, you will need to change the
511 You will need to open the case (4XXt, 4XXdl, 4XXe) or
512 remove the motherboard (4XXs) to access the jumper.
513 Be sure to use static-prevention measures, as you could easily fry
514 your motherboard from carelessness.
515 If you are uncomfortable with this, ask a friend who is
516 aware of these issues.
517 There is a block of 8 jumpers at the rear of the
518 motherboard, labeled AUI/Thin.
519 You will need to put the jumpers in the
520 position necessary for your type of ethernet.
522 .Ss2 Running SYS_INST
524 This step is necessary
526 if you cannot netboot.
530 from the list of bootable devices that the BootROM found.
532 will load and prompt you for a command.
534 .Em A quick note about disk numbers:
537 program, you may use different unit numbers for the disks than when the
540 The unit number for a disk while in
542 is calculated with the following formula:
545 unit = (controller * 8) + slaveID
548 Controllers are numbered 0, 1, ... starting with the lowest select code.
549 SCSI controllers and HP-IB controllers are counted separately.
551 if you had a system with an internal HP-IB interface at select code 7,
552 a fast HP-IB interface at select code 14, and a SCSI interface at select
553 code 16, unit numbers might be something like the following:
554 .Bl -column -offset indent HP-IB\ at\ 14,\ slaveID\ 5 Unit (disk:\ rd13)
555 .It Sy Location Ta Sy Unit
556 .It HP-IB\ at\ 7,\ slaveID\ 2 Ta 2 Ta (disk:\ rd2)
557 .It HP-IB\ at\ 14,\ slaveID\ 5 Ta 13 Ta (disk:\ rd13)
558 .It SCSI\ at\ 16,\ slaveID\ 0 Ta 0 Ta (disk:\ sd0)
561 You will need to place a disklabel on the disk.
564 .No "sys_inst\*[Gt]" Ic disklabel
567 It may be worth selecting the
569 option initially to ensure that
570 the disklabel area is clear.
571 This may be especially important if an
572 HP-UX boot block had been previously installed on the disk.
577 option, and answer the questions about your disk.
578 There may be several questions which you may not be sure of the answers to.
579 Listed below are guidelines for SCSI and HP-IB disks:
581 .Bl -column -offset indent -compact Track-to-track?xx xxxxx
582 .It Bad\ sectoring? Ta NO
586 .It Cylinderskew? Ta 0
588 .It Track-to-track? Ta 0
589 .It Drivedata\ 0-4? Ta 0\ (for\ all\ Drivedata\ values)
592 Next, you will be asked to fill out the partition map.
593 You must provide responses for all 8 partitions.
594 Remember, you must have the sector offset for the
596 partition match the location you dumped the miniroot file system image.
598 offset of any unused partition to 0.
599 Note that sizes and offsets are expressed in
601 assuming 512 byte sectors.
603 to ensure that partitions begin and end on cylinder boundaries (i.e. size
604 and offset is an even multiple of the number of sectors per cylinder).
605 While this is not technically necessary, it is generally encouraged.
608 When setting the partition type of the
610 partition, make sure to
613 partition so that the miniroot can be mounted (even
614 if this will be a swap partition).
615 You will be given a chance to clean
616 this up later in the installation process.
619 Once you have edited the label, select the
621 option to verify that it is correct.
626 Otherwise, you may re-edit the label.
628 In an earlier step, we already copied the miniroot image to the target
631 Boot from the miniroot file system.
634 .No "sys_inst\*[Gt]" Ic boot
637 Enter the disk from which to boot.
638 The kernel in the miniroot file system will be booted into single-user mode.
640 .Ss2 Choosing a kernel location
642 Once the bootstrap program
644 has started, it will pause and let you chose a kernel location, name, and
647 \*[Gt]\*[Gt] NetBSD/hp300 Primary Boot, Revision 1.13
648 \*[Gt]\*[Gt] (gregm@mcgarry, Mon Apr 15 08:46:32 NZST 2002)
649 \*[Gt]\*[Gt] HP 9000/425e SPU
650 \*[Gt]\*[Gt] Enter "reset" to reset system.
651 Boot: [[[le0a:]netbsd][-a][-c][-d][-s][-v][-q]] :-
654 If your kernel is on a different device than
656 then you will need to type in where to find it.
657 This is the case, for
658 example, if your model is incapable of netbooting and you started
660 from a floppy, and the miniroot installer is on a netboot server.
661 In this case, you'd type in
665 If you've installed the miniroot on your disk, you can always boot from
666 that by using partition
670 For example, to boot the miniroot from an HP-IB disk on controller 0 at
671 slave ID 2, you'd type:
673 .No "Boot: [[[rd0a:]netbsd][-a][-c][-d][-s][-v][-q]] :- " Ic "rd2b:netbsd"