Subject: Part 15 of 22 /boot,/mdec,[T]MSCP updates Index: /sys/, /usr/src/etc/ 2.11BSD Description: Repeat-By: Fix: See part 0 (the README) for the Description, the Reason and the instructions on how update your system. This is part 15 of 22 The setup documentation was updated to reflect the fact that the xp driver (in both the GENERIC kernel and standalone utilities) prints the xptype address now. This prevents the use of obsolete/wrong information from the hardcopy documents if the address changes due to rebuilding the GENERIC kernel. *** /usr/doc/2.10/setup.2.11/2.t.old Wed Dec 19 09:48:28 1990 --- /usr/doc/2.10/setup.2.11/2.t Sat May 4 20:35:36 1991 *************** *** 2,8 **** .\" All rights reserved. The Berkeley software License Agreement .\" specifies the terms and conditions for redistribution. .\" ! .\" @(#)2.t 1.0 (Contel) 7/5/90 .\" .ds lq `` .ds rq '' --- 2,8 ---- .\" All rights reserved. The Berkeley software License Agreement .\" specifies the terms and conditions for redistribution. .\" ! .\" @(#)2.t 1.1 (Contel) 5/4/91 .\" .ds lq `` .ds rq '' *************** *** 79,84 **** --- 79,88 ---- sure that the write ring is not inserted. Then use the normal bootstrap ROM, console monitor or other bootstrap to boot from the tape. + .PP + NOTE: The boot blocks expect the CSR of the booting controller in r0 + and the unit number in r1. + .PP If no other means are available, the following code can be keyed in and executed at (say) 0100000 to boot from a TM tape drive (the magic number 172526 is the address of the TM-11 current memory address register; *************** *** 87,97 **** .DS .TS l l. 012700 (mov $172526, r0) 172526 010040 (mov r0, -(r0)) 012740 (mov $60003, -(r0)) ! 060003 000777 (br .) .TE .DE --- 91,103 ---- .DS .TS l l. + 012700 (mov $unit, r1) + 000000 (normally unit 0) 012700 (mov $172526, r0) 172526 010040 (mov r0, -(r0)) 012740 (mov $60003, -(r0)) ! 060003 (if unit 1 use 060403, etc) 000777 (br .) .TE .DE *************** *** 126,141 **** 94 94 + + .TE .DE - The bootstrap can be forced to set up the machine for a different - class of PDP-11 by placing an appropriate value in the console switch register - (if there is one) while booting it. - The value to use is the PDP-11 class, interpreted as an \fIoctal\fP number - (use, for example, 070 for an 11/70). - \fBWarning:\fP some old DEC bootstraps use the switch - register to indicate where to boot from. - On such machines, if the value in the switch register indicates - an incorrect CPU, be sure to reset the switches immediately after - initiating the tape bootstrap. .PP You are now talking to the tape bootstrap monitor. At any point in the following procedure you can return --- 132,137 ---- *************** *** 155,161 **** Disk Root File System Size (1K-byte blocks) ! br 9120 (T300) hk 4158\(ua ra 7942 (RA60/80/81/82, RD54, RC25) 4850 (RD51/52/53) --- 151,157 ---- Disk Root File System Size (1K-byte blocks) ! br 9120 (T300 - not in the GENERIC kernel) hk 4158\(ua ra 7942 (RA60/80/81/82, RD54, RC25) 4850 (RD51/52/53) *************** *** 199,205 **** 072 Ampex Capricorn 073 SI, CDC 9775 (direct) 074 SI 6100, Fuji Eagle 2351A ! 075 Emulex SC01B or SI 9400, Fuji 160 076 Emulex SC-21, Ampex 815 cylinder RM05 077 Diva Comp V, Ampex 9300 .TE --- 195,201 ---- 072 Ampex Capricorn 073 SI, CDC 9775 (direct) 074 SI 6100, Fuji Eagle 2351A ! 075 Emulex SC01B/SC03B or SI 9400, Fuji 160 (in RM80 mode) 076 Emulex SC-21, Ampex 815 cylinder RM05 077 Diva Comp V, Ampex 9300 .TE *************** *** 207,228 **** Check the drive type number in your controller manual, or halt the CPU and examine this register. If the value does not correspond to the actual drive type, ! you must place the correct value in the switch ! register after the tape bootstrap is running ! and before any attempt is made to access the drive. This will override the drive type register. This value must be present at the time each program (including the bootstrap itself) first tries to access the disk. ! On machines without a switch register, the \fIxptype\fP ! variable can be patched in memory. After starting each utility but before accessing the disk, halt the CPU, place the new drive type ! number at the proper memory location with the console switches or monitor, ! and then continue. The location of \fIxptype\fP in each utility is ! .\"CHECK - XXX ! mkfs: 034146, restor: 040054, icheck: 035002 and boot: 0634640 ! (the location for boot is higher because it relocates itself). Once UNIX itself is booted (see section ``\fBStep 4: booting UNIX\fP'') you must ! patch it also. .PP Finally, determine the proper interleaving factors \fIm\fP and \fIn\fP for your disk and CPU combination from the following table. --- 203,225 ---- Check the drive type number in your controller manual, or halt the CPU and examine this register. If the value does not correspond to the actual drive type, ! you must patch the \fIxptype\fP variable in memory ! before any attempt is made to access the drive. This will override the drive type register. This value must be present at the time each program (including the bootstrap itself) first tries to access the disk. ! After starting each utility but before accessing the disk, halt the CPU, place the new drive type ! number at the proper memory location using the front panel or monitor ! and then continue. The address of \fIxptype\fP in each utility is ! printed out on the console the first time the disc is accessed. ! Because \fBboot\fP relocates itself you must remember to add 0600000 ! to the address of \fIxptype\fP. ! .PP Once UNIX itself is booted (see section ``\fBStep 4: booting UNIX\fP'') you must ! patch it also. The \fIxp\fP driver in the \fBGENERIC\fP kernel prints to ! the console the address of \fIxp_drive\fP and \fIxp_controller\fP and delays ! for about 10 seconds. .PP Finally, determine the proper interleaving factors \fIm\fP and \fIn\fP for your disk and CPU combination from the following table. *************** *** 382,397 **** \fBNote:\fP If you are booting from an \fIxp\fP with a drive type that is not recognized, it will be necessary to patch the system before it first accesses the root file system. ! Halt the processor after it ! has begun printing the version string but before it has finished printing ! the ``mem = ...'' strings. Place the drive type number corresponding to your drive ! .\"CHECK - XXX ! at location 010622; ! the address for ! the first controller's CSR is 046552. If you plan to use any drives other than 0 before you recompile ! the system, you should patch these locations. Make the patches and continue the CPU. The value before patching must be zero. If it is not, you have halted too late and should try again. --- 379,399 ---- \fBNote:\fP If you are booting from an \fIxp\fP with a drive type that is not recognized, it will be necessary to patch the system before it first accesses the root file system. ! The \fBGENERIC\fP kernel \fIxp\fP driver prints out the addresses of ! \fIxp_drive\fP and \fIxp_controller\fP and then delays for 10 seconds ! (approximately). ! Halt the processor after it has printed out the addresses ! but before the disk has been accessed. ! .PP Place the drive type number corresponding to your drive ! at the address of \fIxp_drive\fP plus 2. Modify only the low byte, the ! high byte is the drive unit number. ! The address for the first controller's CSR is \fIxp_controller\fP plus 4. ! It should be noted that at present the kernel may only be booted from a ! controller at the standard/first CSR. If you plan to use any drives other than 0 before you recompile ! the system, you should patch the location for those drives. The \fIxp_drive\fP ! structure in the \fBGENERIC\fP kernel is 012 bytes long. Make the patches and continue the CPU. The value before patching must be zero. If it is not, you have halted too late and should try again. *************** *** 461,467 **** l l l. boot driver devices _ ! bruboot br Contel BR1538/BR1711 hkuboot hk RK06/07 rauboot ra RA60/80/81/82, RC25, RD51/52/53/54, RX50 rkuboot rk RK05 --- 463,469 ---- l l l. boot driver devices _ ! bruboot br Contel BR1538/BR1711 (not in the \fBGENERIC\fP kernel) hkuboot hk RK06/07 rauboot ra RA60/80/81/82, RC25, RD51/52/53/54, RX50 rkuboot rk RK05 *************** *** 472,478 **** rm03uboot xp RM02/03 rm05uboot xp RM05 or SI 9500, CDC 9766 si51uboot xp SI 6100, Fujitsu Eagle 2351A ! si94uboot xp Emulex SC01B or SI 9400, Fujitsu 160 .TE .DE Once this is done, booting from this disk will load and execute the block --- 474,480 ---- rm03uboot xp RM02/03 rm05uboot xp RM05 or SI 9500, CDC 9766 si51uboot xp SI 6100, Fujitsu Eagle 2351A ! si94uboot xp Emulex SC01B/SC03B or SI 9400, Fujitsu 160 .TE .DE Once this is done, booting from this disk will load and execute the block *************** *** 482,489 **** .DS .TS lw(1.5i) l. - \fB>boot\fP (printed by some block 0 boots) - .B \fInn\fPBoot \fR(printed by /boot)\fP : --- 484,489 ---- *************** *** 490,496 **** .R .TE .DE - The '>' is the prompt from the first bootstrap. It automatically boots /\fIboot\fP for you; if /\fIboot\fP is not found, the system will hang/loop forever. It is a very small and simple program, however, and can only --- 490,495 ---- *************** *** 596,602 **** DEC TM02/03, TE16/TU45/TU77 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV ht0; sync DEC TS11, TU80/TS05 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV ts0; sync DEC TM11, TU10/TE10/TS03 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync ! DEC TQK50, TK50 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV tu0; sync EMULEX TC11 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync .TE .DE --- 595,601 ---- DEC TM02/03, TE16/TU45/TU77 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV ht0; sync DEC TS11, TU80/TS05 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV ts0; sync DEC TM11, TU10/TE10/TS03 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync ! DEC TQK50, TK50/TU81 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV tu0; sync EMULEX TC11 \fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync .TE .DE