From: Alexy Khrabrov <braver@pobox.com>
To: Alexy Khrabrov <braver@pobox.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Wide negotiation fails with 80->68 LVD adapter?
Date: Sat, 26 Oct 2002 10:53:09 -0400 [thread overview]
Message-ID: <20021026145309.GA7695@angle.setup.org> (raw)
In-Reply-To: <20021022221958.GA17112@angle.setup.org>
OK, I've got the CSC (Corpsys) "sca2lvd" adapters and tried them
with my Barracuda ST150176LC's. The adapters look much more solid
than the anonymous Taiwan-made "v1.1" ones. The CSC adapters have
two ig red LEDs onboard, the inner part of the circuit board
has a cover, etc.
However, they too failed to spin my drives at 160, only at 80.
I went back and enabled Wide Negotiation, then trying
to set speed at 160 caused Adaptec 7899 to recognize
the drives as ASYN, hangup, decreasing it to 80 led to their
recognition as 80 and working fine.
I went back and tried the "v1.1" adapters in that setting,
Wide Negotiation enabled, 80 sync speed, and they worked
at the same speed (as measured by copying a 5 GB from
the 160 drive). Doh.
So I reread the drive manual, which says that
Barracuda 50 drives support ANSI SCSI, SCSI-2 and SCSI-3
(Fast-20 and Fast-40), which it says are the same
as Ultra-1 and Ultra-2 for Fast-20/40, respectively.
Mysteriously, Ultra2 is referred to as Ultra80 elsewhere,
so looks like Fast-40 _is_ 80? If SCSI veterans could
clarify this, I'd see how 40=80... Especially, given
aic7xxx says something about 80 (40 MHz) in parentheses...
In all cases, seems that it's really the drive, Barracuda 50
family is Ultra2 <=> Ultra80 (right?) but I was able to
enable Wide Negotiation and set speed to 80, and aic7xxx v6.2.8
showed them registered at 80. I'm just curious if I still could
kinda spin them up to 160 anyways... :-)
Hence, so far, both SCA<->68 LVD adapters worked as advertised.
I'm going to get a real 160 SCA drive and test it further.
In the same vein, if I do end up getting an Ultra 320 card,
and I will get an Adaptec one, what should I look for in the
drive to see if it's capable of supporting 320? I'm interested
in Ultra160 drives, usually SCA ones I can get at closeouts,
but I heard (in the Ultra320 thread) that they can spin at 320
in case they support "HBA" -- can someone please elaborate?
Many thanks, I'll put together a SCA<->68 mini-HOWTO based
on this.
--
Cheers,
Alexy Khrabrov :: www.setup.org :: Age Quod Agis
next prev parent reply other threads:[~2002-10-26 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 5:14 Wide negotiation fails with 80->68 LVD adapter? Alexy Khrabrov
2002-10-21 16:34 ` Doug Ledford
2002-10-22 2:00 ` Alexy Khrabrov
2002-10-22 5:13 ` Dan Jones
2002-10-22 3:24 ` Alexy Khrabrov
2002-10-22 5:30 ` Dan Jones
2002-10-22 16:16 ` Alexy Khrabrov
2002-10-22 17:03 ` Doug Ledford
2002-10-22 22:19 ` Alexy Khrabrov
2002-10-26 14:53 ` Alexy Khrabrov [this message]
2002-10-26 16:00 ` Doug Ledford
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=20021026145309.GA7695@angle.setup.org \
--to=braver@pobox.com \
--cc=linux-scsi@vger.kernel.org \
/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).