From owner-freebsd-questions Sun Mar 10 07:12:10 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA02423 for questions-outgoing; Sun, 10 Mar 1996 07:12:10 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA02413 for ; Sun, 10 Mar 1996 07:12:06 -0800 (PST) Received: by Sisyphos id AA04563 (5.67b/IDA-1.5 for questions@freebsd.org); Sun, 10 Mar 1996 16:11:35 +0100 Message-Id: <199603101511.AA04563@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Sun, 10 Mar 1996 16:11:35 +0100 In-Reply-To: "Rodney W. Grimes" "Re: NCR disk controller, hp disk" (Mar 8, 23:18) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Rodney W. Grimes" Subject: Re: NCR disk controller, hp disk Cc: questions@freebsd.org Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 8, 23:18, "Rodney W. Grimes" wrote: } Subject: Re: NCR disk controller, hp disk } We really need a SCSI expect to go rewrite the firmware for the NCR cards, } what we have today has so many incompatibility problems it is getting hard } to spec systes using it :-(. Rod, this is plain untrue and you ought to know it ... (If you happen to have a secret list of incompatible drives: Well, there's not much I can do. You are among the least cooperative persons I ever met (on the net), when it comes to remote error diagnosis and debug sessions ...) There have been a few problems with tagged commands and buggy drive firmware, and they often could be solved by getting a firmware upgrade from the drive vendor. There are a few remaining incompatibilities with cheap CDROM drives (esp. the Chinon 525 and 535). Rod, you are the one who did wine about this before, since you ARE making money out of my work, by selling systems with the NCR, but were too busy to help diagnose the problem. There is one problem with multiple tagged START STOP UNIT commands being sent to certain IBM drives, and those start unit commands are bogus anyway, and while I could filter them out in the NCR driver, I'm waiting for a patch to the generic SCSI code to remove the situation. I have asked for the -DFAILSAFE for all install kernels just to be able to make the driver work, even though it does not use all performance features in the install process. Those will be available in all custom kernels, though ... 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