*BSD News Article 63104


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!newsfeed.internetmci.com!news.dacom.co.kr!news.kreonet.re.kr!overload.lbl.gov!eubie.lbl.gov!jin
From: jin@eubie.lbl.gov (Jin Guojun[ITG])
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: SCSI problems on ASUS SC200 (NCR)
Date: 7 Mar 1996 17:30:35 GMT
Organization: Lawrence Berkeley Laboratory
Lines: 36
Message-ID: <4hn6fr$j9p@overload.lbl.gov>
References: <Dno01r.J7u@ritz.mordor.com>
NNTP-Posting-Host: eubie.lbl.gov

In article <Dno01r.J7u@ritz.mordor.com>, David Gifford <giff@mordor.com> wrote:
>System:
>ASUS P/I-P55TP4XE
>ASUS SC200 PCI SCSI (NCR)
>SEAGATE ST32550N 2-Gig SCSI Hard Drive
>ATI Graphics Xpression (Mach 64 DDRAM), PCI
>Texel (now Plextor) DM-3024 SCSI CD-ROM

It looks perfect. I used same configuration with different CD-ROM drives.
I have serveral CD-ROM drives but not one you have.

>I can't get this system to install the Walnut Creek CDROM
>distribution of 2.1.
> ...
>I've tried 4 sets of SCSI cables and gone over termination
>several times.  I am using pretty generic SCSI cables, however.
>
>Is this just a problem with SCSI interference?  Or is there something
>I can look for which might indicate a faulty CD-ROM player?  Why
>doesn't the SCSI bus get reset?

It is not cable problem in most cases. We have tested a 15-foot long
ribbon cable plus another 3-foot long SCSI cable with a 4GB disk and
a 2GB disk or CD-ROM without terminator on many machines and disks.

To isolate the problem, first thing is to make sure you CD-ROM working.
If CD-ROM drive is OK, then make sure the IRQ for NCR is not conflicted
with others. If you got error on NCR irq, it almost 100% makes system
failure.


--
/-------------- Jin Guojun ------------ v ---- Internet: g_jin@lbl.gov ----\
|	Imaging & Distributed Computing | Usenet: ucbvax!g_jin@lbl.gov	   |
|	Lawrence Berkeley Laboratory	| Bitnet:	--		   |
|	50B-2239, Berkeley, CA 94720	-  jin%george.lbl.gov@Csa3.LBL.Gov |