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:23:49 +0200	[thread overview]
Message-ID: <20030430182349.N196974@MissSophie.unixag-kl.fh-kl.de> (raw)
In-Reply-To: <20030430094032.A7330@bcr10.uwaterloo.ca>; from dfevans@bbcr.uwaterloo.ca on Wed, Apr 30, 2003 at 15:40:32 CEST

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

On 2003.04.30 15:40 David Evans wrote:

>   I didn't see my other post go through; 
I got it only via private mail.

> have you tried adding some comments
> to the end of this line?  Perhaps the autoconfig parser becomes
> confused if there aren't any.
Hmm. 
[...]
I added comments at the end of the lines and now it works:

April 30 17:29:29 init: configure system

dhv ? csr 160440 vector 310 didn't interrupt.
ra 0 csr 172150 vector 154 vectorset attached
ra 1 csr 160334 vector 764 vectorset attached
rx ? csr 177170 vector 264 skipped:  No CSR.
tms 0 csr 174500 vector 260 vectorset attached
ts 0 csr 172520 vector 224 attached
cn 1 csr 176540 vector 344 attached
cn 2 csr 176550 vector 354 attached
cn 3 csr 176560 vector 364 attached

Hmmm. No manpage for cn/dl/kl? Major / minor device numbers?
[reading the kernel source]
Aha. /dev/ttyl1 is what I am looking for. But the interrupt vector seams
to be wrong. 

But still trouble with the dhv. Maybe wrong interrupt vector too? Maybe
I compile a kernel with support for a DZQ11... 

> > But I would prefere to get the DHV11 working. It seams that this
> > device is more suitable for multi user operation. 
>   Mine is at least correctly identified by autoconfig, though I've
> never attached a terminal to it to see whether the ports actually do
> anything.
Normaly I use the console for booting only and then I telnet to the
machine. But I wane connect some terminals to the PDP-11 at the VCFe, so
the visitors can log in play around. 

[fsck trouble]
>   Is the disk write-inhibited?
No. It seams that I made the mistake to reboot using reboot(8) insted of
power cycling the machine when fsck modified the file system. Didn't
notice that / was mounted r/w. 
-- 


tschüß,
       Jochen

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





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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2003-04-30 16:59       ` David Evans
  -- 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-30 15:56 Steven M. Schultz
2003-04-30 16:58 ` Jochen Kunz
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=20030430182349.N196974@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).