From: geoff@plan9.bell-labs.com geoff@plan9.bell-labs.com
Subject: SCSI woes.
Date: Sun, 13 Jul 1997 17:12:08 -0400 [thread overview]
Message-ID: <19970713211208.eY838yw55ZJQi04-nto6D0MyJ0uY_T_fYeDZdr7gqZo@z> (raw)
I have used the AHA1542CP in several machines; I think I've used it
with the Seagate ST12400N and on another occasion with bigger disks
and 9pcfs. I don't think I've ever seen your symptoms. You've got
the 1542 i/o port base set to 0x330, the drive's SCSI id set to 0, and
the bus is terminated correctly (if you've only a single SCSI device,
it should have termination enabled internally or have a SCSI
terminator attached)? b.com will only look at 0x330 for a SCSI host
adapter. Have you configured the adapter with Adaptec's `SCSISelect'
program, accessible at boot time with control-a? SCSISelect should
also be able to probe the disk a little, as a sanity check.
Disabling plug-and-play also disables the 1542CP's BIOS (because it
then effectively becomes a 1542CF but the BIOS is for the 1542CP and
the versions don't match), which I don't believe is needed if you only
run Plan 9.
An unrelated potential problem is that the 1542 has a built-in floppy
controller that may need to be disabled (switch 5) if your system
already has one.
The SEE ALSO section of scuzz(8) is a good place to find out where to
learn more about SCSI; there's also a newer book called something like
`The SCSI and IDE Standards' that's quite good. A quick introduction,
geared to FreeBSD, can be found through
`http://www.freebsd.org/handbook/handbook.html' (it's
`http://www.freebsd.org/handbook/handbook127.html' today, but they
keep renumbering it).
next reply other threads:[~1997-07-13 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-13 21:12 geoff [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-07-14 17:16 geoff
1997-07-14 17:04 Berry
1997-07-14 16:49 presotto
1997-07-14 13:17 jmk
1997-07-14 6:43 Lucio
1997-07-13 14:55 Lucio
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=19970713211208.eY838yw55ZJQi04-nto6D0MyJ0uY_T_fYeDZdr7gqZo@z \
--to=geoff@plan9.bell-labs.com \
/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).