From owner-freebsd-questions Wed Jul 23 04:55:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12298 for questions-outgoing; Wed, 23 Jul 1997 04:55:07 -0700 (PDT) Received: from medusa.cs.uoi.gr (medusa.cs.uoi.gr [193.92.5.160]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA12285 for ; Wed, 23 Jul 1997 04:54:52 -0700 (PDT) Received: (from stratos@localhost) by medusa.cs.uoi.gr (8.8.5/8.8.5) id OAA15386; Wed, 23 Jul 1997 14:54:09 +0300 (EEST) From: Stratos Paschos Message-Id: <199707231154.OAA15386@medusa.cs.uoi.gr> Subject: Re: troubles with SCSI controller adaptec 2940AU In-Reply-To: from Marco Molteni at "Jul 22, 97 10:08:16 pm" To: molter@logic.it (Marco Molteni) Date: Wed, 23 Jul 1997 14:54:09 +0300 (EEST) Cc: freebsd-questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Howdy! > > I got a 2.2.2-RELEASE box with a Adaptec 2940AU PCI SCSI controller, > connected to a Quantum Fireball HD. > I'm using kernel.GENERIC, and a TYAN motherboard (more specs if needed, > since I haven't the machine here now). > If I do a cold boot (I mean with the power switch) the BIOS sees the adaptec > and I can boot from the hd (I installed FreeBSD on it :-), > but if I do a warm boot (eg with "reboot") the bios doesn't sees the > controller and I can't boot. > > Here is what I get from the bios during the boot: > > adaptec AHA-2940AU BIOS v1.21 > Press CTRL-A for SCSI Select utility! > [so it seems that the m/b bios sees the controller, but after about 15 > secs I get:] > time-out failure during SCSI inquiry command > No SCSI boot device found > SCSI BIOS not installed > DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER > :-( > > I *hope* ;-) I just have to compile a custom kernel... > > TIA > > Marco Molteni > Computer Science student at the Universita' di Milano, Italy. > "The time has come", the Walrus said, "to talk of many things". > I had the same problem with the _same_ controller and the _same_ Adaptec BIOS version. Someone from a local store told me that this BIOS has some problems with some motherboards. I solved the problem by replacing the Adaptec BIOS by a newer (ver 1.40 I think). ----- Stratos Paschos