The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jkunz@unixag-kl.fh-kl.de (Jochen Kunz)
Subject: [pups] 2.11BSD device config trouble
Date: Thu, 1 May 2003 02:24:50 -0700	[thread overview]
Message-ID: <20030501092450.GE1481@oblina.unixag-kl.fh-kl.de> (raw)
In-Reply-To: <200304301843.h3UIhBa22154@moe.2bsd.com>; from sms@2BSD.COM on Wed, Apr 30, 2003 at 11:43:11 %z

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]

On 2003.04.30 11:43 Steven M. Schultz wrote:

> > Sounds like a funny bug?
> 	Yes, it does. A bug in the parsing. Why it does not affect
> all the lines is unknown.   Perhaps some trailing whitespace
> caused the parser to exhibit the bug.
Maybe I get some time at the VCFE to investigate this. (Showing 
visitors "live hacking". ;-) )

> > But if I try to use /dev/ttyl1 I get a message about a unknown
> interrupt
> > and the output of /dev/ttyl1 hangs after the first character.
> 	What is the exact message?
Sorry don't know. I may be able to reproduce the error later. I got PSU 
trouble when I wanted to do this yesterday...

> 	That would seem to indicate that the device is interrupting
> but not at the expected vector.
If I use a different vector (e.g. 404) it tells me that the vector is 
wrong when booting. Maybe I can use a VAX with NetBSD for some 
"probing".... 
> > I have a M3106 DZQ11 that I can use instead.
> 	Definitely worth trying.
But when I was compiling the kernel with the new driver the machine 
crashed. The PSU simply stoped working. :-((( It worked again when I 
pulled all non-essential cards and the TK50. Maybe I overloaded the 
PSU? Maybe I will need a new PSU soon? If everything fails I can use 
the BA215 for the PDP-11. I have several spare PSUs for that box. But a 
BA215 is not the "right", "contemporary" enclosure for PDP-11/73. 
> I did the the same thing - wondered why I could never get a
> clean	file system.   Then I realized what was going on.
Nice to hear that I am not the only one who made that mistake. ;-)
-- 



tschüß,
           Jochen

Homepage: http://www.unixag-kl.fh-kl.de/~jkunz



  reply	other threads:[~2003-05-01  9:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 18:43 Steven M. Schultz
2003-05-01  9:24 ` Jochen Kunz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-01 19:14 Michael Sokolov
2003-05-01 13:49 Norman Wilson
2003-05-01  4:04 Steven M. Schultz
2003-05-01  3:30 Carl Lowenstein
2003-05-01  3:48 ` Gregg C Levine
2003-04-30 16:03 Steven M. Schultz
2003-04-30 15:56 Steven M. Schultz
2003-04-30 16:58 ` Jochen Kunz
2003-04-29 22:48 Steven M. Schultz
2003-04-30  8:24 ` Jochen Kunz
2003-04-30 13:40   ` David Evans
2003-04-30 16:23     ` Jochen Kunz
2003-04-30 16:59       ` David Evans
2003-04-29 21:54 Jochen Kunz

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=20030501092450.GE1481@oblina.unixag-kl.fh-kl.de \
    --to=jkunz@unixag-kl.fh-kl.de \
    /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).