From owner-freebsd-questions Mon Dec 11 16:42:10 2000 From owner-freebsd-questions@FreeBSD.ORG Mon Dec 11 16:42:08 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id B6DBF37B400 for ; Mon, 11 Dec 2000 16:42:05 -0800 (PST) Received: from backup.af.speednet.com.au (backup.af.speednet.com.au [172.22.2.4]) by backup.af.speednet.com.au (8.11.1/8.11.1) with ESMTP id eBC0fUF78220; Tue, 12 Dec 2000 11:41:33 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Tue, 12 Dec 2000 11:41:30 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Dan Langille Cc: David Kelly , freebsd-questions@FreeBSD.ORG Subject: Re: sym SCSI card problems during settle wait In-Reply-To: <200012060418.RAA11867@ducky.nz.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 6 Dec 2000, Dan Langille wrote: > On 5 Dec 2000, at 22:04, David Kelly wrote: > > > Don't think your problem is termination as it wouldn't hang forever > > unless it was stuck between the CPU and '810. > > Good. Because I've just moved to a SCSI cable with a terminator at the > end of it and it still doesn't boot. > > > I was not aware the sym driver supported the 810, but its man page says > > it does. If you have a running system, try replacing sym with ncr. If > > ncr is in your kernel think you can disable sym with "boot -c". > > This is a fresh install. I'm still trying to get the box to come up after visual > configuration, removing conflicts, etc. > > I've gotten myself to the "config"> prompt and I'm trying to disable sym. > di sym, di sym0, all fail. What have I missed? G'day Dan, Did you get it working yet? They do work - here's mine: sym0: <810> port 0x6000-0x60ff mem 0xf0000000-0xf00000ff irq 11 at device 5.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: PCI DATA PARITY ERROR DETECTED - DISABLING MASTER DATA PARITY CHECKING. ... da2 at sym0 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 2103MB (4308352 512 byte sectors: 255H 63S/T 268C) da1 at sym0 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 1003MB (2055035 512 byte sectors: 64H 32S/T 1003C) da3 at sym0 bus 0 target 2 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da3: 2103MB (4308352 512 byte sectors: 255H 63S/T 268C) I strongly suspect that your problem IS with termination. If your card is anything like mine (I suspect it is), then you'll notice that there is NO termination on the card itself! Therefore, you have to terminate BOTH ends of the SCSI cable (assuming only one drive). Hope this helps... > > -- > Dan Langille > The FreeBSD Diary - http://www.freebsddiary.org/ > NZ ADSL - http://www.unixathome.org/adsl/ > NZ Broadband - http://www.unixathome.org/broadband/ > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message