From owner-freebsd-scsi Sun Sep 14 00:22:56 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id AAA27621
for freebsd-scsi-outgoing; Sun, 14 Sep 1997 00:22:56 -0700 (PDT)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA27616;
Sun, 14 Sep 1997 00:22:49 -0700 (PDT)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id AAA01220; Sun, 14 Sep 1997 00:22:37 -0700 (PDT)
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199709140722.AAA01220@GndRsh.aac.dev.com>
Subject: Re: Patches on senderp-ppp.i-connect.net
In-Reply-To: <19970913200905.31425@hydrogen.nike.efn.org> from John-Mark Gurney at "Sep 13, 97 08:09:05 pm"
To: gurney_j@resnet.uoregon.edu
Date: Sun, 14 Sep 1997 00:22:36 -0700 (PDT)
Cc: Shimon@i-Connect.Net, freebsd-hackers@FreeBSD.ORG,
freebsd-scsi@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
> Rodney W. Grimes scribbled this message on Sep 13:
> > > Hi Y'all,
> > >
> > > This is just a bit of formality and a reminder:
> > >
> > > Any progamming logic (source, object, executable, etc.) that you may find
> > > on the computer known as sendero-ppp.i-connect.net (206.190.143.100), which
> > > does not clearly display a Copyright notice authorizing free distribution
> > > is proprietary, unpublished source code of Simon Shapiro, Atlas Telecom or
> > > both.
> >
> > I love the work you are doing, but the above statement is not correct.
> >
> > a) It is not ``proprietary'' unless you take legal and proper actions
> > to keep it as such. In most cases you have done just the opposite,
> > you've given pointers to it in a public forum.
> >
> > b) The action of making it avaliable to anyone other than yourself
> > is `publication'', thierfor the code is not ``unpublished''.
>
> if this is true.. and that simply letting people download load it means
> that the copyright is invalid (i.e. it's publicly avail), then why do we
> worry about GPL'd code?? it's publicly avail.. but we still have to adhear
> to the copyright attached... so why does this apply to his code?
My statement b) above says nothing about invalidating the copyright on
the file(s). It said that his claim to being ``unpublished source code''
would not hold up in court. Infact no where in my reply do I mention
copyright.
His base copyright is fully intact and binding, though missing a
few technical legal requirements (City and State for a filed US copyright)
his assertion of copyright infringement would hold up in a court. His
assertion that it is a proprietary, unpublished source code how ever
would not.
I am not a lawyer, but have and do spend a healthy chunk of money
in that area on a regular basis and have some first hand expertise
in watching just how a lawyer disects things like the first 8 lines
of dpt_pci.h, I am sure Greenly, Rottenberg, Evans and Brag as well
as a Black's legal dictionary would back me up on my assertion in b)
above.
> it also only in theory that published material is free... but case law
> has proven otherwise.. this is the basis for all intellectual property
> law...
I could get get Blacks and spend an hour showing you how many flaws
there are in the above 3 statements, but instead let me just make
3 statements back:
Published material is not free, unless there are attached conditions
to the copyright that are legally valid and true granting you rights
beyond what the copyright grants you.
Case law is only some % of the picture, you have to see if the
actual law as applied in a particular case decision matches the
current situation.
Intellectual property law has no single basis, and is comprised
of both actual written law and the cases tried using those laws
(commonly called case law). Infact that should apply to all law
as far as I can tell.
>
> > c) Your ftp server welcome message desen't even head any warnings
> > what so ever.
>
> well. that has been fixed... :)
Okay, it has warnings, but those warings are seriously lacking in
there legal correctness :-(. Folks don't try to write protection
mechanisms yourself unless you have a good understanding and first hand
experience with the applicable law.
I don't see anything in the login banner I couldn't get a good lawyer
to destroy in a few minutes. The word copyright doesn't even appear,
and I've already blasted the holes in ``unpublished''. And that
claim to ``proprietary'', well, thats blown by not taking steps to
protect it, kinda like a trademark. You'd really need a password
on the site to assert the unpublished and/or proprietary claims.
Kinda like laying a book in the book store with those claims on
it and a $0.00 price tag. I just don't think the claims would
have a leg to stand on in court. Most any company asserting
these claims require an NDA before you can even look at it,
let alone download it and use it!
--
Rod Grimes rgrimes@gndrsh.aac.dev.com
Accurate Automation, Inc. Reliable computers for FreeBSD
From owner-freebsd-scsi Sun Sep 14 11:21:51 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id LAA21616
for freebsd-scsi-outgoing; Sun, 14 Sep 1997 11:21:51 -0700 (PDT)
Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA21611;
Sun, 14 Sep 1997 11:21:46 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA01984;
Sun, 14 Sep 1997 12:21:36 -0600 (MDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA19937; Sun, 14 Sep 1997 12:21:33 -0600 (MDT)
Date: Sun, 14 Sep 1997 12:21:33 -0600 (MDT)
Message-Id: <199709141821.MAA19937@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Cc: Shimon@i-connect.net (Simon Shapiro), freebsd-hackers@freebsd.org,
freebsd-scsi@freebsd.org
Subject: Re: Patches on senderp-ppp.i-connect.net
In-Reply-To: <199709140137.SAA00731@GndRsh.aac.dev.com>
References: <XFMail.970913154942.Shimon@i-Connect.Net>
<199709140137.SAA00731@GndRsh.aac.dev.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
> a) It is not ``proprietary'' unless you take legal and proper actions
> to keep it as such. In most cases you have done just the opposite,
> you've given pointers to it in a public forum.
Correct.
> b) The action of making it avaliable to anyone other than yourself
> is `publication'', thierfor the code is not ``unpublished''.
Then AT&T/USL/Novell/SCO code isn't publication either, since they
contain the same wording. I'd tend to be believe that the above isn't
true.
> c) Your ftp server welcome message desen't even head any warnings
> what so ever.
I don't think it matters, since many ftp servers that distribute
copyrighted software don't have welcome messages. Welcome messages
aren't even standard on stock ftp server.
But, the first clause alone is enough to make things 'interesting.
Nate
From owner-freebsd-scsi Sun Sep 14 11:39:32 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id LAA22807
for freebsd-scsi-outgoing; Sun, 14 Sep 1997 11:39:32 -0700 (PDT)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA22799;
Sun, 14 Sep 1997 11:39:28 -0700 (PDT)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id LAA01564; Sun, 14 Sep 1997 11:38:45 -0700 (PDT)
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199709141838.LAA01564@GndRsh.aac.dev.com>
Subject: Re: Patches on senderp-ppp.i-connect.net
In-Reply-To: <199709141821.MAA19937@rocky.mt.sri.com> from Nate Williams at "Sep 14, 97 12:21:33 pm"
To: nate@mt.sri.com (Nate Williams)
Date: Sun, 14 Sep 1997 11:38:45 -0700 (PDT)
Cc: Shimon@i-connect.net, freebsd-hackers@freebsd.org,
freebsd-scsi@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
> > a) It is not ``proprietary'' unless you take legal and proper actions
> > to keep it as such. In most cases you have done just the opposite,
> > you've given pointers to it in a public forum.
>
> Correct.
>
> > b) The action of making it avaliable to anyone other than yourself
> > is `publication'', thierfor the code is not ``unpublished''.
>
> Then AT&T/USL/Novell/SCO code isn't publication either, since they
> contain the same wording. I'd tend to be believe that the above isn't
> true.
The AT&T/USL/Novell/SCO code is _only_ made avaliable under license
agreement, and the _signed_ license is what keeps it unpublished. So
you are correct, my statement was incomplete, whoever, Simons code
has been ``published'' since he did not protect himself with a
``license''.
> > c) Your ftp server welcome message desen't even head any warnings
> > what so ever.
>
> I don't think it matters, since many ftp servers that distribute
> copyrighted software don't have welcome messages. Welcome messages
> aren't even standard on stock ftp server.
People keep going back to ``copyright'' his copyright is fine, he
has copyriht protection, but, the other parts are pretty much blown.
Go back and even try and find the word copyright in my original
mail message...
> But, the first clause alone is enough to make things 'interesting.
Yep.....
--
Rod Grimes rgrimes@gndrsh.aac.dev.com
Accurate Automation, Inc. Reliable computers for FreeBSD
From owner-freebsd-scsi Sun Sep 14 12:50:41 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id MAA26235
for freebsd-scsi-outgoing; Sun, 14 Sep 1997 12:50:41 -0700 (PDT)
Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA26227
for <scsi@FreeBSD.ORG>; Sun, 14 Sep 1997 12:50:37 -0700 (PDT)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id NAA24360;
Sun, 14 Sep 1997 13:50:33 -0600 (MDT)
Message-Id: <199709141950.NAA24360@pluto.plutotech.com>
To: dag-erli@ifi.uio.no (Dag-Erling Coidan Sm rgrav)
cc: scsi@FreeBSD.ORG
Subject: Re: XP34550S / AHA2940UW refuses wide negotiation
In-reply-to: Your message of "13 Sep 1997 17:27:15 +0200."
<xzphgbpqlnw.fsf@hall.ifi.uio.no>
Date: Sun, 14 Sep 1997 13:50:27 -0600
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
>I recently upgraded my Adaptec 2940 to a 2940UW to take full advantage
>of my Quantum Atlas II. However, it seems that both the adapter and
>the disk are refusing wide negotiation.
No. Your narrow disk and cdrom drive are refusing wide negotiation.
The Quantum seems to be doing just fine. Boot with the "-v" boot
flag to be certain of what the negotiated speeds are.
>--
> * Finrod (INTJ) * Unix weenie * dag-erli@ifi.uio.no * cellular +47-92835919 *
> RFC1123: "Be liberal in what you accept, and conservative in what you send"
>
--
Justin T. Gibbs
===========================================
FreeBSD: Turning PCs into workstations
===========================================
From owner-freebsd-scsi Sun Sep 14 15:05:37 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id PAA03743
for freebsd-scsi-outgoing; Sun, 14 Sep 1997 15:05:37 -0700 (PDT)
Received: from usr09.primenet.com (tlambert@usr09.primenet.com [206.165.6.209])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA03723;
Sun, 14 Sep 1997 15:05:32 -0700 (PDT)
Received: (from tlambert@localhost)
by usr09.primenet.com (8.8.5/8.8.5) id PAA24060;
Sun, 14 Sep 1997 15:05:21 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199709142205.PAA24060@usr09.primenet.com>
Subject: Re: Patches on senderp-ppp.i-connect.net
To: nate@mt.sri.com (Nate Williams)
Date: Sun, 14 Sep 1997 22:05:20 +0000 (GMT)
Cc: rgrimes@gndrsh.aac.dev.com, Shimon@i-connect.net,
freebsd-hackers@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
In-Reply-To: <199709141821.MAA19937@rocky.mt.sri.com> from "Nate Williams" at Sep 14, 97 12:21:33 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
> > a) It is not ``proprietary'' unless you take legal and proper actions
> > to keep it as such. In most cases you have done just the opposite,
> > you've given pointers to it in a public forum.
>
> Correct.
Or it might be seen as "due dilligence"...
> > b) The action of making it avaliable to anyone other than yourself
> > is `publication'', thierfor the code is not ``unpublished''.
>
> Then AT&T/USL/Novell/SCO code isn't publication either, since they
> contain the same wording. I'd tend to be believe that the above isn't
> true.
You're right. Unpublished code can remain unpublished, however widely
distributed, so long as it is only distributed to a "select group".
Without controls on who can FTP the code, there is no group selection
enforced. This would fail to meet the criteria for distribution of
unpublished sources, I'm afraid. Which means that due dilligence isn't
met either.
>
> > c) Your ftp server welcome message desen't even head any warnings
> > what so ever.
>
> I don't think it matters, since many ftp servers that distribute
> copyrighted software don't have welcome messages. Welcome messages
> aren't even standard on stock ftp server.
>
> But, the first clause alone is enough to make things 'interesting.
Yup.
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
From owner-freebsd-scsi Sun Sep 14 17:29:36 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id RAA14108
for freebsd-scsi-outgoing; Sun, 14 Sep 1997 17:29:36 -0700 (PDT)
Received: from cenotaph.snafu.de (gw-deadnet.snafu.de [194.121.229.33])
by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA14103
for <freebsd-scsi@FreeBSD.ORG>; Sun, 14 Sep 1997 17:29:31 -0700 (PDT)
Received: by cenotaph.snafu.de
id m0xAP2e-000350C; Mon, 15 Sep 1997 02:29:28 +0200 (CEST)
(Smail-3.2.0.97 1997-Aug-19 #1)
Received: (qmail 13920 invoked from network); 12 Sep 1997 18:07:23 -0000
Received: from neologic.dritter.stock (@192.168.2.3)
by reality.dritter.stock with SMTP; 12 Sep 1997 18:07:23 -0000
Received: (qmail 557 invoked by uid 1001); 12 Sep 1997 18:27:38 -0000
Date: Fri, 12 Sep 1997 20:27:37 +0200 (CEST)
From: Mark Riekenberg <mark@reality.snafu.de>
X-Sender: mark@neologic.dritter.stock
Reply-To: mark@reality.snafu.de
To: freebsd-scsi@FreeBSD.ORG
Subject: phase error
Message-ID: <Pine.BSF.3.95.970912201705.544A-100000@neologic.dritter.stock>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
Hi!
In the last few days i experience some strange error messages from my
noname ncr 53c810:
ncr0: SCSI phase error fixup: CCB address mismatch (0xf0f2cc00 != 0xf0f0bc00)
np->ccb = 0xf0f0be00
sd0: phase change 6-2 3@00099dd0 resid=3.
ncr0: SCSI phase error fixup: CCB address mismatch (0xf0f2cc00 != 0xf0f0ba00)
np->ccb = 0xf0f0be00
sd0: phase change 6-2 3@00099dd0 resid=2.
sd0: phase change 6-2 3@00099dd0 resid=3.
sd0: phase change 6-2 3@00099dd0 resid=3.
ncr0: SCSI phase error fixup: CCB address mismatch (0xf0f2cc00 != 0xf0f0b800)
np->ccb = 0xf0f0be00
sd0: phase change 6-2 3@00099dd0 resid=3.
Is this something to worry about?
Apart from these messages nothing seems to be fucked up, but i slept better
before knowing them ;-) ...
tnx in advance,
mark.
---
FreeBSD 3.0-CURRENT #0: Mon Aug 18 03:41:07 CEST 1997
ncr0: <ncr 53c810 fast10 scsi> rev 0x02 int a irq 15 on pci0.8.0
ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo
scbus0 at ncr0 bus 0
sd0 at scbus0 target 0 lun 0
sd0: <IBM DCAS-34330 S61A> type 0 fixed SCSI 2
sd0: Direct-Access
sd0: 10.0 MB/s (100 ns, offset 8)
4134MB (8467200 512 byte sectors)
--
email: <mark@reality.snafu.de> PGP public key available
From owner-freebsd-scsi Tue Sep 16 01:08:53 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id BAA05855
for freebsd-scsi-outgoing; Tue, 16 Sep 1997 01:08:53 -0700 (PDT)
Received: from murkwood.gaffaneys.com (dialup2.gaffaneys.com [208.155.161.52])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA05836
for <scsi@freebsd.org>; Tue, 16 Sep 1997 01:08:48 -0700 (PDT)
Received: (from zach@localhost)
by murkwood.gaffaneys.com (8.8.7/8.8.6) id DAA10216;
Tue, 16 Sep 1997 03:09:07 -0500 (CDT)
From: Zach Heilig <zach@gaffaneys.com>
Message-ID: <19970916030907.64550@gaffaneys.com>
Date: Tue, 16 Sep 1997 03:09:07 -0500
To: scsi@freebsd.org
Subject: PCI Advansys controller...
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
There is a place in town that has a couple of PCI AdvanSys cards it wants to
get rid of. I happen to be in the market for a couple PCI scsi cards. The
salesman pointed me to a file on the AdvanSys ftp server
(ftp://ftp.advansys.com/pub/freebsd/freebsd.txt, dated 1/16/97) that noted ISA
support was supposed to be done and PCI support was near completion. And, are
these cards junk? (the ones he wants to sell are 930AU, I think).
Which version of FreeBSD has this? It must be -current, since a grep of LINT
doesn't show any matches for advansys in 2.2-stable.
This same store has two Symbios 53c875 based cards on back-order for me, but
they would cancel that order, if I got those AdvanSys cards.
How good of trade would that be (the Advansys cards are about half the price
of the Symbios cards, $80 vs. $150). I know the Symbios chip has the scripts
memory, and can offload some of the work from the host CPU, but exactly how
much of a win is that?
Thanks for any anwser.
--
Zach Heilig
From owner-freebsd-scsi Tue Sep 16 01:28:22 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id BAA10917
for freebsd-scsi-outgoing; Tue, 16 Sep 1997 01:28:22 -0700 (PDT)
Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA10907
for <scsi@FreeBSD.ORG>; Tue, 16 Sep 1997 01:28:17 -0700 (PDT)
Received: (from jmg@localhost)
by hydrogen.nike.efn.org (8.8.7/8.8.7) id BAA13439;
Tue, 16 Sep 1997 01:28:06 -0700 (PDT)
Message-ID: <19970916012806.54936@hydrogen.nike.efn.org>
Date: Tue, 16 Sep 1997 01:28:06 -0700
From: John-Mark Gurney <gurney_j@efn.org>
To: Zach Heilig <zach@gaffaneys.com>
Cc: scsi@FreeBSD.ORG
Subject: Re: PCI Advansys controller...
References: <19970916030907.64550@gaffaneys.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.69
In-Reply-To: <19970916030907.64550@gaffaneys.com>; from Zach Heilig on Tue, Sep 16, 1997 at 03:09:07AM -0500
Reply-To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Organization: Cu Networking
X-Operating-System: FreeBSD 2.2.1-RELEASE i386
X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4
X-Files: The truth is out there
X-URL: http://resnet.uoregon.edu/~gurney_j/
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
Zach Heilig scribbled this message on Sep 16:
> There is a place in town that has a couple of PCI AdvanSys cards it wants to
> get rid of. I happen to be in the market for a couple PCI scsi cards. The
> salesman pointed me to a file on the AdvanSys ftp server
> (ftp://ftp.advansys.com/pub/freebsd/freebsd.txt, dated 1/16/97) that noted ISA
> support was supposed to be done and PCI support was near completion. And, are
> these cards junk? (the ones he wants to sell are 930AU, I think).
>
> Which version of FreeBSD has this? It must be -current, since a grep of LINT
> doesn't show any matches for advansys in 2.2-stable.
currently.. the only version is the one that uses Justin Gibb's CAM
scsi code that will soon replace the current code.. once that is done,
then the driver for the cards will be included, (correct me if I remeber
wrong Justin)...
> This same store has two Symbios 53c875 based cards on back-order for me, but
> they would cancel that order, if I got those AdvanSys cards.
>
> How good of trade would that be (the Advansys cards are about half the price
> of the Symbios cards, $80 vs. $150). I know the Symbios chip has the scripts
> memory, and can offload some of the work from the host CPU, but exactly how
> much of a win is that?
Justin will have to answer this question.. but I am looking forward to
the time that FreeBSD does support them, as my supplier has the Advansys
cards, but doesn't have any of the ncr based cards...
ttyl..
--
John-Mark Gurney Modem/FAX: +1 541 683 6954
Cu Networking
Live in Peace, destroy Micro$oft, support free software, run FreeBSD
From owner-freebsd-scsi Tue Sep 16 04:15:23 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id EAA18507
for freebsd-scsi-outgoing; Tue, 16 Sep 1997 04:15:23 -0700 (PDT)
Received: from gatekeeper.acucobol.ie (gatekeeper.acucobol.ie [194.125.135.194])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA18477;
Tue, 16 Sep 1997 04:15:10 -0700 (PDT)
Received: (from daemon@localhost)
by gatekeeper.acucobol.ie (8.8.5/8.8.5) id MAA25170;
Tue, 16 Sep 1997 12:12:18 +0100 (IST)
Received: from guinness.acucobol.ie(194.125.135.195) by gatekeeper.acucobol.ie via smap (V2.0beta)
id xma025158; Tue, 16 Sep 97 12:12:15 +0100
Received: from guinness (localhost [127.0.0.1])
by guinness.acucobol.ie (8.8.5/8.8.5) with ESMTP id MAA27536;
Tue, 16 Sep 1997 12:15:38 +0100 (BST)
Message-Id: <199709161115.MAA27536@guinness.acucobol.ie>
From: "John McLaughlin" <John.McLaughlin@Acucobol.IE>
To: hardware@freebsd.org, scsi@freebsd.org
Subject: Adaptec 1542CP on Compaq Prosignia VS problems
Date: Tue, 16 Sep 1997 12:15:38 +0100
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
Hi,
I'm running 2.2.2 on the above, which has started to
intermittently give the following errors:
aha0: Bus dropped at unexpected time
aha0: Invalid bus phase/sequence
sd0(aha0:0:0): UNIT ATTENTION asc:29,0
sd0(aha0:0:0): Power on, reset, or bus device reset occurred
, retries:4
aha0: Invalid bus phase/sequence
aha0: Invalid bus phase/sequence
sd0(aha0:0:0): timed out
sd0(aha0:0:0): UNIT ATTENTION asc:29,0
sd0(aha0:0:0): Power on, reset, or bus device reset occurred
, retries:2
aha0: Invalid bus phase/sequence
sd0(aha0:0:0): UNIT ATTENTION asc:29,0
sd0(aha0:0:0): Power on, reset, or bus device reset occurred
, retries:4
And the dmesg output is:
Copyright (c) 1992-1997 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 2.2.2-RELEASE #0: Wed Jul 23 11:40:00 IST 1997
root@holsten.acucobol.ie:/usr/src/sys/compile/HOLSTEN
CPU: i486 DX2 (486-class CPU)
Origin = "GenuineIntel" Id = 0x435 Stepping=5
Features=0x3<FPU,VME>
real memory = 16777216 (16384K bytes)
avail memory = 14864384 (14516K bytes)
eisa0: <CPQ701 (System Board)>
Probing for devices on the EISA bus
eisa0:8 <CPQ4410=0xe114410> unknown device
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 not found at 0x280
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 not found at 0x2f8
sio2: disabled, not probed.
sio3: disabled, not probed.
lpt0 at 0x3bc-0x3c3 irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
fd1: 1.2MB 5.25in
aha0 at 0x330-0x333 irq 11 drq 5 on isa
aha0 waiting for scsi devices to settle
(aha0:0:0): "COMPAQ M2694ES-512 952B" type 0 fixed SCSI 2
sd0(aha0:0:0): Direct-Access 1001MB (2051000 512 byte sectors)
(aha0:2:0): "TANDBERG TDC 3600 =08:" type 1 removable SCSI 2
st0(aha0:2:0): Sequential-Access density code 0x0, drive empty
(aha0:4:0): "ARCHIVE Python 27871-XXX 4.BG" type 1 removable SCSI 2
st1(aha0:4:0): Sequential-Access density code 0x13, drive empty
lnc0 at 0x8800-0x8817 irq 10 drq 0 on eisa slot 8
lnc0: PCnet-32 VL-Bus address 00:80:5f:18:d9:9c
npx0 flags 0x1 on motherboard
npx0: INT 16 interface
It was working fine for about 6 weeks after the install,
before the started turning up regularly, so I'd guess it's either a
problem with the controller, or the disk. Is it possibly a problem
with the setup on the card, or possibly the fact that it's all sitting
inside a Compaq?
Any suggestions much appreciated.
Thanks,
John
----------------------------------------------------------------------
John McLaughlin | Acucobol Ireland Ltd.
IS Manager, Europe | South Co. Business Park
| Dublin 18, Ireland.
e-Mail: jmcl@Acucobol.IE | Phone: +353 1 294-0967
John.McLaughlin@Acucobol.IE | Fax: +353 1 294-0969
----------------------------------------------------------------------
From owner-freebsd-scsi Wed Sep 17 12:29:09 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id MAA04164
for freebsd-scsi-outgoing; Wed, 17 Sep 1997 12:29:09 -0700 (PDT)
Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA04159
for <scsi@FreeBSD.ORG>; Wed, 17 Sep 1997 12:29:04 -0700 (PDT)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id NAA11169;
Wed, 17 Sep 1997 13:28:34 -0600 (MDT)
Message-Id: <199709171928.NAA11169@pluto.plutotech.com>
X-Mailer: exmh version 2.0zeta 7/24/97
To: John-Mark Gurney <gurney_j@resnet.uoregon.edu>
cc: Zach Heilig <zach@gaffaneys.com>, scsi@FreeBSD.ORG
Subject: Re: PCI Advansys controller...
In-reply-to: Your message of "Tue, 16 Sep 1997 01:28:06 PDT."
<19970916012806.54936@hydrogen.nike.efn.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 17 Sep 1997 13:28:26 -0600
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
>currently.. the only version is the one that uses Justin Gibb's CAM
>scsi code that will soon replace the current code.. once that is done,
>then the driver for the cards will be included, (correct me if I remeber
>wrong Justin)...
This is correct.
>> How good of trade would that be (the Advansys cards are about half the price
>> of the Symbios cards, $80 vs. $150). I know the Symbios chip has the script
>s
>> memory, and can offload some of the work from the host CPU, but exactly how
>> much of a win is that?
>
>Justin will have to answer this question.. but I am looking forward to
>the time that FreeBSD does support them, as my supplier has the Advansys
>cards, but doesn't have any of the ncr based cards...
I haven't done any side by side benchmarks between the two cards, but the
architecture that the AdvanSys cards use doesn't strike me as really
high performance.
>--
> John-Mark Gurney Modem/FAX: +1 541 683 6954
> Cu Networking
>
> Live in Peace, destroy Micro$oft, support free software, run FreeBSD
>
--
Justin T. Gibbs
===========================================
FreeBSD: Turning PCs into workstations
===========================================
From owner-freebsd-scsi Wed Sep 17 19:04:06 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id TAA26886
for freebsd-scsi-outgoing; Wed, 17 Sep 1997 19:04:06 -0700 (PDT)
Received: from mail2.uunet.ca (mail2.uunet.ca [142.77.1.15])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26880
for <scsi@freebsd.org>; Wed, 17 Sep 1997 19:04:02 -0700 (PDT)
Received: from why.whine.com ([205.150.249.1]) by mail2.uunet.ca with ESMTP id <123122-23826>; Wed, 17 Sep 1997 22:03:56 -0400
Received: from why (why [205.150.249.1]) by why.whine.com (8.8.5/8.7.3) with SMTP id WAA00325 for <scsi@freebsd.org>; Wed, 17 Sep 1997 22:03:40 -0400 (EDT)
Date: Wed, 17 Sep 1997 22:03:40 -0400
From: Andrew Herdman <andrew@whine.com>
X-Sender: andrew@why
To: scsi@freebsd.org
Subject: CD-R causing system to freeze then reboot
Message-ID: <Pine.BSF.3.96.970917215955.309B-100000@why>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
I just purchased s JVC XR-W2001, hooked it up to my ncr53c810
scsi controller. Everytime I do anything direted at the drive ( a
dd, scsi command, wormcontrol) the computer freezes, and then reboots.
I haven't been able to get a dump as I have no where large enough
at this time to dump the core to.
I haven'theard of anyone else experiencing freezes and reboots with
CD-R's and wonder if anything else might be amiss. The probe of
the CDR is below.
Thanks
Andrew
scbus1 target 4 lun 0: <JVC XR-W2001 2.35> type 4 removable SCSI 2
worm0 at scbus1 target 4 lun 0
worm0: Write-Once
From owner-freebsd-scsi Thu Sep 18 01:46:17 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id BAA19492
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 01:46:17 -0700 (PDT)
Received: from trifork.gu.net (trifork.gu.net [194.93.190.194])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19482
for <scsi@FreeBSD.ORG>; Thu, 18 Sep 1997 01:46:04 -0700 (PDT)
Received: from localhost (localhost.gu.kiev.ua [127.0.0.1])
by trifork.gu.net (8.8.6/8.8.6) with SMTP id LAA09204;
Thu, 18 Sep 1997 11:45:04 +0300 (EEST)
Date: Thu, 18 Sep 1997 11:45:04 +0300 (EEST)
From: Andrew Stesin <stesin@gu.net>
Reply-To: stesin@gu.net
To: "Justin T. Gibbs" <gibbs@plutotech.com>
cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>,
Zach Heilig <zach@gaffaneys.com>, scsi@FreeBSD.ORG
Subject: Re: PCI Advansys controller...
In-Reply-To: <199709171928.NAA11169@pluto.plutotech.com>
Message-ID: <Pine.BSF.3.96.970918114255.9131E-100000@trifork.gu.net>
X-NCC-RegID: ua.gu
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
On Wed, 17 Sep 1997, Justin T. Gibbs wrote:
> I haven't done any side by side benchmarks between the two cards, but the
> architecture that the AdvanSys cards use doesn't strike me as really
> high performance.
Back in 1994 I did have some experience with PCI Advansys
SCSI controllers, under SCO UNIX. They were noticeable
slower than any of NCR 53c810 and Adaptec 2940.
Best regards,
Andrew Stesin
nic-hdl: ST73-RIPE
From owner-freebsd-scsi Thu Sep 18 01:55:15 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id BAA19882
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 01:55:15 -0700 (PDT)
Received: from forwiss.tu-muenchen.de (root@forwiss.tu-muenchen.de [131.159.128.1])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19861;
Thu, 18 Sep 1997 01:55:10 -0700 (PDT)
Received: from pccog4.forwiss.tu-muenchen.de (hafner@pccog4.forwiss.tu-muenchen.de [131.159.128.55]) by forwiss.tu-muenchen.de (8.8.5/V5) with ESMTP id KAA01841; Thu, 18 Sep 1997 10:55:06 +0200 (MET DST)
Received: (hafner@localhost) by pccog4.forwiss.tu-muenchen.de (8.8.5/8.6.12) id IAA03695; Thu, 18 Sep 1997 08:57:34 GMT
Date: Thu, 18 Sep 1997 08:57:34 GMT
Message-Id: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de>
From: Walter Hafner <hafner@forwiss.tu-muenchen.de>
To: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org
Cc: hafner@forwiss.tu-muenchen.de
Subject: Is my NCR controller broken?
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
Hello!
I just want to make sure I don't miss something before changing my
mainboard. Please enlighten me.
I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI
controller). This computer runs for about 3 years now (2.0.5, 2.1.0,
2.1.5)
Since about four weeks I keep getting SCSI resets and then the bus is
dead. No recovery! And it's really strange because the NCR controller
reports totally different errors before hanging. Here are the error
reports from the last three crashes (typed in by hand, so the actual
format may differ):
-------------------------------------------------------------------------------
sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24)
ncr0: timeout ccb=f19fbc00 (skip)
-------------------------------------------------------------------------------
ncr0:1: ERROR (a0:0) (f-28-0) (8/13) @ (260:00000000).
script cmd=fc00001c.
reg: da 10 80 13 47 08 01 1f 00 0f 81 28 80 00 00 00.
ncr0: restart (fatal error).
sd1(ncr0:1:0): command failed (9ff)@f19fbc00.
nrc0: timeout ccb=f19fbc00 (skip)
-------------------------------------------------------------------------------
ncr0: SCSI phase error fixup: CCB already dequeued (0xf19fbc00)
nrc0: timeout ccb=f19fbc00 (skip)
-------------------------------------------------------------------------------
I changed everything:
* disconnected everything except the system drive -> still errors
* changed cables (three different ones) -> still errors
* changed termination (two different external ones, internal, different
termpower sttings etc.) -> still errors
* turned all devices to 5MB synchr. and finally to acync via
'ncrcontrol' -> still errors
* finally replaced the system drive (old DEC 5200 against new IBM DAHC
34330) and put 2.2.1 on it -> still errors. Actually, the errors above
are from that setup.
The only thing I didn't change was the mainboard.
I'd be glad if anyone can confirm my suspicion that the NCR controller
has gone nuts. I just can't imagine why ...
I'd also appreciate it very much if someone with more insight than
myself could explain the error reports to me. I'd especially like to
know what this 'f19fbc00' means: it shows up in all three errors (what's
a 'ccb' anyway?)
Thanks in advance!
-Walter
From owner-freebsd-scsi Thu Sep 18 06:25:49 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id GAA05379
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 06:25:49 -0700 (PDT)
Received: from destiny.erols.com (root@destiny.erols.com [207.96.73.65])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA05354;
Thu, 18 Sep 1997 06:25:38 -0700 (PDT)
Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.8.7/8.6.12) with SMTP id JAA01136; Thu, 18 Sep 1997 09:25:01 -0400 (EDT)
Date: Thu, 18 Sep 1997 09:25:00 -0400 (EDT)
From: John Dowdal <jdowdal@destiny.erols.com>
To: Walter Hafner <hafner@forwiss.tu-muenchen.de>
cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG
Subject: Re: Is my NCR controller broken?
In-Reply-To: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de>
Message-ID: <Pine.BSF.3.95q.970918090954.1078A-100000@destiny.erols.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
I just dealt with solving the same problem. In fact there were were
several problems.
1) DEC DSP5400S drive dies with a physical media failure
2) Attempt to low level the drive; it fails and the drive powers down [ie
it is dead, Jim]
3) remove the drive from /etc/fstab and run for two weeks with same
physical setup, waiting for replacement.
4) Remove dead drive [internal] and add new drive [external] with correct
termination. Haul dead drive to school, to try using the Solaris
format comand on it. Attempt to remote log into my machine, its dead.
5) Go back home, and messages like you describe. The old good drive
powering up and powering down. Turns out the Y connector is dead.
Remove it. Sigh of releif; not two dead disks in two weeks.
6) Format the DSP5400S. It powers down on the sun too. The grown
defect list is approx 1000; the primary is approx 200. Seems quite
dead...
7) Return home, reconnect the rest of my external chain. Starts to boot,
and dies with error messsages you describe during fsck. *Grumble*
8) Dissect each external case, try all combinations one at a time, turns
out that if I include the CD writer I get the above errors while
fscking. "FunnySCSI" below is the "weird" connector which is on a
SUN-3 shoe box.
[2 internal drives] -> [Computer-HD50] -> [Tape-Centronics] ->
[CDWriter-FunnySCSI] -> [Disk-Centronics]
Next I swapped the tape and disk; same effect
9) Next I bought a Centronics-Centronics cable, to remove the CDWriter
from the chain.
-> this worked fine
10) Broke SCSI spec by terminating the CD writer at the drive, leaving
an illegal stub of cable sticking out of the case [the other FunnySCSI
connector]. Connected this with one funnyscsi->centronics cable ..
-> this seems to work fine
Hopefully this helps somebody with scsi problems :)
John
On Thu, 18 Sep 1997, Walter Hafner wrote:
> Hello!
>
> I just want to make sure I don't miss something before changing my
> mainboard. Please enlighten me.
>
> I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI
> controller). This computer runs for about 3 years now (2.0.5, 2.1.0,
> 2.1.5)
>
> Since about four weeks I keep getting SCSI resets and then the bus is
> dead. No recovery! And it's really strange because the NCR controller
> reports totally different errors before hanging. Here are the error
> reports from the last three crashes (typed in by hand, so the actual
> format may differ):
>
> -------------------------------------------------------------------------------
>
> sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24)
> ncr0: timeout ccb=f19fbc00 (skip)
>
> -------------------------------------------------------------------------------
>
> ncr0:1: ERROR (a0:0) (f-28-0) (8/13) @ (260:00000000).
> script cmd=fc00001c.
> reg: da 10 80 13 47 08 01 1f 00 0f 81 28 80 00 00 00.
> ncr0: restart (fatal error).
> sd1(ncr0:1:0): command failed (9ff)@f19fbc00.
> nrc0: timeout ccb=f19fbc00 (skip)
>
> -------------------------------------------------------------------------------
>
> ncr0: SCSI phase error fixup: CCB already dequeued (0xf19fbc00)
> nrc0: timeout ccb=f19fbc00 (skip)
>
> -------------------------------------------------------------------------------
>
> I changed everything:
>
> * disconnected everything except the system drive -> still errors
> * changed cables (three different ones) -> still errors
> * changed termination (two different external ones, internal, different
> termpower sttings etc.) -> still errors
> * turned all devices to 5MB synchr. and finally to acync via
> 'ncrcontrol' -> still errors
> * finally replaced the system drive (old DEC 5200 against new IBM DAHC
> 34330) and put 2.2.1 on it -> still errors. Actually, the errors above
> are from that setup.
>
> The only thing I didn't change was the mainboard.
>
> I'd be glad if anyone can confirm my suspicion that the NCR controller
> has gone nuts. I just can't imagine why ...
>
> I'd also appreciate it very much if someone with more insight than
> myself could explain the error reports to me. I'd especially like to
> know what this 'f19fbc00' means: it shows up in all three errors (what's
> a 'ccb' anyway?)
>
> Thanks in advance!
>
> -Walter
>
>
From owner-freebsd-scsi Thu Sep 18 06:46:51 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id GAA06551
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 06:46:51 -0700 (PDT)
Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA06542
for <scsi@FreeBSD.ORG>; Thu, 18 Sep 1997 06:46:42 -0700 (PDT)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id HAA00715;
Thu, 18 Sep 1997 07:46:19 -0600 (MDT)
Message-Id: <199709181346.HAA00715@pluto.plutotech.com>
To: stesin@gu.net
cc: "Justin T. Gibbs" <gibbs@plutotech.com>,
John-Mark Gurney <gurney_j@resnet.uoregon.edu>,
Zach Heilig <zach@gaffaneys.com>, scsi@FreeBSD.ORG
Subject: Re: PCI Advansys controller...
In-reply-to: Your message of "Thu, 18 Sep 1997 11:45:04 +0300."
<Pine.BSF.3.96.970918114255.9131E-100000@trifork.gu.net>
Date: Thu, 18 Sep 1997 07:46:11 -0600
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
>On Wed, 17 Sep 1997, Justin T. Gibbs wrote:
>
>> I haven't done any side by side benchmarks between the two cards, but the
>> architecture that the AdvanSys cards use doesn't strike me as really
>> high performance.
>
> Back in 1994 I did have some experience with PCI Advansys
> SCSI controllers, under SCO UNIX. They were noticeable
> slower than any of NCR 53c810 and Adaptec 2940.
>
>Best regards,
>Andrew Stesin
If you had one of the early AdvanSys controllers, the latency timer
is explicitly set to 0 to get around a bug. This, above and beyond
the architecture used to talk to the cards, really kills performance.
It was corrected in Rev C and higher of the non-ultra Asc1200 chips
and is not a problem in the Ultra line.
--
Justin T. Gibbs
===========================================
FreeBSD: Turning PCs into workstations
===========================================
From owner-freebsd-scsi Thu Sep 18 15:59:45 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id PAA15128
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 15:59:45 -0700 (PDT)
Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA15101;
Thu, 18 Sep 1997 15:59:33 -0700 (PDT)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP
id PAA24536; Thu, 18 Sep 1997 15:58:49 -0700 (PDT)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA10561;
Thu, 18 Sep 1997 15:58:48 -0700 (PDT)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA00471;
Thu, 18 Sep 1997 15:58:47 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199709182258.PAA00471@salsa.gv.tsc.tdk.com>
Date: Thu, 18 Sep 1997 15:58:47 -0700
In-Reply-To: John Dowdal <jdowdal@destiny.erols.com>
"Re: Is my NCR controller broken?" (Sep 18, 9:25am)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: John Dowdal <jdowdal@destiny.erols.com>,
Walter Hafner <hafner@forwiss.tu-muenchen.de>
Subject: Re: Is my NCR controller broken?
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
On Sep 18, 9:25am, John Dowdal wrote:
} Subject: Re: Is my NCR controller broken?
} I just dealt with solving the same problem. In fact there were were
} several problems.
}
} 7) Return home, reconnect the rest of my external chain. Starts to boot,
} and dies with error messsages you describe during fsck. *Grumble*
} 8) Dissect each external case, try all combinations one at a time, turns
} out that if I include the CD writer I get the above errors while
} fscking. "FunnySCSI" below is the "weird" connector which is on a
} SUN-3 shoe box.
}
} [2 internal drives] -> [Computer-HD50] -> [Tape-Centronics] ->
} [CDWriter-FunnySCSI] -> [Disk-Centronics]
}
} Next I swapped the tape and disk; same effect
}
} 9) Next I bought a Centronics-Centronics cable, to remove the CDWriter
} from the chain.
} -> this worked fine
}
} 10) Broke SCSI spec by terminating the CD writer at the drive, leaving
} an illegal stub of cable sticking out of the case [the other FunnySCSI
} connector]. Connected this with one funnyscsi->centronics cable ..
} -> this seems to work fine
I seem to recall problems with termpower and Sun 3 vintage equipment
(this stuff predates SCSI 1). I believe the some Sun 3's actually
grounded the termpower pin which tended to melt things if you connected
them to post-standard equipment that supplied termpower. I wonder if
your shoe box or the cables that connect to it don't pass termpower
through. This might result in no power to an external terminator at
the end of your SCSI chain, and it is consistent with the configurations
that worked and didn't work. You should be able to make it work by
putting either the disk or tape back at the end of the chain and
configuring the end device to supply termpower to the bus.
--- Truck
From owner-freebsd-scsi Thu Sep 18 17:19:24 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id RAA20575
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 17:19:24 -0700 (PDT)
Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3])
by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA20530
for <scsi@freebsd.org>; Thu, 18 Sep 1997 17:19:03 -0700 (PDT)
Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C)
id AA08848; Fri, 19 Sep 97 02:11:10 +0100
Date: Fri, 19 Sep 97 02:11:10 +0100
Message-Id: <9709190111.AA08848@cabri.obs-besancon.fr>
From: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
To: andrew@whine.com
Cc: scsi@freebsd.org
In-Reply-To: <Pine.BSF.3.96.970917215955.309B-100000@why> (message from Andrew
Herdman on Wed, 17 Sep 1997 22:03:40 -0400)
Subject: Re: CD-R causing system to freeze then reboot
X-Mailer: Emacs
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
>>>>> Andrew Herdman writes:
> I just purchased s JVC XR-W2001, hooked it up to my ncr53c810
> scsi controller. Everytime I do anything direted at the drive ( a
> dd, scsi command, wormcontrol) the computer freezes, and then reboots.
This is normal :-) the JVC is not a supported drive.
Jean-Marc
_____________________________________________________________________________
Jean-Marc Zucconi Observatoire de Besancon F 25010 Besancon cedex
PGP Key: finger jmz@cabri.obs-besancon.fr
From owner-freebsd-scsi Thu Sep 18 17:30:45 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id RAA21484
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 17:30:45 -0700 (PDT)
Received: from ns.feral.com (mjacob@feral.mauswerks.net [204.152.96.10])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA21476;
Thu, 18 Sep 1997 17:30:42 -0700 (PDT)
Received: (from mjacob@localhost)
by ns.feral.com (8.8.6/8.8.6) id RAA07442;
Thu, 18 Sep 1997 17:25:13 -0700
Date: Thu, 18 Sep 1997 17:25:13 -0700
From: Matthew Jacob <mjacob@feral.com>
Message-Id: <199709190025.RAA07442@ns.feral.com>
To: Don.Lewis@tsc.tdk.com
Subject: Re: Is my NCR controller broken?
Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
>(this stuff predates SCSI 1)
Wrong.
> I believe the some Sun 3's actually
Wrong. It was actually the sun 4/110.
I'd also like to point out that neither SCSI-1 nor SASI before
it specified cable pinouts- just pin numbers.
From owner-freebsd-scsi Thu Sep 18 18:25:58 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id SAA25286
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 18:25:58 -0700 (PDT)
Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25276;
Thu, 18 Sep 1997 18:25:54 -0700 (PDT)
Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191])
by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP
id SAA26662; Thu, 18 Sep 1997 18:25:51 -0700 (PDT)
Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194])
by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id SAA12896;
Thu, 18 Sep 1997 18:25:50 -0700 (PDT)
Received: (from gdonl@localhost)
by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id SAA00739;
Thu, 18 Sep 1997 18:25:49 -0700 (PDT)
From: Don Lewis <Don.Lewis@tsc.tdk.com>
Message-Id: <199709190125.SAA00739@salsa.gv.tsc.tdk.com>
Date: Thu, 18 Sep 1997 18:25:48 -0700
In-Reply-To: Matthew Jacob <mjacob@feral.com>
"Re: Is my NCR controller broken?" (Sep 18, 5:25pm)
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: Matthew Jacob <mjacob@feral.com>, Don.Lewis@tsc.tdk.com
Subject: Warning! Sun archaeology [was Re: Is my NCR controller broken?]
Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
On Sep 18, 5:25pm, Matthew Jacob wrote:
} Subject: Re: Is my NCR controller broken?
} >(this stuff predates SCSI 1)
}
} Wrong.
I may have misremembered on this point.
} > I believe the some Sun 3's actually
}
} Wrong. It was actually the sun 4/110.
Looks like we're both right. I was unaware that the 4/110 was
similarly afflicted. From my sun-managers archives:
First, I was reminded about something which, while not directly impacting
my situation, is well worth repeating. This is the infamous design
decision(?) by Sun to ground the "termination power" SCSI pin on the 3/60
and 4/110 models, which means that a straight-through cable from either of
these models to a SCSI drive with termination power supplied tends to blow
the drive up! So while it's safe to plug an ex sun-3 drive onto a new
system, plugging a new drive onto a 3/60 is potentially a problem! It's ok
if you disable "termination power" on the drive, or cut the appropriate pin
of the SCSI cable.
Also
>> 1) most Sun-2/Sun-3 SCSI cards don't supply termination power to the
>> TRMPWR line on the SCSI bus. Only very late engineering rev
>> cards supply power (if your's does it will have a fuse on
>> the card). Make sure that your disk is supplying termination
>> power (most disks have a jumper to enable/disable this).
and from comp.periphs.scsi:
The SparcStation 1 and 1+, Sun3/50 and 3/60, all do not supply
term power. And, I think I recall that some 3/60s even have
their TERMPWR pin (pin 26) wired to ground. This can cause
serious smoke if you connect a device that sources term power;
The 386i seems to be the only Sun (non-VME) that sources term power,
as this was required to power the external terminator plug that
was supplied with that machine.
and from comp.periphs:
Some time ago, there was much discussion of how Sun screwed up the SCSI
interface on their 3/60s -- pin 26, which is supposed to supply +5
volts for termination power was grounded. This meant that any other
device which chose to supply +5 on that line was likely to melt-down
its power supply, or worse, its firmware. Since, up till now, I have
always connected to Sun shoeboxes, I have not been concerned with this
problem.
However, now that I am connecting to another vendor's shoebox, I must
take precautions. As a simple, if ugly, fix, I just cut wire 26 of the
ribbon cable at the Sun end, causing line to float. (Actually, I made
a short piece of cable with line 26 cut which I can insert between the
sun and the cable to the disk drives). Strangely, when I tested for
continuity between pin 26 and ground on the 3/60, there was none.
Still, better to be safe...
} I'd also like to point out that neither SCSI-1 nor SASI before
} it specified cable pinouts- just pin numbers.
}
}-- End of excerpt from Matthew Jacob
--- Truck
From owner-freebsd-scsi Thu Sep 18 18:29:00 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id SAA25613
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 18:29:00 -0700 (PDT)
Received: from ns.feral.com (mjacob@feral.mauswerks.net [204.152.96.10])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25598;
Thu, 18 Sep 1997 18:28:56 -0700 (PDT)
Received: (from mjacob@localhost)
by ns.feral.com (8.8.6/8.8.6) id SAA07539;
Thu, 18 Sep 1997 18:23:29 -0700
Date: Thu, 18 Sep 1997 18:23:29 -0700
From: Matthew Jacob <mjacob@feral.com>
Message-Id: <199709190123.SAA07539@ns.feral.com>
To: Don.Lewis@tsc.tdk.com, mjacob@feral.com
Subject: Re: Warning! Sun archaeology [was Re: Is my NCR controller broken?]
Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
>Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG
>
>On Sep 18, 5:25pm, Matthew Jacob wrote:
>} Subject: Re: Is my NCR controller broken?
>} >(this stuff predates SCSI 1)
>}
>} Wrong.
>
>I may have misremembered on this point.
Ooh, I should have been nicer... sorry...
>
>} > I believe the some Sun 3's actually
>}
>} Wrong. It was actually the sun 4/110.
>
>Looks like we're both right. I was unaware that the 4/110 was
>similarly afflicted. From my sun-managers archives:
>..
Oops- yer right, the 3/60 putzed it too.
> >> 1) most Sun-2/Sun-3 SCSI cards don't supply termination power to the
> >> TRMPWR line on the SCSI bus. Only very late engineering rev
That's also true.
From owner-freebsd-scsi Thu Sep 18 18:47:18 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id SAA27632
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 18:47:18 -0700 (PDT)
Received: from cicerone.uunet.ca (root@cicerone.uunet.ca [142.77.1.11])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA27627
for <scsi@freebsd.org>; Thu, 18 Sep 1997 18:47:15 -0700 (PDT)
Received: from why.whine.com ([205.150.249.1]) by cicerone.uunet.ca with ESMTP id <115753-10828>; Thu, 18 Sep 1997 21:47:08 -0400
Received: from why (why [205.150.249.1]) by why.whine.com (8.8.5/8.7.3) with SMTP id VAA01730; Thu, 18 Sep 1997 21:46:55 -0400 (EDT)
Date: Thu, 18 Sep 1997 21:46:54 -0400
From: Andrew Herdman <andrew@whine.com>
X-Sender: andrew@why
To: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
cc: scsi@freebsd.org
Subject: Re: CD-R causing system to freeze then reboot
In-Reply-To: <9709190111.AA08848@cabri.obs-besancon.fr>
Message-ID: <Pine.BSF.3.96.970918214621.1614A-100000@why>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
On Thu, 18 Sep 1997, Jean-Marc Zucconi wrote:
> >>>>> Andrew Herdman writes:
>
> > I just purchased s JVC XR-W2001, hooked it up to my ncr53c810
> > scsi controller. Everytime I do anything direted at the drive ( a
> > dd, scsi command, wormcontrol) the computer freezes, and then reboots.
>
> This is normal :-) the JVC is not a supported drive.
Hrm... isn't this a little..... harsh?
Thanks for the reply;
Andrew
From owner-freebsd-scsi Thu Sep 18 19:08:06 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id TAA29030
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 19:08:06 -0700 (PDT)
Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA29025
for <scsi@FreeBSD.ORG>; Thu, 18 Sep 1997 19:08:02 -0700 (PDT)
Received: (from grog@localhost)
by freebie.lemis.com (8.8.7/8.8.5) id LAA01849;
Fri, 19 Sep 1997 11:37:52 +0930 (CST)
Message-ID: <19970919113751.44992@lemis.com>
Date: Fri, 19 Sep 1997 11:37:51 +0930
From: Greg Lehey <grog@lemis.com>
To: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
Cc: andrew@whine.com, scsi@FreeBSD.ORG
Subject: Re: CD-R causing system to freeze then reboot
References: <Pine.BSF.3.96.970917215955.309B-100000@why> <9709190111.AA08848@cabri.obs-besancon.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.81e
In-Reply-To: <9709190111.AA08848@cabri.obs-besancon.fr>; from Jean-Marc Zucconi on Fri, Sep 19, 1997 at 02:11:10AM +0100
Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8250
Fax: +61-8-8388-8250
Mobile: +61-41-739-7062
WWW-Home-Page: http://www.lemis.com/~grog
Fight-Spam-Now: http://www.cauce.org
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
On Fri, Sep 19, 1997 at 02:11:10AM +0100, Jean-Marc Zucconi wrote:
>>>>>> Andrew Herdman writes:
>
>> I just purchased s JVC XR-W2001, hooked it up to my ncr53c810
>> scsi controller. Everytime I do anything direted at the drive ( a
>> dd, scsi command, wormcontrol) the computer freezes, and then reboots.
>
> This is normal :-) the JVC is not a supported drive.
I'd still say that's a bug. Unsupported drives shouldn't cause a
reboot.
Greg
From owner-freebsd-scsi Thu Sep 18 21:21:40 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id VAA07576
for freebsd-scsi-outgoing; Thu, 18 Sep 1997 21:21:40 -0700 (PDT)
Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100])
by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA07561
for <scsi@FreeBSD.ORG>; Thu, 18 Sep 1997 21:21:33 -0700 (PDT)
Received: (qmail 22323 invoked by uid 1000); 19 Sep 1997 04:21:56 -0000
Message-ID: <XFMail.970918212155.Shimon@i-Connect.Net>
X-Mailer: XFMail 1.2-alpha-091897 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <9709190111.AA08848@cabri.obs-besancon.fr>
Date: Thu, 18 Sep 1997 21:21:55 -0700 (PDT)
Organization: Atlas Telecom
From: Simon Shapiro <Shimon@i-Connect.Net>
To: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
Subject: Re: CD-R causing system to freeze then reboot
Cc: scsi@FreeBSD.ORG, andrew@whine.com
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
Hi Jean-Marc Zucconi; On 19-Sep-97 you wrote:
> >>>>> Andrew Herdman writes:
>
> > I just purchased s JVC XR-W2001, hooked it up to my ncr53c810
> > scsi controller. Everytime I do anything direted at the drive ( a
> > dd, scsi command, wormcontrol) the computer freezes, and then
> reboots.
>
> This is normal :-) the JVC is not a supported drive.
Try to see if you have LUn (other than zero) scanning enabled. If you do,
knock it OFF. FreeBSD does some initial access commands in backwards order
(I forget which, maybe TEST UNIT READY and INQUIRY), which, on many CD-R
units cause them to try and answer for LUNs other than zero and promptly
hang.
---
Sincerely Yours, (Sent on 18-Sep-97, 21:17:23
by XF-Mail)
Simon Shapiro Atlas Telecom
Senior Architect 14355 SW Allen Blvd., Suite 130 Beaverton OR 97005
Shimon@i-Connect.Net Voice: 503.643.5559, Emergency: 503.799.2313
From owner-freebsd-scsi Fri Sep 19 02:35:49 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id CAA28582
for freebsd-scsi-outgoing; Fri, 19 Sep 1997 02:35:49 -0700 (PDT)
Received: from DonaldBurr.dyn.ml.org (ppp6204.la.inreach.net [199.107.160.204])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA28577
for <scsi@FreeBSD.ORG>; Fri, 19 Sep 1997 02:35:46 -0700 (PDT)
Received: (from dburr@localhost)
by DonaldBurr.dyn.ml.org (8.8.5/8.8.5) id CAA26353
for scsi@FreeBSD.ORG; Fri, 19 Sep 1997 02:37:23 -0700 (PDT)
Message-ID: <XFMail.970919023723.dburr@POBoxes.com>
X-Mailer: XFMail 1.1 [p0] on FreeBSD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <9709190111.AA08848@cabri.obs-besancon.fr>
Date: Fri, 19 Sep 1997 02:35:35 -0700 (PDT)
Organization: Starfleet Command
From: Donald Burr <dburr@POBoxes.com>
To: scsi@FreeBSD.ORG
Subject: Re: CD-R causing system to freeze then reboot
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
-----BEGIN PGP SIGNED MESSAGE-----
My secret spy satellite informs me that on 19-Sep-97, Jean-Marc Zucconi
wrote:
>
>>>>>> Andrew Herdman writes:
>
> > I just purchased s JVC XR-W2001, hooked it up to my ncr53c810
> > scsi controller. Everytime I do anything direted at the drive ( a
> > dd, scsi command, wormcontrol) the computer freezes, and then reboots.
>
>This is normal :-) the JVC is not a supported drive.
Yeah, normal maybe for Lose'95 :) , but it shouldn't be for UNIX -- it
should die in a more robust manner (like maybe saying "worm0: Device not
configured"? and defnitely NOT rebooting the system!)
Donald Burr <dburr@POBoxes.com> - Ask me for my PGP key | PGP: Your
WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to
Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy.
Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNCJH0vjpixuAwagxAQHrQQP+Oc5p8AAOAuoo/DjcE6kamAIMzxdm6dX4
YehpbApmNTgv+e3GYKRyxlCuyoJprFIFqrFu8EcJdXoaKwGYO28Rhix41PfE6ciN
mM6meO5zwCUg+Cz4ZeCXLVzNGkFnJFluXm1i+Cozheiojc97ZAlalutPwc4e6wLz
Q3rL9ImkZEM=
=8Td3
-----END PGP SIGNATURE-----
From owner-freebsd-scsi Fri Sep 19 06:32:08 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id GAA11918
for freebsd-scsi-outgoing; Fri, 19 Sep 1997 06:32:08 -0700 (PDT)
Received: from mail1.kcnet.com (mail1.kcnet.com [206.102.152.3])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA11907
for <freebsd-scsi@freebsd.org>; Fri, 19 Sep 1997 06:32:04 -0700 (PDT)
Received: from enh5x33.kcnet.com (enh5x33.kcnet.com [206.102.153.33])
by mail1.kcnet.com (8.8.7/8.8.5) with SMTP id IAA12905
for <freebsd-scsi@freebsd.org>; Fri, 19 Sep 1997 08:31:51 -0500
Received: by enh5x33.kcnet.com with Microsoft Mail
id <01BCC4D6.77625630@enh5x33.kcnet.com>; Fri, 19 Sep 1997 08:31:46 -0500
Message-ID: <01BCC4D6.77625630@enh5x33.kcnet.com>
From: Christopher S Johnson <chrisj@kcnet.com>
To: "'freebsd-scsi@freebsd.org'" <freebsd-scsi@freebsd.org>
Subject: Zip drives
Date: Fri, 19 Sep 1997 08:31:42 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id GAA11908
Sender: owner-freebsd-scsi@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk
I am new to the wold of FreeBSD, but somewhat familiar with Linux and Unix. The problem I am running in to is getting my zip drive to mount. When my system boots up and probes for devices, the zip drive is assigned sd1. Once I log in, based on what I do in Linux, if I try to mount the drive using the command mount /dev/sd1 /zip it returns an error.
Can you tell me what I am doing wrong or what I can do to resolve the problem?
Thank you
Chris
From owner-freebsd-scsi Fri Sep 19 07:19:12 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id HAA14663
for freebsd-scsi-outgoing; Fri, 19 Sep 1997 07:19:12 -0700 (PDT)
Received: from runningman.rs.itd.umich.edu (0@runningman.rs.itd.umich.edu [141.211.144.15])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14644;
Fri, 19 Sep 1997 07:19:07 -0700 (PDT)
Received: from HG-BASIC1MAIL.HG.MED.UMICH.EDU by runningman.rs.itd.umich.edu (8.8.5/2.3)
with ESMTP id KAA21718; Fri, 19 Sep 1997 10:19:06 -0400 (EDT)
Received: from HG-BASIC1/SpoolDir by HG-BASIC1MAIL.HG.MED.UMICH.EDU (Mercury 1.31);
19 Sep 97 10:19:05 -0500
Received: from SpoolDir by HG-BASIC1 (Mercury 1.31); 19 Sep 97 10:18:51 -0500
Received: from biped by HG-BASIC1MAIL.HG.MED.UMICH.EDU (Mercury 1.31) with ESMTP;
19 Sep 97 10:18:50 -0500
Message-ID: <342289CA.99C025E9@umich.edu>
Date: Fri, 19 Sep 1997 10:18:50 -0400
From: Sasha Kacanski <kacanski@umich.edu>
X-Mailer: Mozilla 4.01 [en] (WinNT; I)
MIME-Version: 1.0
To: "freebsd-scsi@FreeBSD.ORG" <freebsd-scsi@FreeBSD.ORG>,
"hardware@FreeBSD.ORG" <hardware@FreeBSD.ORG>
Subject: password protected site
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
Hi,
Have a Q:
if I have a BSD machine running internet server and SUN running a
intranet, how should I go about implementing user/password access to the
intranet via BSD.
Apache web server is running on the BSD side.
What type of password encryption does Netscape client supports. I can't
go with the clear text. Any suggestions!
thanks
/s
From owner-freebsd-scsi Fri Sep 19 11:58:33 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id LAA01046
for freebsd-scsi-outgoing; Fri, 19 Sep 1997 11:58:33 -0700 (PDT)
Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20])
by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA01039;
Fri, 19 Sep 1997 11:58:26 -0700 (PDT)
Received: by iafnl.es.iaf.nl with UUCP id AA07459
(5.67b/IDA-1.5); Fri, 19 Sep 1997 20:59:38 +0200
Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id UAA03014; Fri, 19 Sep 1997 20:45:49 +0200 (MET DST)
From: Wilko Bulte <wilko@yedi.iaf.nl>
Message-Id: <199709191845.UAA03014@yedi.iaf.nl>
Subject: Re: Warning! Sun archaeology [was Re: Is my NCR controller broken?]
To: Don.Lewis@tsc.tdk.com (Don Lewis)
Date: Fri, 19 Sep 1997 20:45:49 +0200 (MET DST)
Cc: mjacob@feral.com, Don.Lewis@tsc.tdk.com, freebsd-hardware@FreeBSD.ORG,
freebsd-scsi@FreeBSD.ORG
In-Reply-To: <199709190125.SAA00739@salsa.gv.tsc.tdk.com> from "Don Lewis" at Sep 18, 97 06:25:48 pm
X-Organisation: Private FreeBSD site - Arnhem, The Netherlands
X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org'
X-Mailer: ELM [version 2.4 PL24 ME8a]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
As Don Lewis wrote...
>
> On Sep 18, 5:25pm, Matthew Jacob wrote:
> } Subject: Re: Is my NCR controller broken?
> } >(this stuff predates SCSI 1)
> }
> } Wrong.
>
> I may have misremembered on this point.
>
> } > I believe the some Sun 3's actually
> }
> } Wrong. It was actually the sun 4/110.
>
> Looks like we're both right. I was unaware that the 4/110 was
> similarly afflicted. From my sun-managers archives:
>
> First, I was reminded about something which, while not directly impacting
> my situation, is well worth repeating. This is the infamous design
> decision(?) by Sun to ground the "termination power" SCSI pin on the 3/60
> and 4/110 models, which means that a straight-through cable from either of
> these models to a SCSI drive with termination power supplied tends to blow
> the drive up! So while it's safe to plug an ex sun-3 drive onto a new
> system, plugging a new drive onto a 3/60 is potentially a problem! It's ok
> if you disable "termination power" on the drive, or cut the appropriate pin
> of the SCSI cable.
The Sun thing is definitely a hardware bug. But drives should not die a
smoking death 'cause the TERMPOWER line should always be current-limited
(fused) of 1.5 amps per the ANSI SCSI standard. In addition a low-drop
(Schottky) diode is normally used to avoid powering switched-off devices
thru the SCSI bus.
Wilko
_ ____________________________________________________________________
| / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko
|/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try'
----------------------------------------------------------------------Yoda
From owner-freebsd-scsi Fri Sep 19 15:24:08 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id PAA13645
for freebsd-scsi-outgoing; Fri, 19 Sep 1997 15:24:08 -0700 (PDT)
Received: from gaia.coppe.ufrj.br (jonny@cisigw.coppe.ufrj.br [146.164.5.200])
by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA13639
for <freebsd-scsi@FreeBSD.ORG>; Fri, 19 Sep 1997 15:24:04 -0700 (PDT)
Received: (from jonny@localhost)
by gaia.coppe.ufrj.br (8.8.7/8.8.7) id TAA17246;
Fri, 19 Sep 1997 19:23:50 -0300 (EST)
From: Joao Carlos Mendes Luis <jonny@coppe.ufrj.br>
Message-Id: <199709192223.TAA17246@gaia.coppe.ufrj.br>
Subject: Re: Zip drives
In-Reply-To: <01BCC4D6.77625630@enh5x33.kcnet.com> from Christopher S Johnson at "Sep 19, 97 08:31:42 am"
To: chrisj@kcnet.com (Christopher S Johnson)
Date: Fri, 19 Sep 1997 19:23:50 -0300 (EST)
Cc: freebsd-scsi@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
#define quoting(Christopher S Johnson)
// I am new to the wold of FreeBSD, but somewhat familiar with Linux and Unix. The problem I am running in to is getting my zip drive to mount. When my system boots up and probes for devices, the zip drive is assigned sd1. Once I log in, based on what I do in Linux, if I try to mount the drive using the command mount /dev/sd1 /zip it returns an error.
FreeBSD use specific devices for each partition.
If it's a DOS disk, try this:
mount -t msdos /dev/sd1s4 /zip
Jonny
--
Joao Carlos Mendes Luis jonny@gta.ufrj.br
+55 21 290-4698 jonny@coppe.ufrj.br
Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI
PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67
From owner-freebsd-scsi Fri Sep 19 17:14:49 1997
Return-Path: <owner-freebsd-scsi>
Received: (from root@localhost)
by hub.freebsd.org (8.8.7/8.8.7) id RAA20285
for freebsd-scsi-outgoing; Fri, 19 Sep 1997 17:14:49 -0700 (PDT)
Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130])
by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA20278
for <freebsd-scsi@FreeBSD.ORG>; Fri, 19 Sep 1997 17:14:42 -0700 (PDT)
From: sthaug@nethelp.no
Received: (qmail 28192 invoked by uid 1001); 20 Sep 1997 00:14:06 +0000 (GMT)
To: hafner@forwiss.tu-muenchen.de
Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG
Subject: Re: Is my NCR controller broken?
In-Reply-To: Your message of "Thu, 18 Sep 1997 08:57:34 GMT"
References: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de>
X-Mailer: Mew version 1.05+ on Emacs 19.28.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Sat, 20 Sep 1997 02:14:06 +0200
Message-ID: <28190.874714446@verdi.nethelp.no>
Sender: owner-freebsd-scsi@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk
> I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI
> controller). This computer runs for about 3 years now (2.0.5, 2.1.0,
> 2.1.5)
>
> Since about four weeks I keep getting SCSI resets and then the bus is
> dead. No recovery! And it's really strange because the NCR controller
> reports totally different errors before hanging. Here are the error
> reports from the last three crashes (typed in by hand, so the actual
> format may differ):
>
> -------------------------------------------------------------------------------
>
> sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24)
> ncr0: timeout ccb=f19fbc00 (skip)
I have a PVI486-SP3 with AMD 5x86-133 processor and ASUS PCI-SC200 SCSI
controller. It works very well for me. I had *one* problem initially,
which may be relevant: Some versions of the PVI486-SP3 motherboard (I
have version 1.22) have an "IDE prefetch buffer". This *must be* turned
off if you use PCI bus master cards (such as a 53c810 card). This is
explicitly mentioned in my PVI486-SP3 manual at page 3-15.
Before I turned off the "IDE prefetch buffer" in the BIOS, I got errors
similar to yours.
Steinar Haug, Nethelp consulting, sthaug@nethelp.no