From owner-freebsd-bugs  Mon Apr 29 22:47:49 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id WAA08821
          for bugs-outgoing; Mon, 29 Apr 1996 22:47:49 -0700 (PDT)
Received: from pioneer.arc.nasa.gov (pioneer.arc.nasa.gov [128.102.194.143])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA08816
          for <bugs@FreeBSD.org>; Mon, 29 Apr 1996 22:47:46 -0700 (PDT)
Received: by pioneer.arc.nasa.gov (8.7.1/1.35)
	id WAA27896; Mon, 29 Apr 1996 22:47:43 -0700 (PDT)
Date: Mon, 29 Apr 1996 22:47:43 -0700 (PDT)
From: bridges@pioneer.arc.nasa.gov (Michael D. Bridges)
Message-Id: <199604300547.WAA27896@pioneer.arc.nasa.gov>
To: bugs@FreeBSD.org
Subject: Prob - 2.1 FreeBSD boot floppy "can't see" controller: Adaptec 2940W
Cc: bridges@pioneer.arc.nasa.gov
Sender: owner-bugs@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk


I've previously installed and successfully run FreeBSD with
XFree86 on a 486.  This system preforms beautifully.

So I tried to do the same thing on a Pentium.  I was unsuccessful :^(

The Boot floppy probe process apparently can't find 
my disk controller and/or disk.

This pentium system has an Adaptec 2940W SCSI controller with 
Seagate 32550W 2GB Barrcuda disk on an Intel Endeavor motherboard.
According the 2.1 FreeBSD docs, this controller is supported.

Unfortunately, the boot disk doesn't see the my disk.  
At least the "novice" & "custom" menu items claim that the 
disk is unseen.

Based on the FreeBSD documentation I should have seen "ahc0" come up 
when devices are being probed at boot time.  This didn't happen.  
I tried a couple of reset boots, but still no disk controller.

(Of course if it was at the end of the boot process it might have
 blown by.  The last third of this process blows off the screen and
 into the "install menu".  Wish it would wait a few moments or ask
 if I wish to proceed.  This would help me see what the probe process
 found.)

In any case, I next floppy booted with the "-c" option.
The config "ls" command did not show the expected "ahc0". 

So next I went to visual mode.
Visual mode shows that device "ahc1" should take care of the 
294x family of controllers  --> unlike the docs which refer to "ahc0".

In any case the -c boot didn't help, except to provide
more confusion.

So a three of questions:

1) Is there a way to manually force a couple of probes for 
   the Adaptec 2940W controller during the floppy boot?

2) How can I get a list of devices see by the probe during floppy
   boot?

3) Got an idea what I should try next?


Thanks for the help,

	Mike Bridges