From owner-freebsd-scsi Sat Jan 23 14:49:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27402 for freebsd-scsi-outgoing; Sat, 23 Jan 1999 14:49:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27396 for ; Sat, 23 Jan 1999 14:49:13 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id PAA04680; Sat, 23 Jan 1999 15:48:48 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901232248.PAA04680@panzer.plutotech.com> Subject: Re: Adaptec 2920? In-Reply-To: <36A69F98.DEF7B827@vee.net> from Michael Gratton at "Jan 21, 99 01:31:36 pm" To: mike@vee.net (Michael Gratton) Date: Sat, 23 Jan 1999 15:48:48 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Gratton wrote... > Kenneth D. Merry wrote: > > > > Michael Gratton wrote... > > > Booting hangs after the "Waiting for SCSI devices to settle.." message. > > > The probe complains about somthing, but I lost the bit of paper the > > > messages were scribbled on (darn darn darn!). > > > > Well, I've got a few questions: > > > > - It sounds like you must be booting off an IDE disk. Can you boot > > without the DAT drive attached, or without the SCSI controller in the > > machine? > > The machine does only have a single IDE drive. The same problem occcurs when > the DAT is disconnected, and it boots just fine without the adapter > installed. > > If I left it long enough, with the driver give up and allow the machine to > boot normally? At least then I could copy the errors from /var/log/messages This sounds like an interrupt conflict of some sort, although I'm not sure why it would be happening with a PCI card. If you leave it long enough, it's certainly possible that it will allow the machine to boot normally. Another alternative is putting a serial console on the machine. That would allow you to capture boot messages, kernel printfs, etc. If the machine won't come up after you leave it for a while, I would suggest putting a serial console on it, so we can figure out what's going on. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message