From mboxrd@z Thu Jan 1 00:00:00 1970 From: cube1@home.com (Jay Jaeger) Date: Sun, 04 Feb 2001 16:09:33 -0600 Subject: [pups] Booting V6 on 11/34 vs 11/34A ?? Message-ID: <4.3.2.7.2.20010204155043.045c7d50@cirithi> That RK05 image boots on an 11/34A just fine. (I own one. Trust me. It just works. No fiddling required). Perhaps you have a plain 11/34, and perhaps there is some difference that matters. But they should both have MMU, but perhaps the MMU in the 34A is different than a 34 in some odd way. Do you have floating point? Maybe that's the problem. You could always try mini-unix... 8-) That should run (it ran on an 11/20). Jay Date: Wed, 31 Jan 2001 09:13:30 +1100 (EST) From: Warren Toomey Subject: Re: [pups] A bootable disk image for a PDP-11/34? In article by Carl Lowenstein: > Just from the historical point of view, note that the first major > file on a genuine 6th Edition distribution tape _is_ a bootable > RK05 image. Something like 4000 blocks. > > carl Yes, but it doesn't boot on an 11/34 :( That's the problem. Cheers, Warren - --- --- Jay R. Jaeger The Computer Collection cube1 at home.com visit http://members.home.net/thecomputercollection Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id JAA61690 for pups-liszt; Mon, 5 Feb 2001 09:48:38 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from mailserver.nktelco.net (mailserver.nktelco.net [216.206.77.3]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id JAA61686 for ; Mon, 5 Feb 2001 09:48:34 +1100 (EST) (envelope-from chd at nktelco.net) Received: by mailserver.nktelco.net from localhost (router,SLMail V4.1); Sun, 04 Feb 2001 17:35:38 -0500 for Received: from nktelco.net [63.238.116.228] by mailserver.nktelco.net [216.206.77.3] (SLmail 4.1.3395) with ESMTP id D0A2B493F87E11D4B0A800500424CC10 for ; Sun, 04 Feb 2001 17:35:37 -0500 Message-ID: <3A7DDBA8.3C69A521 at nktelco.net> Date: Sun, 04 Feb 2001 17:46:00 -0500 From: "Chuck Dickman" X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: pups at minnie.cs.adfa.edu.au Subject: [pups] Hardware config for 2.11BSD Installation on PDP-11/73 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SLUIDL: 14D76A5B-F97F11D4-B0A80050-0424CC10 Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk Greetings, I have a PDP-11/73 on which I have installed 2.11 BSD from the PUPS archives. I have a few hardware configurations questions that I hope someone might be able to help me with. The memory board that I have was made by Clearpoint Inc. The board has the markings Q-RAM 44B REV. B and GSB-2. Unfortunately, I have no documentation for the board. The board originally had 1 MB installed, and I added another 1 MB of chips. The extra chips were not recognized though. Does anyone have information on the jumper settings for this board? I have two MSCP controllers installed. One is a CMD CQD-220/M SCSI controller with one drive attached, CSR is the first MSCP controller, and unit is set to 0. The second is an RQDX3 with an RX50 attached. It is set with CSR at the second MSCP controller address. The jumpers are set for unit 1. The result is that I have a SCSI drive at DU0 and the RX50's at DU4 and DU5 during boot. DU0 is ra0 and DU4 is ra12 in 2.11 BSD. If I change the jumpers on RQDX3 to unit 2, I boot at DU8, the first RX50, but I can no longer access the floppies from 2.11 BSD. Looking at the sources, it seems that the drive number is limited to 0-7, but the controller seems to want unit number 8. What am I missing? This seems to occur both in the kernel and in the standalone installation system. Chuck Dickman chd at nktelco.net Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id LAA62190 for pups-liszt; Mon, 5 Feb 2001 11:01:37 +1100 (EST) (envelope-from owner-pups at 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 LAA62186 for ; Mon, 5 Feb 2001 11:01:33 +1100 (EST) (envelope-from sms at moe.2bsd.com) Received: (from sms at localhost) by moe.2bsd.com (8.10.1/8.10.1) id f14NjXN00172 for pups at minnie.cs.adfa.edu.au; Sun, 4 Feb 2001 15:45:33 -0800 (PST) Date: Sun, 4 Feb 2001 15:45:33 -0800 (PST) From: "Steven M. Schultz" Message-Id: <200102042345.f14NjXN00172 at moe.2bsd.com> To: pups at minnie.cs.adfa.edu.au Subject: Re: [pups] Hardware config for 2.11BSD Installation on PDP-11/73 Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk Hi - > From: "Chuck Dickman" > The memory board that I have was made by Clearpoint Inc. The board 'fraid I can't be of help with the memory board - that's not my area of expertise. > I have two MSCP controllers installed. One is a CMD CQD-220/M SCSI Ah, but I can help with getting the dual MSCP controller question. My 11/73 is similar - it has an Emulex UC08 and the original RQDX3 (with an RD54 and a RX03). > DU0 is ra0 and DU4 is ra12 in 2.11 BSD. If I change the jumpers on > RQDX3 to unit 2, I boot at DU8, the first RX50, but I can no longer > access the floppies from 2.11 BSD. Looking at the sources, it seems > that the drive number is limited to 0-7, but the controller seems to > want unit number 8. What am I missing? This seems to occur both in > the kernel and in the standalone installation system. Ignore anything you might know about DU numbers ;) 2.11 numbers the drives 0 thru 7 on _each_ controller. Thus 'ra0' thru 'ra7' are on the first controller, 'ra8' thru 'ra15' on the second controller and so on. There is a maximum of 4 controllers supported (two bits in the minor device number). The standalone I/O system uses device names of the form: dev(ctlr, unit, part) where 'ctlr' is the controller number (0 thru 3), the 'unit' number is 0 thru 7 and the 'part' is the partition number (0 thru 7). So, to access the first drive on the second controller from a standalone program the name would be: ra(1,0,0) you probably will be prompted for the CSR since 'boot' and friends only know about the first controller's address. Once the kernel is loaded you access drives on the 2nd controller with device names such as /dev/ra8a, /dev/ra9a, and so on. The "sparse" numbering was chosen (eons and eons ago) to make the MSCP disks look more like the traditional disc controllers which allowed for 8 drives per controller. In my /etc/dtab file I have: ra ? 172154 154 5 raintr # uda50, rqdx1/2/3 ra ? 172150 0 5 raintr # 2nd uda50/uc08 From the console ODT prompt (I've an older MXV11 boot set up) I use "172150 du 0" to boot from the SCSI disk attached to the UC08. When the system is up the RD54 (which is unit 0 on the other MSCP controller) is accessed as 'ra8' (and the RX03 which is unit 1 accessed as 'ra9'). It's pretty simple and regular once one knows what is going on ;) Steven Schultz sms at to.gd-es.com Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id MAA62645 for pups-liszt; Mon, 5 Feb 2001 12:52:20 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from mailserver.nktelco.net (mailserver.nktelco.net [216.206.77.3]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id MAA62637 for ; Mon, 5 Feb 2001 12:52:16 +1100 (EST) (envelope-from chd at nktelco.net) Received: by mailserver.nktelco.net from localhost (router,SLMail V4.1); Sun, 04 Feb 2001 20:39:27 -0500 for Received: from nktelco.net [63.238.116.228] by mailserver.nktelco.net [216.206.77.3] (SLmail 4.1.3395) with ESMTP id 8253E300FAEF11D4B0A800500424CC10 for ; Sun, 04 Feb 2001 20:39:27 -0500 Message-ID: <3A7E06BE.F5687560 at nktelco.net> Date: Sun, 04 Feb 2001 20:49:50 -0500 From: "Chuck Dickman" X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: pups at minnie.cs.adfa.edu.au Subject: Re: [pups] Hardware config for 2.11BSD Installation on PDP-11/73] Content-Type: multipart/mixed; boundary="------------F423B2C7167AA36041F4AE52" X-SLUIDL: 14D76C4B-F97F11D4-B0A80050-0424CC10 Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk This is a multi-part message in MIME format. --------------F423B2C7167AA36041F4AE52 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Steven M. Schultz" wrote: > > Hi - > What you described here makes sense and was my first impression of what should happen, but my experience is different. > > In my /etc/dtab file I have: > > ra ? 172154 154 5 raintr # uda50, rqdx1/2/3 > ra ? 172150 0 5 raintr # 2nd uda50/uc08 My /etc/dtab is: ra ? 172150 154 5 raintr # uda50, rqdx1/2/3 ra ? 160334 160 5 raintr # secondary mscp The CQD220 is at 172150 and the RXDX3 is at 160334. Is 172154 a valid MSCP address? It must be, cause it works for you. The docs I have show 160334. On booting the 11/73 and starting 2.11 BSD the following occurs: DU8 and DU9 at boot are the RX50 drives on the second controller. The floppy in DU8 contains the installation standalone utilities that were part of the installation tape, including icheck. ------------ Testing in progress - Please wait Memory Size is 1024 K Bytes 9 Step memory test Step 1 2 3 4 5 6 7 8 9 Message 04 Entering Dialog mode Commands are Help, Boot, List, Setup, Map and Test. Type a command then press the RETURN key: B DU8 Trying DU8 Starting system from DU8 .83Boot from ra(1,0,0) at 0160334 .: ra(1,0,0)/icheck .ra(1,0,0) err op=89 sts=3 .ra(1,0,0) !online .: ra(0,0,0)/unix .Boot: bootdev=02400 bootcsr=0172150 . 2.11 BSD UNIX #10: Fri Nov 24 16:52:18 PST 2000 root at mars.chd-net:/usr/src/sys/MARS ra0: Ver 6 mod 13 ra0: RA82 size=1295849 attaching qe0 csr 174440 qe0: DEC DELQA addr 08:00:2b:0e:24:7c attaching lo0 phys mem = 1048576 avail mem = 725696 user mem = 307200 February 1 23:38:41 init: configure system hk ? csr 177440 vector 210 skipped: No autoconfig routines. ht ? csr 172440 vector 224 skipped: No autoconfig routines. ra 0 csr 172150 vector 154 vectorset attached ra 1 csr 160334 vector 160 vectorset attached rl ? csr 174400 vector 160 skipped: No autoconfig routines. tm ? csr 172520 vector 224 skipped: No autoconfig routines. ts 0 csr 172520 vector 224 attached xp ? csr 176700 vector 254 skipped: No autoconfig routines. erase, kill ^U, intr ^C # # mount /dev/ra8a /mnt/rx0 ra1: Ver 4 mod 3 ra8 st=3 sb=0 fl=0 en=9 /dev/ra8a on /mnt/rx0: Input/output error : not found : not found # mount /dev/ra9a /mnt/rx0 ra9 st=3 sb=0 fl=0 en=9 /dev/ra9a on /mnt/rx0: Input/output error # > > It's pretty simple and regular once one knows what is going on ;) > I agree that it is pretty simple as you describe it and it is what I expected, but it does not seem to be as I see it here. Could the problem be that I am booting from the second controller? Should all the controllers be jumpered for unit 0? Now that I think about it, it may be the boot firmware that is uncooperative. If I set the RQDX3 for unit 0, I cannot boot from the second controller's first disk, but I can from the second. So, I should set all the controller unit numbers to 0. The restriction is that the boot device must be visible to the firmware. Make sense? ... OK, I moved the RQDX3 to unit 0, and the boot floppy to the second drive. The boot is then: -------------- Testing in progress - Please wait Memory Size is 1024 K Bytes 9 Step memory test Step 1 2 3 4 5 6 7 8 9 Message 04 Entering Dialog mode Commands are Help, Boot, List, Setup, Map and Test. Type a command then press the RETURN key: B DU1 Trying DU1 Starting system from DU1 .83Boot from ra(1,1,0) at 0160334 .: ra(0,0,0)/unix .Boot: bootdev=02400 bootcsr=0172150 . 2.11 BSD UNIX #10: Fri Nov 24 16:52:18 PST 2000 root at mars.chd-net:/usr/src/sys/MARS ra0: Ver 6 mod 13 ra0: RA82 size=1295849 attaching qe0 csr 174440 qe0: DEC DELQA addr 08:00:2b:0e:24:7c attaching lo0 phys mem = 1048576 avail mem = 725696 user mem = 307200 February 1 23:38:41 init: configure system hk ? csr 177440 vector 210 skipped: No autoconfig routines. ht ? csr 172440 vector 224 skipped: No autoconfig routines. ra 0 csr 172150 vector 154 vectorset attached ra 1 csr 160334 vector 160 vectorset attached rl ? csr 174400 vector 160 skipped: No autoconfig routines. tm ? csr 172520 vector 224 skipped: No autoconfig routines. ts 0 csr 172520 vector 224 attached xp ? csr 176700 vector 254 skipped: No autoconfig routines. erase, kill ^U, intr ^C # mount /dev/ra9a /mnt/rx0 ra1: Ver 4 mod 3 ra9: RX50 size=800 # ls /mnt/rx0 boot icheck restor unix disklabel mkfs rx50toroot # > Steven Schultz > sms at to.gd-es.com Thanks for helping me work through this. It looks like the boot device must be within the first 8 devices that the firmware can see, but 2.11 BSD wants all the unit number jumpers set to 0. Chuck Dickman chd at nktelco.net --------------F423B2C7167AA36041F4AE52 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3A7E052A.D2F195E1 at nktelco.net> Date: Sun, 04 Feb 2001 20:43:06 -0500 From: Chuck Dickman X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Steven M. Schultz" Subject: Re: [pups] Hardware config for 2.11BSD Installation on PDP-11/73 References: <200102042345.f14NjXN00172 at moe.2bsd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "Steven M. Schultz" wrote: > > Hi - > What you described here makes sense and was my first impression of what should happen, but my experience is different. > > In my /etc/dtab file I have: > > ra ? 172154 154 5 raintr # uda50, rqdx1/2/3 > ra ? 172150 0 5 raintr # 2nd uda50/uc08 My /etc/dtab is: ra ? 172150 154 5 raintr # uda50, rqdx1/2/3 ra ? 160334 160 5 raintr # secondary mscp The CQD220 is at 172150 and the RXDX3 is at 160334. Is 172154 a valid MSCP address? It must be, cause it works for you. The docs I have show 160334. On booting the 11/73 and starting 2.11 BSD the following occurs: DU8 and DU9 at boot are the RX50 drives on the second controller. The floppy in DU8 contains the installation standalone utilities that were part of the installation tape, including icheck. ------------ Testing in progress - Please wait Memory Size is 1024 K Bytes 9 Step memory test Step 1 2 3 4 5 6 7 8 9 Message 04 Entering Dialog mode Commands are Help, Boot, List, Setup, Map and Test. Type a command then press the RETURN key: B DU8 Trying DU8 Starting system from DU8 .83Boot from ra(1,0,0) at 0160334 .: ra(1,0,0)/icheck .ra(1,0,0) err op=89 sts=3 .ra(1,0,0) !online .: ra(0,0,0)/unix .Boot: bootdev=02400 bootcsr=0172150 . 2.11 BSD UNIX #10: Fri Nov 24 16:52:18 PST 2000 root at mars.chd-net:/usr/src/sys/MARS ra0: Ver 6 mod 13 ra0: RA82 size=1295849 attaching qe0 csr 174440 qe0: DEC DELQA addr 08:00:2b:0e:24:7c attaching lo0 phys mem = 1048576 avail mem = 725696 user mem = 307200 February 1 23:38:41 init: configure system hk ? csr 177440 vector 210 skipped: No autoconfig routines. ht ? csr 172440 vector 224 skipped: No autoconfig routines. ra 0 csr 172150 vector 154 vectorset attached ra 1 csr 160334 vector 160 vectorset attached rl ? csr 174400 vector 160 skipped: No autoconfig routines. tm ? csr 172520 vector 224 skipped: No autoconfig routines. ts 0 csr 172520 vector 224 attached xp ? csr 176700 vector 254 skipped: No autoconfig routines. erase, kill ^U, intr ^C # # mount /dev/ra8a /mnt/rx0 ra1: Ver 4 mod 3 ra8 st=3 sb=0 fl=0 en=9 /dev/ra8a on /mnt/rx0: Input/output error : not found : not found # mount /dev/ra9a /mnt/rx0 ra9 st=3 sb=0 fl=0 en=9 /dev/ra9a on /mnt/rx0: Input/output error # > > It's pretty simple and regular once one knows what is going on ;) > I agree that it is pretty simple as you describe it and it is what I expected, but it does not seem to be as I see it here. Could the problem be that I am booting from the second controller? Should all the controllers be jumpered for unit 0? Now that I think about it, it may be the boot firmware that is uncooperative. If I set the RQDX3 for unit 0, I cannot boot from the second controller's first disk, but I can from the second. So, I should set all the controller unit numbers to 0. The restriction is that the boot device must be visible to the firmware. Make sense? ... OK, I moved the RQDX3 to unit 0, and the boot floppy to the second drive. The boot is then: -------------- Testing in progress - Please wait Memory Size is 1024 K Bytes 9 Step memory test Step 1 2 3 4 5 6 7 8 9 Message 04 Entering Dialog mode Commands are Help, Boot, List, Setup, Map and Test. Type a command then press the RETURN key: B DU1 Trying DU1 Starting system from DU1 .83Boot from ra(1,1,0) at 0160334 .: ra(0,0,0)/unix .Boot: bootdev=02400 bootcsr=0172150 . 2.11 BSD UNIX #10: Fri Nov 24 16:52:18 PST 2000 root at mars.chd-net:/usr/src/sys/MARS ra0: Ver 6 mod 13 ra0: RA82 size=1295849 attaching qe0 csr 174440 qe0: DEC DELQA addr 08:00:2b:0e:24:7c attaching lo0 phys mem = 1048576 avail mem = 725696 user mem = 307200 February 1 23:38:41 init: configure system hk ? csr 177440 vector 210 skipped: No autoconfig routines. ht ? csr 172440 vector 224 skipped: No autoconfig routines. ra 0 csr 172150 vector 154 vectorset attached ra 1 csr 160334 vector 160 vectorset attached rl ? csr 174400 vector 160 skipped: No autoconfig routines. tm ? csr 172520 vector 224 skipped: No autoconfig routines. ts 0 csr 172520 vector 224 attached xp ? csr 176700 vector 254 skipped: No autoconfig routines. erase, kill ^U, intr ^C # mount /dev/ra9a /mnt/rx0 ra1: Ver 4 mod 3 ra9: RX50 size=800 # ls /mnt/rx0 boot icheck restor unix disklabel mkfs rx50toroot # > Steven Schultz > sms at to.gd-es.com Thanks for helping me work through this. It looks like the boot device must be within the first 8 devices that the firmware can see, but 2.11 BSD wants all the unit number jumpers set to 0. Chuck Dickman chd at nktelco.net --------------F423B2C7167AA36041F4AE52-- Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id NAA62886 for pups-liszt; Mon, 5 Feb 2001 13:46:33 +1100 (EST) (envelope-from owner-pups at 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 NAA62882 for ; Mon, 5 Feb 2001 13:46:28 +1100 (EST) (envelope-from sms at moe.2bsd.com) Received: (from sms at localhost) by moe.2bsd.com (8.10.1/8.10.1) id f152Zs901247; Sun, 4 Feb 2001 18:35:54 -0800 (PST) Date: Sun, 4 Feb 2001 18:35:54 -0800 (PST) From: "Steven M. Schultz" Message-Id: <200102050235.f152Zs901247 at moe.2bsd.com> To: chd at nktelco.net, sms at moe.2bsd.com Subject: Re: [pups] Hardware config for 2.11BSD Installation on PDP-11/73 Cc: pups at minnie.cs.adfa.edu.au Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk Hi - > From: "Chuck Dickman" > What you described here makes sense and was my first impression of > what should happen, but my experience is different. I'm wondering if the console/boot firmware might not be the cause of some of the confusion. > My /etc/dtab is: > > ra ? 172150 154 5 raintr # uda50, rqdx1/2/3 > ra ? 160334 160 5 raintr # secondary mscp Looks good. With 2.11 you can, if you want, leave the interrupt vector as 0, the kernel will allocate an available vector and tell the MSCP controller what vector to use. > The CQD220 is at 172150 and the RXDX3 is at 160334. Is 172154 a valid > MSCP address? It must be, cause it works for you. The docs I have > show 160334. As long as it doesn't conflict with anything else on the system it's valid ;-) The system came with the RQDX3 and I worked with the RD54 for a while before adding the UC08 - when I added the UC08 I just picked the next free CSR which happened to be 172154. > DU8 and DU9 at boot are the RX50 drives on the second controller. The > floppy in DU8 contains the installation standalone utilities that were > part of the installation tape, including icheck. > > ------------ > .83Boot from ra(1,0,0) at 0160334 > .: ra(1,0,0)/icheck It probably doesn't hurt anything but I would leave off the '/' > .ra(1,0,0) err op=89 sts=3 > .ra(1,0,0) !online op=89 is the "ONLINE" command and a status of 3 means the unit didn't go 'online'. That is very strange since 'boot' was obviously loaded from the drive/controller. What I am wondering now is: does the boot monitor pass 0 or 8 thru as the unit number? If it's expecting 8 or 9 then that might be the problem because boot and the 2.11 kernel only deal with 0 thru 7 > .: ra(0,0,0)/unix > .Boot: bootdev=02400 bootcsr=0172150 > . > hk ? csr 177440 vector 210 skipped: No autoconfig routines. > ht ? csr 172440 vector 224 skipped: No autoconfig routines. > ra 0 csr 172150 vector 154 vectorset attached > ra 1 csr 160334 vector 160 vectorset attached Ok, that looks encouraging. > # mount /dev/ra8a /mnt/rx0 > ra1: Ver 4 mod 3 > ra8 st=3 sb=0 fl=0 en=9 > /dev/ra8a on /mnt/rx0: Input/output error > : not found > : not found > # mount /dev/ra9a /mnt/rx0 > ra9 st=3 sb=0 fl=0 en=9 > /dev/ra9a on /mnt/rx0: Input/output error Same as before - the "online" command is failing for reason(s) unknown as yet. > I agree that it is pretty simple as you describe it and it is what I expected, > but it does not seem to be as I see it here. Could the problem be that I am > booting from the second controller? Should all the controllers be jumpered I boot from the second controller all the time. If I weren't so lazy (and the BA23 so narrow and hard to work in ;)) I'd have swapped the UC08 and RQDX3 around a long time ago. As it is now I have to hit ^C during the POST and at the BOOT> prompt I enter "172154 DU 0" to boot from the second controller. > for unit 0? Now that I think about it, it may be the boot firmware that is Yes, if given a choice (and I don't know how this is done) all the controllers need to start from 0. If the "base unit" of a controller is 8 then I think the problem is that the controller is expecting values such as 8, 9, etc in the 'mscp_unit' part of the MSCP packet. That would explain the failure to "online unit 0" - the controller is expecting to be told "online unit 8". > controller's first disk, but I can from the second. So, I should set all the > controller unit numbers to 0. The restriction is that the boot device > must be visible to the firmware. Make sense? Yes. I think the 'restriction' in this case is 2.11 - it doesn't know how to deal with units other than 0 thru 7. > Thanks for helping me work through this. It looks like the boot device > must be within the first 8 devices that the firmware can see, but 2.11 BSD > wants all the unit number jumpers set to 0. Quite welcome! The boot monitor can load anything, but once 'boot' (or the kernel) is loaded they do not know how to deal with unit=8. Steven Schultz sms at moe.2bsd.com Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id OAA63034 for pups-liszt; Mon, 5 Feb 2001 14:23:08 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from mailserver.nktelco.net (mailserver.nktelco.net [216.206.77.3]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id OAA63030 for ; Mon, 5 Feb 2001 14:23:03 +1100 (EST) (envelope-from chd at nktelco.net) Received: by mailserver.nktelco.net from localhost (router,SLMail V4.1); Sun, 04 Feb 2001 22:10:04 -0500 for Received: from nktelco.net [63.238.116.228] by mailserver.nktelco.net [216.206.77.3] (SLmail 4.1.3395) with ESMTP id 8253E3E2FAEF11D4B0A800500424CC10 for plus 1 more; Sun, 04 Feb 2001 22:10:04 -0500 Message-ID: <3A7E1BFB.98767635 at nktelco.net> Date: Sun, 04 Feb 2001 22:20:27 -0500 From: "Chuck Dickman" X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.14 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Steven M. Schultz" CC: pups at minnie.cs.adfa.edu.au Subject: Re: [pups] Hardware config for 2.11BSD Installation on PDP-11/73 References: <200102050235.f152Zs901247 at moe.2bsd.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SLUIDL: 14D76D51-F97F11D4-B0A80050-0424CC10 Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk "Steven M. Schultz" wrote: > > > "Chuck Dickman" wrote: > > > > Thanks for helping me work through this. It looks like the boot device > > must be within the first 8 devices that the firmware can see, but 2.11 BSD > > wants all the unit number jumpers set to 0. > > Quite welcome! The boot monitor can load anything, but once 'boot' > (or the kernel) is loaded they do not know how to deal with unit=8. I think that was what I was trying to say, but you said it better. Thanks. > > Steven Schultz > sms at moe.2bsd.com Now if someone could help be double my memory. :-) Chuck Dickman chd at nktelco.net Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id XAA65456 for pups-liszt; Mon, 5 Feb 2001 23:39:58 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from mud.stack.nl (mud.stack.nl [131.155.141.98]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id XAA65452 for ; Mon, 5 Feb 2001 23:39:53 +1100 (EST) (envelope-from martijnb at stack.nl) Received: by mud.stack.nl (Postfix, from userid 587) id 3AC547F18; Mon, 5 Feb 2001 13:37:53 +0100 (CET) Date: Mon, 5 Feb 2001 13:37:53 +0100 From: Martijn van Buul To: pups at minnie.cs.adfa.edu.au Subject: [pups] Y2K problem in ftpd? Message-ID: <20010205133753.A23455 at mud.stack.nl> Reply-To: Martijn van Buul Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.3i Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk Hi. A friendly user pointed me to this obvious error: (part of a typescript, an FTP session to my PDP, running 2.11BSD) ncftp /usr/home/martijnb> ls -la foobar.c -rw-r--r-- 1 martijnb users 106 Jan 15 15:25 foobar.c ncftp /usr/home/martijnb> quote mdtm foobar.c 191010115144152 (mdtm should return the datestamp, in the form yyyymmddhhmm. ftpd thinks that it is 19101, and chops off the last digit of the filedate..) Things go wrong when you try to get an allready existing file: ncftp /usr/home/martijnb > get foobar.c The local file "foobar.c" already exists. Local: 133 bytes, dated Mon Feb 5 13:25:59 2001. Remote: 133 bytes, dated Thu Oct 13 04:44:15 1910. [O]verwrite? [A]ppend to? [S]kip? [N]ew Name? > Hmm. I'll see if I can figure out a quick patch :) -- Martijn van Buul - Pino at dohd.org - http://www.stack.nl/~martijnb/ Geek code: G-- - Visit OuterSpace: mud.stack.nl 3333 Kees J. Bot: The sum of CPU power and user brain power is a constant. Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id AAA65628 for pups-liszt; Tue, 6 Feb 2001 00:14:23 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from fgh.geac.com.au ([203.32.189.100]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id AAA65624 for ; Tue, 6 Feb 2001 00:14:21 +1100 (EST) (envelope-from dave at horsfall.org) Received: from localhost (dave at localhost) by fgh.geac.com.au (8.11.2/8.11.2) with ESMTP id f15D9on12003 for ; Tue, 6 Feb 2001 00:09:50 +1100 (EST) X-Authentication-Warning: fgh.au.geac.com: dave owned process doing -bs Date: Tue, 6 Feb 2001 00:09:49 +1100 (EST) From: Dave Horsfall X-X-Sender: To: PDP Unix Preservation Society Subject: Re: [pups] Y2K problem in ftpd? In-Reply-To: <20010205133753.A23455 at mud.stack.nl> Message-ID: X-No-Archive: Yes X-Disclaimer: "Me, speak for us?" X-Witty-Saying: "Mobius Strip - See other side for instructions" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk On Mon, 5 Feb 2001, Martijn van Buul wrote: > ncftp /usr/home/martijnb> quote mdtm foobar.c > 191010115144152 > > (mdtm should return the datestamp, in the form yyyymmddhhmm. ftpd > thinks that it is 19101, and chops off the last digit of the filedate..) Yep, that's a sure sign, which (cough, cough) I have personally seen on some (cough, cough) Y2K-compliant software supported by (cough, cough) A Large Software Company. No, I wasn't personally responsible for that code :-) > I'll see if I can figure out a quick patch :) Beware of the Y2K.1 bug :-( Synopsis: In order to overcome the Y2K bug, we implement a quick fix, because we are too lazy to do it properly: IF last two digits == '00' THEN make first two digits == '20'. // Because we're gonna retire this stuff after 2000. So what happens in 2001? Well, you get 1901, 19101, etc. Sigh... Isn't that fix what got us into trouble in the first place? Disclaimer: None of Geac software exhibited the Y2K.1 bug, since we tested it thoroughly, for years 2000, 2001, etc: I make no comment on Y2K. -- Dave Horsfall CL VK2KFU dave at geac.com.au Ph: +61 2 9978-7493 Fx: * 9978-7490 Geac Computers P/L (ERP Division) 2/57 Christie St, St Leonards 2065, Australia Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id AAA65695 for pups-liszt; Tue, 6 Feb 2001 00:29:48 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from mud.stack.nl (mud.stack.nl [131.155.141.98]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id AAA65691 for ; Tue, 6 Feb 2001 00:29:45 +1100 (EST) (envelope-from martijnb at stack.nl) Received: by mud.stack.nl (Postfix, from userid 587) id 8FD117F18; Mon, 5 Feb 2001 14:27:46 +0100 (CET) Date: Mon, 5 Feb 2001 14:27:46 +0100 From: Martijn van Buul To: pups at minnie.cs.adfa.edu.au Subject: Re: [pups] Y2K problem in ftpd? Message-ID: <20010205142746.A24731 at mud.stack.nl> Reply-To: Martijn van Buul References: <20010205133753.A23455 at mud.stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.3i In-Reply-To: <20010205133753.A23455 at mud.stack.nl>; from pino at dohd.org on Mon, Feb 05, 2001 at 01:37:53PM +0100 Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk Martijn van Buul wrote: > I'll see if I can figure out a quick patch :) Done. A diff for /usr/src/libexec/ftpd/ftpcmd.y: 461,463c461,464 < "19%02d%02d%02d%02d%02d%02d", < t->tm_year, t->tm_mon+1, t->tm_mday, < t->tm_hour, t->tm_min, t->tm_sec); --- > "%04d%02d%02d%02d%02d%02d", > t->tm_year+1900, t->tm_mon+1, > t->tm_mday, t->tm_hour, t->tm_min, > t->tm_sec); Miraculously, this *reduces* the size of the binary by a whopping two bytes ;) -- Martijn van Buul - Pino at dohd.org - http://www.stack.nl/~martijnb/ Geek code: G-- - Visit OuterSpace: mud.stack.nl 3333 Kees J. Bot: The sum of CPU power and user brain power is a constant. Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id BAA65865 for pups-liszt; Tue, 6 Feb 2001 01:04:27 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from fgh.geac.com.au ([203.32.189.100]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id BAA65861 for ; Tue, 6 Feb 2001 01:04:25 +1100 (EST) (envelope-from dave at horsfall.org) Received: from localhost (dave at localhost) by fgh.geac.com.au (8.11.2/8.11.2) with ESMTP id f15DocZ18079 for ; Tue, 6 Feb 2001 00:50:38 +1100 (EST) X-Authentication-Warning: fgh.au.geac.com: dave owned process doing -bs Date: Tue, 6 Feb 2001 00:50:37 +1100 (EST) From: Dave Horsfall X-X-Sender: To: PDP Unix Preservation Society Subject: Re: [pups] Y2K problem in ftpd? In-Reply-To: <20010205142746.A24731 at mud.stack.nl> Message-ID: X-No-Archive: Yes X-Disclaimer: "Me, speak for us?" X-Witty-Saying: "Mobius Strip - See other side for instructions" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk On Mon, 5 Feb 2001, Martijn van Buul wrote: > < "19%02d%02d%02d%02d%02d%02d", > < t->tm_year, t->tm_mon+1, t->tm_mday, Dead giveaway... > Miraculously, this *reduces* the size of the binary by a whopping two > bytes ;) Well, we can find a job for you in writing PDP-11 bootstraps :-) -- Dave Horsfall CL VK2KFU dave at geac.com.au Ph: +61 2 9978-7493 Fx: * 9978-7490 Geac Computers P/L (ERP Division) 2/57 Christie St, St Leonards 2065, Australia Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id DAA66602 for pups-liszt; Tue, 6 Feb 2001 03:01:50 +1100 (EST) (envelope-from owner-pups at minnie.cs.adfa.edu.au) Received: from igas2.postoffice.co.uk (firewall-user at igas2-2.igas.postoffice.co.uk [194.152.87.163]) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id DAA66598 for ; Tue, 6 Feb 2001 03:01:44 +1100 (EST) (envelope-from robin.birch at postoffice.co.uk) From: robin.birch@postoffice.co.uk Received: by igas2.postoffice.co.uk; id PAA03738; Mon, 5 Feb 2001 15:58:24 GMT Received: from unknown(10.5.4.9) by igas2.postoffice.co.uk via smap (V5.0) id xma003421; Mon, 5 Feb 01 15:58:09 GMT Received: with SMTP id PAA25299; Mon, 5 Feb 2001 15:58:07 GMT Received: by postoffice.co.uk(Lotus SMTP MTA v4.6.6 (890.1 7-16-1999)) id 002569EA.0057991A ; Mon, 5 Feb 2001 15:56:48 +0000 X-Lotus-FromDomain: POSTOFFICE To: Dave Horsfall cc: PDP Unix Preservation Society Message-ID: <002569EA.00579852.00 at postoffice.co.uk> Date: Mon, 5 Feb 2001 15:46:48 +0000 Subject: Re: [pups] Y2K problem in ftpd? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk Dear All, IIRC the start of this thread stated that this was on a 2.11 system. If this was so has anyone submitted the patch to Steve Schultz for consideration as a formal update? Appologies if this has already been done. Rgds Robin Received: (from major at localhost) by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id EAA66960 for pups-liszt; Tue, 6 Feb 2001 04:01:38 +1100 (EST) (envelope-from owner-pups at 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 EAA66955 for ; Tue, 6 Feb 2001 04:01:30 +1100 (EST) (envelope-from sms at moe.2bsd.com) Received: (from sms at localhost) by moe.2bsd.com (8.10.1/8.10.1) id f15GpYd11283 for pups at minnie.cs.adfa.edu.au; Mon, 5 Feb 2001 08:51:34 -0800 (PST) Date: Mon, 5 Feb 2001 08:51:34 -0800 (PST) From: "Steven M. Schultz" Message-Id: <200102051651.f15GpYd11283 at moe.2bsd.com> To: pups at minnie.cs.adfa.edu.au Subject: Re: [pups] Y2K problem in ftpd? Sender: owner-pups at minnie.cs.adfa.edu.au Precedence: bulk Hi -- > From: robin.birch at postoffice.co.uk > IIRC the start of this thread stated that this was on a 2.11 system. If this > was so has anyone submitted the patch to Steve Schultz for consideration as a > formal update? Don't worry - I saw the thread. Consider the patch submitted :) I did find it fascinating that the bug slipped thru since at one time a (obviously not detailed enough) scan of the system for 'tm_year' references was done. Thanks! Steven Schultz sms at moe.2bsd.com