The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: michi@michiw.org (Michael Werner)
Subject: [pups] Problems booting PDP11/40 using vtserver
Date: Sun, 27 Jan 2002 19:03:24 +0100 (CET)	[thread overview]
Message-ID: <Pine.NEB.4.21.0201271901240.3240-100000@server.michiw.org> (raw)

Hi there,

I have my PDP11/40 connected to a MicroVAX 2 (running NetBSD/vax
1.5.2) via serial line and want to boot a 2.9BSD or 2.11BSD using the
vtserver software.
When I toggle in vtserver's boot code, the first file is being loaded
correctly by the PDP. Then, following the instructions in vtserver
documentation, the serial line should be used as a serial console - and
some text should appear! And this is the problem: I don't get any output.

When manually sending characters from the PDP, there is no problem.
I've set the serial line characteristics to:
Speed 2400, Character Size 8, Modem Control enabled, and RTS/CTS flow
control disabled. (I've changed these characteristics in many ways with
stty, but still no success...)
Using a break-out-box, I switched RTS/CTS and DTR/CTS flow control on and
off, forced the CTS line to be on, etc., but it still didn't work.
After successfully loading the bootloader via vtserver, the PDP's CPU goes
into an endless loop.

So, my question: Does anybody know what's going wrong here?

Thanks in advance - Michi





             reply	other threads:[~2002-01-27 18:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-27 18:03 Michael Werner [this message]
2002-01-29 16:38 ` Johnny Billquist
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 17:36 Fred N. van Kempen
2002-01-30  3:20 John Holden
2002-01-28 23:11 John Holden
2002-01-26 16:38 Michael Werner
2002-01-28 22:08 ` Warren Toomey
2002-01-28 22:53 ` Johnny Billquist
2002-01-29 13:16   ` Michael Werner
2002-01-29  5:10 ` Kirk B. Davis

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=Pine.NEB.4.21.0201271901240.3240-100000@server.michiw.org \
    --to=michi@michiw.org \
    /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).