Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Dec 1995 12:12:16 +0100
From:      se@zpr.uni-koeln.de (Stefan Esser)
To:        Jeff Bewley <wabbit@ionet.net>
Cc:        questions@freebsd.org
Subject:   Re: Install probs: NCRc810/HP drive?
Message-ID:  <199512211112.AA05140@Sysiphos>
In-Reply-To: Jeff Bewley <wabbit@ionet.net> "Install probs: NCRc810/HP drive?" (Dec 20, 19:20)

next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 20, 19:20, Jeff Bewley wrote:
} Subject: Install probs: NCRc810/HP drive?
} I'm trying to install FreeBSD for the first time, from the
} Walnut Creek 2.1.0 CD.  The bootdisk boots just fine, but whenever
} I go into the "Novice" section, it informs me that it could not
} locate my hard drive (a WD 3275s 2.1 gig SCSI drive, on id0).
} It seems to handle my NCR3c810 controller fine, and recognize the
} HP drive and my Matshita CR-504 (SCSI) CD-ROM drive, located on
} id0 and id1, respectively.
}   As I select "Quit" from the install menu (my only real option),
} I can see error messages as the system reboots. Best as I can
} reassemble (I can't find a way to read them except in the few
} tenths of a second before the system reboots), the messages
} appear to be:
} sd0:ncr0(0:0:0) asc:4e,0 ABORTED COMMAND

Hard to tell what's going on, 
but this is most definitely
not the expected behaviour ...

The asc:... message is written 
by the higher level SCSI code,
so I don't expect this to be 
a NCR driver problem.

} Basic system information: Pentium 100mhz, 32 megs non-EDO RAM,
} NCR3c810 (rev 2) controller, Diamond Stealth Graphics 2001 video
} card, 2.1 gig HP SCSI drive, 4x Matshita CDROM, Zoom internal
} faxmodem (com4), ms-busmouse(com1)

You may want to try without the 
WD hard disk and CDROM, first. 
The NCR driver does negotiate 
fast synchronous transfers and 
uses tagged command queues, if 
the drive claims to support these 
features. This may not be true for 
the other operating systems you 
tried before. 

The performance optimizations can
make a system fail because of bad
cables/terminators or firmware bugs,
though the latter are very rare ...


Please send more information,
and I will try to identify the 
cause of the failure ...

Regards, STefan

-- 
 Stefan Esser, Zentrum fuer Paralleles Rechnen		Tel:	+49 221 4706021
 Universitaet zu Koeln, Weyertal 80, 50931 Koeln	FAX:	+49 221 4705160
 ==============================================================================
 http://www.zpr.uni-koeln.de/~se			  <se@ZPR.Uni-Koeln.DE>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512211112.AA05140>