diff options
author | Mark Kettenis <kettenis@cvs.openbsd.org> | 2008-05-13 20:47:33 +0000 |
---|---|---|
committer | Mark Kettenis <kettenis@cvs.openbsd.org> | 2008-05-13 20:47:33 +0000 |
commit | 94b8fed963be0124709eeeeeca76b6841699e80a (patch) | |
tree | 6c35cc0ffcfb0db49a767a6667e51f2b4cbaf7e7 /distrib/notes/socppc | |
parent | 1ddffb03d710335b443892926952b78b275d47ef (diff) |
Initial stab at installation notes.
Diffstat (limited to 'distrib/notes/socppc')
-rw-r--r-- | distrib/notes/socppc/contents | 34 | ||||
-rw-r--r-- | distrib/notes/socppc/hardware | 3 | ||||
-rw-r--r-- | distrib/notes/socppc/install | 52 | ||||
-rw-r--r-- | distrib/notes/socppc/prep | 137 | ||||
-rw-r--r-- | distrib/notes/socppc/upgrade | 2 | ||||
-rw-r--r-- | distrib/notes/socppc/whatis | 3 | ||||
-rw-r--r-- | distrib/notes/socppc/xfer | 18 |
7 files changed, 249 insertions, 0 deletions
diff --git a/distrib/notes/socppc/contents b/distrib/notes/socppc/contents new file mode 100644 index 00000000000..f1fed16e6d6 --- /dev/null +++ b/distrib/notes/socppc/contents @@ -0,0 +1,34 @@ +dnl $OpenBSD: contents,v 1.1 2008/05/13 20:47:32 kettenis Exp $ +TopPart + +OpenBSDdistsets + +OpenBSDbsd + +OpenBSDrd + + boot The OpenBSD/MACHINE secondary boot loader. + +DistributionDescription(eleven) + +OpenBSDbase(56910063,164264180,shared) + +OpenBSDcomp(98847624,255348473,shared) + +OpenBSDetc(1222181,4031284) + +OpenBSDgame(2749879,6226456) + +OpenBSDman(7710862,27896382) + +OpenBSDmisc(2306611,7714263) + +OpenBSDxbase(11134588,32455021) + +OpenBSDxetc(80630,301140) + +OpenBSDxfont(35581491,43728442) + +OpenBSDxserv(8299743,23973793) + +OpenBSDxshare(2743002,14575889) diff --git a/distrib/notes/socppc/hardware b/distrib/notes/socppc/hardware new file mode 100644 index 00000000000..9fb96145107 --- /dev/null +++ b/distrib/notes/socppc/hardware @@ -0,0 +1,3 @@ +dnl $OpenBSD: hardware,v 1.1 2008/05/13 20:47:32 kettenis Exp $ +dnl When more than one model is supported, turn this into a list... +OpenBSD/MACHINE runs on the Thecus N1200 at the moment. diff --git a/distrib/notes/socppc/install b/distrib/notes/socppc/install new file mode 100644 index 00000000000..64b15a3b333 --- /dev/null +++ b/distrib/notes/socppc/install @@ -0,0 +1,52 @@ +dnl $OpenBSD: install,v 1.1 2008/05/13 20:47:32 kettenis Exp $ +OpenBSDInstallPrelude + +OpenBSDInstallPart2 + +OpenBSDBootMsgs(,"wd0") + + You will next be asked for your terminal type. If you are + installing from a non-serial console, the default of "vt220" + is correct. If you are installing from a serial console + you should choose the terminal type from amongst those listed. + (If your terminal type is xterm, just use vt220.) + +OpenBSDInstallPart3 + + Next you will have to edit or create a disk label for the disk + OpenBSD is being installed on. If there are any existing + partitions defined (for any operating system), and a disk label + is not found, you will first be given an opportunity to run + fdisk and create an OpenBSD partition. + + If fdisk is being invoked on your behalf, it will start by + displaying the current partitions defined and then allow you + to modify this information, add new partitions and change + which partition to boot from by default. If you make a mistake, + you will be allowed to repeat this procedure as necessary to + correct this. Note that you should make OpenBSD be the active + partition at least until the install has been completed. + +OpenBSDInstallPart4({:- If you have Linux partitions + defined on the disk, these will usually show up as partition + 'h', 'i' and so on.-:}) + + Explain more here. + +OpenBSDInstallPart5(wd0) + +OpenBSDInstallNet({:-CD-ROM, -:},nofloppy) + +OpenBSDFTPInstall + +OpenBSDHTTPInstall + +OpenBSDCDROMInstall + +OpenBSDDISKInstall({:-"wdN" or -:},,{:-, Linux (ext2) or MS-DOS-:}) + +OpenBSDCommonFS + +OpenBSDCommonURL + +OpenBSDCongratulations diff --git a/distrib/notes/socppc/prep b/distrib/notes/socppc/prep new file mode 100644 index 00000000000..b82d7a04e4b --- /dev/null +++ b/distrib/notes/socppc/prep @@ -0,0 +1,137 @@ +dnl $OpenBSD: prep,v 1.1 2008/05/13 20:47:32 kettenis Exp $ +To be able to boot the OpenBSD/MACHINE installation program, you will +need to learn a bit about Das U-Boot, the low-level process that controls +the microprocessor after hardware initialization. + +Talking to the Thecus + +The Thecus N2100 needs a serial cable. On the back of the disk drive +circuit board, there is either a 10-pin header (with one pin removed), +or 9 holes for you to solder in your own header. The ribbon cable +that connects from there to your serial cable or the serial port on +your computer is of the same type as used on older i386 PCs, but +be aware that there are two different types of 10-pin IDC to DB-9M +ribbon cable in use, which look identical (the differences are hidden +inside the DB-9 connector). The cable you need is wired using the +"AT-Everex" or "Asus" pinout, as described here: + + http://www.pccables.com/07120.htm + +and *not* the more straightforward to solder "crossed" type: + + http://www.pccables.com/07121.htm. + +If you wish to check a cable, or make your own, the pinouts are: + + DB9 IDC10 + === ===== + 1 2 3 4 5 1 3 5 7 9 + 6 7 8 9 2 4 6 8 10 + +Wire pin 1 to 1, 2 to 2 etc, with 10 not connected. + + +Booting Thecus N2100 + +When you have connected your computer, a command like "tip -115200 tty00" +(assuming you're using the first serial port on your machine) should +connect you to the Thecus console. Now apply power to the Thecus +and start it. + +After some device probe information, you should see this prompt: + + Hit any key to stop autoboot: 1 + +You have exactly one second to press a key and enter interactive +U-Boot. Fortunately it will typically accept a key typed during the +diagnostics that precede thus prompt. + +The recommended way to boot OpenBSD on Thecus is to configure networking and +load bsd.rd from a tftp server or http server. First networking must be +configured using the setenv command. + + => setenv ipaddr 10.0.0.21 + => setenv serverip 10.0.0.7 + +Once you have done this, and have set up your TFTP server on +the gateway machine (10.0.0.7 in the above example), you can +boot manually. + + => tftpboot 200000 bsd.rd + Speed: 1000, full duplex + Using Freescale TSEC0 device + TFTP from server 10.0.0.7; our IP address is 10.0.0.21 + Filename 'bsd.rd'. + Load address: 0x200000 + Loading: ########################################################## + ############################################################# + ... + ###### + done + Bytes transferred = 295148 (480ec hex) + => go 200000 + +Copyright (c) 1982, 1986, 1989, 1991, 1993 + The Regents of the University of California. All rights reserved. +Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org + +OpenBSD 4.3 (RAMDISK) #175: Tue Mar 4 21:54:34 MST 2008 + deraadt@socppc.openbsd.org:/usr/src/sys/arch/socppc/compile/RAMDISK +real mem = 67108864 (64MB) +avail mem = 63012864 (60MB) +... +Install(I), Upgrade(U) or Shell(S)? + +If you then install to your hard disk, in future you can +load the OpenBSD/socppc boot loader + + => tftpboot 100000 boot + => bootm + +and just hit "return" to boot OpenBSD. + + +Automatic Booting + +However, for easier booting, you may wish to modify the flash +memory so that the Thecus will boot automatically into OpenBSD +when it is powered up. + + => erase fe780000 fe800000 + + .... done + Erased 4 sectors + => tftpboot 200000 boot + Speed: 1000, full duplex + Using Freescale TSEC0 device + TFTP from server 10.0.0.7; our IP address is 10.0.0.21 + Filename 'boot'. + Load address: 0x200000 + Loading: ########################################################## + done + Bytes transferred = 295148 (480ec hex) + => cp 200000 fe780000 20000 + Copy to Flash... + 512 KBdone + => setenv bootcmd bootm FE780000 + => saveenv + Saving Environment to Flash... + Un-Protected 2 sectors + Erasing Flash... + .. done + Erased 2 sectors + Writing to Flash... + 256 KBdone + Protected 2 sectors + => reset + +This configuration can easily be set back to the default, as the +Linux system does not get erased from the flash memory. To set it +back, just change the boot script with fconfig back to what it was, +for example: + + => setenv bootcmd flashboot + => savenv + +The bootloader is command driven with timeout like many other OpenBSD +architectures. diff --git a/distrib/notes/socppc/upgrade b/distrib/notes/socppc/upgrade new file mode 100644 index 00000000000..0ea8de9c4bd --- /dev/null +++ b/distrib/notes/socppc/upgrade @@ -0,0 +1,2 @@ +dnl $OpenBSD: upgrade,v 1.1 2008/05/13 20:47:32 kettenis Exp $ +OpenBSDUpgrade({:-bsd.rd on the boot disk-:}) diff --git a/distrib/notes/socppc/whatis b/distrib/notes/socppc/whatis new file mode 100644 index 00000000000..178350046f1 --- /dev/null +++ b/distrib/notes/socppc/whatis @@ -0,0 +1,3 @@ +dnl $OpenBSD: whatis,v 1.1 2008/05/13 20:47:32 kettenis Exp $ + +OpenBSD/MACHINE runs on the Thecus N1200 PowerPC-based network disk appliances. diff --git a/distrib/notes/socppc/xfer b/distrib/notes/socppc/xfer new file mode 100644 index 00000000000..c5f8704736c --- /dev/null +++ b/distrib/notes/socppc/xfer @@ -0,0 +1,18 @@ +dnl $OpenBSD: xfer,v 1.1 2008/05/13 20:47:32 kettenis Exp $ +Installation is supported from several media types, including: + + CD-ROM + FFS partitions (for upgrades only) +dnl DOS (FAT) partitions +dnl EXT2 partitions + FTP + HTTP + +Although you can access the distribution sets directly from the CD-ROM or +from one of the FTP mirrors over the internet, you may wish to transfer +the sets to a local FTP server, or copy them to a partition on the target +system's disk (for upgrades only). + +OpenBSDXferShortPrelude + +OpenBSDXferFFS |