9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: James A. Robinson Jim.Robinson@Stanford.Edu
Subject: [9fans] NCR SCSI drivers
Date: Tue, 20 Oct 1998 13:47:17 -0700	[thread overview]
Message-ID: <19981020204717.7eNVRD143UlF4MOp_PJDmyNhx9ZNNjxDmLmDzsB1jYI@z> (raw)

> There ought not to be any other difficulties. The 875J is really just 
> an 875 with a different ID. Odd, really. 

I might be doing something wrong then. But after booting, I get
a whole slew of debugging:

	...
	ncr53c8xx: tpf = 137 scf = 4.0 xferp = 11 mhz = 1.825
	...
	
And then 

	scsi0: ncr53c8xx: port 0 irq 0 addr 0 size 0
	
and a config prompt. So it looks like it is scsi.c is calling
the ncr driver's reset, and the ncr driver thinks it succeeded.
However, I'm wondering about all the '0' values -- I don't know
if that is more of the same 'everything hidden by PCI' or not.

Once I enter the config info and type 'end' I get
	sysinit
	config w0
		devinit D6.0.0.0
	ncr53c8xx: 0: WDTN: target init 1
	ncr53c8xx: 0: WDTN: responding 1
	ncr53c8xx: 0: WDTN: response accepted
	ncr53c8xx: 0: SDTN: target init 12 15
	ncr53c8xx: 0: using 12 15
	ncr53c8xx: 0: SDTN: response accepted (status)
	D6.0.0.0 ready
	
which look like it just tried to access drive 0, but then it just sits
there. It doesn't access the disk, and doesn't print out anything else.

I've played around with the termination, and I'm sort of worried that the
system might not like me using a SCSI 1 cable to hook into an SCA->SCSI1
adapter on the seagate.

Anyone run into this before? Is it stalling on recognizing the hd?

Jim




             reply	other threads:[~1998-10-20 20:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-20 20:47 James [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-10-21 13:42 jmk
1998-10-21  9:29 James
1998-10-19 22:03 ngr

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=19981020204717.7eNVRD143UlF4MOp_PJDmyNhx9ZNNjxDmLmDzsB1jYI@z \
    --to=9fans@9fans.net \
    /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).