The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] 2.9 kernel compile
Date: Wed, 11 Feb 2015 11:20:54 -0500 (EST)	[thread overview]
Message-ID: <20150211162054.1496F18C096@mercury.lcs.mit.edu> (raw)

    > From: Jacob Ritorto

    > I think it's something to do with the fact that he compiled it to run on
    > an 11/23. Maybe it lacks unibus support.

No, the UNIBUS and QBUS appear (from the programming level) to be identical.
There are subtle differences (the /23 and its devices can address more than
256KB of memory, and some devices have minor differences between the QBUS and
UBIBUS - e.g. the QBUS DZ has only 4 lines, not 8), but in general, they
should be interchangeable.

    > Maybe something to do with clock differences.

Again, if it boots at all, that's not it. (The vanilla /23 doesn't have a
software-controllable clock, and when booting Unix on one, one has to leave
the clock switched off till UNIX is running - at least, for the early versions
of UNIX.)

    > I fired 2.9MSCP up in simh emulating an 11/23 and it works fine. Just to
    > corroborate my hardware experience of it on the '34, I switch the cpu
    > emulation to 11/34 and got a mostly identical crash sequence as with my
    > real hardware.

Ah. Now we're getting somewhere! If the simulator crashes in the same way, it's
not flaky hardware (my first guess as to the cause).

What are the symptoms (in as much detail as you can give us)? What, if anything,
is printed before it dies?

    > I changed ...
    > UNIBUS_MAP = 0
    > to
    > UNIBUS_MAP = 1

The /34 doesn't have a UNIBUS map.

    Noel



             reply	other threads:[~2015-02-11 16:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 16:20 Noel Chiappa [this message]
2015-02-11 16:27 ` Cory Smelosky
2015-02-11 20:32 ` Jacob Ritorto
2015-02-11 20:38   ` Jacob Ritorto
2015-02-12  9:50 ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2015-02-12 15:44 Noel Chiappa
2015-02-12 15:27 Noel Chiappa
2015-02-13  2:20 ` Dave Horsfall
2015-02-12 13:47 Noel Chiappa
2015-02-12 14:16 ` Jacob Ritorto
2015-02-13  2:15   ` Dave Horsfall
2015-02-12  3:43 Noel Chiappa
2015-02-11 21:14 Noel Chiappa
2015-02-12  3:23 ` Jacob Ritorto
2015-02-11 16:37 Noel Chiappa
2015-02-11 15:47 Jacob Ritorto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150211162054.1496F18C096@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).