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: Wed, 30 Apr 2003 18:58:26 +0200	[thread overview]
Message-ID: <20030430185826.R196974@MissSophie.unixag-kl.fh-kl.de> (raw)
In-Reply-To: <200304301556.h3UFuwb20269@moe.2bsd.com>; from sms@2BSD.COM on Wed, Apr 30, 2003 at 17:56:58 CEST

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

On 2003.04.30 17:56 Steven M. Schultz wrote:

> 	Interesting.   I do not recall any particular problem getting 
> 	additional DL devices recognized (the 11/93 had 7 of them).
As already mentioned: If I add comments at the end of the lines it
works:
cn      1 176540 344    5       cnrint  cnxint  # kl/dl-11 (on mvx11-aa)
cn      2 176550 354    5       cnrint  cnxint  # kl/dl-11 (on mvx11-aa)
cn      3 176560 364    5       cnrint  cnxint  # kl/dl-11 (on mvx11-aa)
cn 1 csr 176540 vector 344 attached
cn 2 csr 176550 vector 354 attached
cn 3 csr 176560 vector 364 attached
Sounds like a funny bug? 

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. 

> 	If you do 
> 		nm /unix | egrep 'cnxint|cnrint' 
> 	what do you see?
# nm /unix | egrep 'cnxint|cnrint' 
007402 T _cnrint
007624 T _cnxint
000050 t cnrint
000060 t cnxint

> 	Yes, it's a little better.  Not as nice as a DHQ-11 though
I have a M3106 DZQ11 that I can use instead. 

> I forget the exact error you were getting on the DHV but if it was
> 'no interrupt' then it might be that the DHV clone is not behaving
> exactly like a DEC DHV
The DHV is a DEC M3104:
dhv ? csr 160440 vector 310 didn't interrupt.
The DL11 card is a clone made by Sigma. 

> How are you rebooting?  With the "reboot" command or by using the
> 'halt' button?   
[...]
Noticed that already. I am really not used to Unix stuff of that age.
;-) 
-- 


tschüß,
       Jochen

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





  reply	other threads:[~2003-04-30 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 15:56 Steven M. Schultz
2003-04-30 16:58 ` 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 18:43 Steven M. Schultz
2003-05-01  9:24 ` Jochen Kunz
2003-04-30 16:03 Steven M. Schultz
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=20030430185826.R196974@MissSophie.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).