From owner-freebsd-current Sun Aug 31 14:35:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19461 for current-outgoing; Sun, 31 Aug 1997 14:35:18 -0700 (PDT) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA19455; Sun, 31 Aug 1997 14:35:12 -0700 (PDT) Received: from x14.mi.uni-koeln.de ([134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA12054 (5.67b/IDA-1.5); Sun, 31 Aug 1997 23:35:10 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.7/8.6.9) id XAA03986; Sun, 31 Aug 1997 23:28:49 +0200 (CEST) X-Face: " Date: Sun, 31 Aug 1997 23:28:49 +0200 From: Stefan Esser To: Glenn Johnson Cc: freebsd-current@FreeBSD.ORG, Stefan Esser Subject: Re: NCR SCSI will not boot References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Glenn Johnson on Thu, Aug 21, 1997 at 01:51:55PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Aug 21, Glenn Johnson wrote: > ncr0: rev 0x11 int a irq 11 on pci0.14.0 > ncr0: minsync=25, maxsync=206, maxoffs=8, 128 dwords burst, large dma fifo Could you please try revision 1.106 of /sys/pci/ncr.c ? I have found and fixed a problem with early revision NCR 53c875 chips, and could verify it with my rev 0x01 53c875. If my understanding of the problem is correct, then the driver should now be able to the on-chip SRAM for SCRIPTS storage ... Regards, STefan