[pups] 2.11BSD boot hangs.

Hi. Yesterday I installed 2.11BSD on my PDP11/73. Everything went fine up to the first time when UNIX was booted. The kernel came up, init was started, autoconfig run and printed out the devices it had (not) found. My disk and tape were found but then, after printing: ----- 73Boot from tms(0,0,0) at 0174500 : ra(0,0)unix Boot: bootdev=02400 bootcsr=0172150 2.11 BSD UNIX #115: Sat Apr 22 19:07:25 PDT 2000 sms1@curly.2bsd.com:/usr/src/sys/GENERIC ra0: Ver 3 mod 3 ra0: RD54 size=311200 phys mem = 4186112 avail mem = 3962176 user mem = 307200 June 8 21:21:24 init: configure system hk ? csr 177440 vector 210 skipped: No CSR. ht ? csr 172440 vector 224 skipped: No CSR. ra 0 csr 172150 vector 154 vectorset attached rl ? csr 174400 vector 160 skipped: No CSR. tm ? csr 172520 vector 224 skipped: No CSR. tms 0 csr 174500 vector 260 vectorset attached ts ? csr 172520 vector 224 skipped: No CSR. xp ? csr 176700 vector 254 skipped: No CSR. ----- it hangs. Characters I type into the terminal are echod, but nothing else happens. The "Run" LED at the front panel is of. I tried with an other CPU und memory card, but the same happend. System configuration: 11/73 (M8192), one with FP accel. or one without. (Jumpers W1..W6 in, W7..W9 out, so that the CPU enters ODT at power up.) 4MB or 1MB memory card (non DEC) Sigma DLV11-J clone for console (CSR 1765{0,1,2}0 and 177560) TK50 with TQK50 (CSR 174500) RA54, last week reformated on a MV2000 with RQDX3 (CSR 172150) BA23 from a MVII. BTW: What serial parameters does 2.11BSD use? The first time I booted UNIX I got garbage after "user mem = 307200". I seted the vt220 to 7e1 and this worked, but is it correct? -- tschuess, Jochen Homepage: http://www.unixag-kl.fh-kl.de/~jkunz Received: (from major@localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id EAA53205 for pups-liszt; Tue, 27 Feb 2001 04:35:02 +1100 (EST) (envelope-from owner-pups(a)minnie.cs.adfa.edu.au) Received: from grumpy.usu.edu (grumpy.usu.edu [129.123.1.86]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id EAA53196 for <PUPS(a)MINNIE.CS.ADFA.EDU.AU>AU>; Tue, 27 Feb 2001 04:34:59 +1100 (EST) (envelope-from IVIE(a)cc.usu.edu) Received: from cc.usu.edu by cc.usu.edu (PMDF V5.2-32 #39375) id <01K0K9U87TRK9ODB68(a)cc.usu.edu> for PUPS(a)MINNIE.CS.ADFA.EDU.AU; Mon, 26 Feb 2001 10:31:41 MST Date: Mon, 26 Feb 2001 10:31:41 -0700 (MST) From: Roger Ivie <IVIE(a)cc.usu.edu> Subject: Re: [pups] Swap device in V6? To: PUPS(a)minnie.cs.adfa.edu.au Message-id: <01K0K9U87UPE9ODB68(a)cc.usu.edu> X-VMS-To: PUPS(a)MINNIE.CS.ADFA.EDU.AU MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-pups(a)minnie.cs.adfa.edu.au Precedence: bulk Ian King said: Yeah, I figured this out a while ago. Unfortunately, I'm in the middle of changing employers so everything's in boxes at the moment. Basically, the swap space is hard-coded into the device drivers. If you take a look at, for example, the RK05 driver you'll see that one of the drives is smaller than the others. That extra space is the swap space. I forget how the rest of the system is informed of the swap space, but it's done in the disk driver sources IIRC. Roger Ivie ivie(a)cc.usu.edu Received: (from major@localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id EAA53322 for pups-liszt; Tue, 27 Feb 2001 04:55:47 +1100 (EST) (envelope-from owner-pups(a)minnie.cs.adfa.edu.au) Received: from arundel.fortyfour.org (138bus2.tampabay.rr.com [24.94.138.2]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id EAA53318 for <PUPS(a)minnie.cs.adfa.edu.au>au>; Tue, 27 Feb 2001 04:55:43 +1100 (EST) (envelope-from kwellsch(a)tampabay.rr.com) Received: from tampabay.rr.com (localhost [127.0.0.1]) by arundel.fortyfour.org (8.11.2/8.11.2) with ESMTP id f1QHpnL27849; Mon, 26 Feb 2001 12:51:49 -0500 (EST) Message-ID: <3A9A97B5.4EBD13A4(a)tampabay.rr.com> Date: Mon, 26 Feb 2001 12:51:49 -0500 From: Ken Wellsch <kwellsch(a)tampabay.rr.com> X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.0.38 i386) X-Accept-Language: en MIME-Version: 1.0 To: Roger Ivie <IVIE(a)cc.usu.edu> CC: PUPS(a)minnie.cs.adfa.edu.au Subject: Re: [pups] Swap device in V6? References: <01K0K9U87UPE9ODB68(a)cc.usu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-pups(a)minnie.cs.adfa.edu.au Precedence: bulk Roger Ivie wrote: I took a quick look at this this morning and as Roger says, the kernel is built with a wired in swap. In the case of the kernel 'rkunix,' in looking at usr/sys/run or something like that, I see they are wiring the swap to be device major=0 and minor=0 which is the root RK05 drive. Looking at the code it seems the first 4000 blocks are file system and a following 782 (or something like that) are for swap. The "ps" command source appears to be poking around /dev looking for a block device that matches the kernel value for swapdev (or something like that) and confirming it is a block device. Yet I see I have /dev/rk0 mknod'ed 0/0 and it is a block device but "ps" still gripes about "no swap device." So I'm missing something I guess. -- Ken Received: (from major@localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id FAA53659 for pups-liszt; Tue, 27 Feb 2001 05:39:14 +1100 (EST) (envelope-from owner-pups(a)minnie.cs.adfa.edu.au) Received: from moe.2bsd.com (MOE.2BSD.COM [206.139.202.200]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id FAA53655 for <pups(a)minnie.cs.adfa.edu.au>au>; Tue, 27 Feb 2001 05:39:10 +1100 (EST) (envelope-from sms(a)moe.2bsd.com) Received: (from sms@localhost) by moe.2bsd.com (8.10.1/8.10.1) id f1QIMNt09941 for pups(a)minnie.cs.adfa.edu.au; Mon, 26 Feb 2001 10:22:23 -0800 (PST) Date: Mon, 26 Feb 2001 10:22:23 -0800 (PST) From: "Steven M. Schultz" <sms(a)moe.2bsd.com> Message-Id: <200102261822.f1QIMNt09941(a)moe.2bsd.com> To: pups(a)minnie.cs.adfa.edu.au Subject: Re: [pups] 2.11BSD boot hangs. Sender: owner-pups(a)minnie.cs.adfa.edu.au Precedence: bulk Hi - That looks good - and familiar ;) The next thing that should have come out is the '# ' single user prompt. That sounds like the system 'halt'ed for some (unknown) reason. Sigh - that kernel should work fine, especially with a RQDX3/RD54. I am at a loss to explain/diagnose the problem. There is a jumper (I forget which one) that enables/disables the 'halt' instruction. If 'halt' is disabled then the 'halt' instruction is treated as a 'nop' even in kernel mode. If 'halt' is enabled then the console ODT will be entered if the kernel executes a halt. Looks like we'll have to try and solve this the hard way ;( After the system hangs press the 'halt' button on the front of the machine and note the PC - hopefully that value will give a clue as to where the kernel is at the time (likely in a clock interrupt). Yes, 7e1 is correct - a legacy setting from eons ago. Steven Schultz sms(a)moe.2bsd.com