From owner-freebsd-scsi Sun Dec 1 06:39:27 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA16491 for freebsd-scsi-outgoing; Sun, 1 Dec 1996 06:39:27 -0800 (PST) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA16482 for ; Sun, 1 Dec 1996 06:39:16 -0800 (PST) Received: from x14.mi.uni-koeln.de (annexr2-41.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA11733 (5.67b/IDA-1.5 for ); Sun, 1 Dec 1996 15:39:07 +0100 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.3/8.6.9) id PAA02154; Sun, 1 Dec 1996 15:07:59 +0100 (CET) Message-Id: Date: Sun, 1 Dec 1996 15:07:59 +0100 From: se@freebsd.org (Stefan Esser) To: marcs@znep.com (Marc Slemko) Cc: scsi@freebsd.org, skafte@worldgate.com (Greg Skafte) Subject: Re: Tekram 390U and Seagate hawk ST32151N References: <57pc97$hcm@news.itfs.nsk.su> X-Mailer: Mutt 0.52 Mime-Version: 1.0 In-Reply-To: ; from Marc Slemko on Nov 30, 1996 19:32:28 -0700 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Nov 30, marcs@znep.com (Marc Slemko) wrote: > [Sent to hardware and scsi; unless you have a reason, please followup to > only one list. scsi is probably better, since it is dealing with freebsd > drivers now.] > > Nickolay's suggestion worked, so now we can get past the BIOS probing > stage. However, FreeBSD still won't boot. I am using -stable with > the NCR driver (ncr.c and ncrregs.h) from -current dropped in. A 300 meg > drive will work fine, but when it tries to probe the 2 gig hawk we get > something like: > > sd0(ncr0:4:0): COMMAND failed (9 ff) @[address] > sd0 could not get size error ncr0: aborting job > ERROR (90:0) (0-21-15) (0/13) @ (418:43000060) > script cmd = 878b0000 > reg : [deleted] > ncr0: restart failed Please do not use the driver from -current under -stable ! There have been quite some changes, and I'm surprised you got that far ... (552 lines of diffs in ncr.c alone ...) > Booting with a 2.2-ALPHA disk works fine, so either I missed something > from the NCR stuff between stable and current or there was another change > that fixed this. Anyone have any ideas about what it could be? Nothing > stood out in the CVS logs as being obvious. > > If all else fails, we just have to move to 2.2 which won't kill us, but we > would prefer not to for this machine. Please allow a few days to send you patches that add all -current driver features to the NCR driver in -stable. It is too late to integrate them into 2.1.6.1 (AFAIK), but I'll support 2.1.x as long as there is interest by users. Regards, STefan