From owner-freebsd-bugs  Tue Apr 30 07:10:15 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA09484
          for bugs-outgoing; Tue, 30 Apr 1996 07:10:15 -0700 (PDT)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA09478
          Tue, 30 Apr 1996 07:10:11 -0700 (PDT)
Message-Id: <199604301410.HAA09478@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: bridges@pioneer.arc.nasa.gov (Michael D. Bridges)
cc: bugs@FreeBSD.org
Subject: Re: Prob - 2.1 FreeBSD boot floppy "can't see" controller: Adaptec 2940W 
In-reply-to: Your message of "Mon, 29 Apr 1996 22:47:43 PDT."
             <199604300547.WAA27896@pioneer.arc.nasa.gov> 
Date: Tue, 30 Apr 1996 07:10:11 -0700
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
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.

Hmmm.  Strange.

>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.

It is, although you'll probably want to pick up a more recent
version of the ahc driver once you're installed.

...

>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.

Yes, it should be ahc0.

>(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.)

When you get to the install menu, hit "scoll-lock" followed by a few
"page-up"s.  My guess is that the PCI code is having problems with
your motherboard for some reason.  Copy down all the messages you get
from the PCI system and send them to this list.

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

Userconfig only works for ISA devices.  In 2.1, it also worked for most
EISA devices (like the AHA2742/AHA2842 that the ahc1 entry is for) but
now that EISA devices are probed automatically, even ahc1 has gone
away from user config in releases after 2.1.

>3) Got an idea what I should try next?

Try a newer SNAPshot boot floppy.

>Thanks for the help,
>
>	Mike Bridges
>

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================