From owner-freebsd-scsi Sat Nov 30 18:33:40 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA26717 for freebsd-scsi-outgoing; Sat, 30 Nov 1996 18:33:40 -0800 (PST) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA26712; Sat, 30 Nov 1996 18:33:37 -0800 (PST) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.7.5/8.7.3) with UUCP id TAA03299; Sat, 30 Nov 1996 19:33:37 -0700 (MST) Received: from localhost (marcs@localhost) by alive.ampr.ab.ca (8.7.5/8.7.3) with SMTP id TAA05070; Sat, 30 Nov 1996 19:32:28 -0700 (MST) Date: Sat, 30 Nov 1996 19:32:28 -0700 (MST) From: Marc Slemko X-Sender: marcs@alive.ampr.ab.ca To: hardware@freebsd.org cc: scsi@freebsd.org, Greg Skafte Subject: Re: Tekram 390U and Seagate hawk ST32151N In-Reply-To: <57pc97$hcm@news.itfs.nsk.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [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 That is not exact and doesn't include some of the important stuff for debugging it, but I don't have a copy of the full message right now. 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. On 30 Nov 1996, Nickolay N. Dudorov wrote: > Marc Slemko wrote: > > Anyone have any trouble making a Tekram 390U SCSI controller work with > > certain disks? What we are seeing is that it hangs on probing the disks > > after the SCSI bios is installed, but if you go into the bios setup it can > > probe them, scan them, etc. with no problems. It works fine with tape > > drives and an old 300 meg drive we tried. > > > Tried lowering the SCSI bus speed, disabling things that could cause > > problems, etc. See the same thing when we try it with a different type of > > Seagate. Yes, the bus is properly terminated and we have tried multiple > > cables. > > > No, the question isn't really freebsd specific but there has been some > > discussion of the Tekram here a while back.... > > Last week I also encounter a problem with Tekram DC-390F > controller and CONNER CFP2105S disk (which also has some Seagate > name on it ;). This disk was previously used with NCR 53c810-based > controller AND was Dangerously Dedicated to FreeBSD. Tekram's > BIOS hangs on identifing the disk, but successfully sees it when > in it's setup. I solve my problem by re-fdisking disk to non-DD > mode with old controller. > This is definitely Tekram BIOS bug - if it does'nt like > DD disk it can just skip it and not hung forever ;-). > > P.S. Are there any plans/shedules to support extened features > of 53c875-based controllers in ncr-driver ? > (It'll be very good ULTRA WIDE SCSI controller for ~150$ > here in Siberia) > > N.Dudorov >