From owner-freebsd-questions  Mon Feb 10 01:49:46 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA22114
          for questions-outgoing; Mon, 10 Feb 1997 01:49:46 -0800 (PST)
Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA22108
          for <questions@FreeBSD.org>; Mon, 10 Feb 1997 01:49:36 -0800 (PST)
Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.7.5/8.6.12) id LAA12231; Mon, 10 Feb 1997 11:47:42 +0200 (IST)
X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to <nadav@barcode.co.il> using -f
Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3)
	id sma012229; Mon Feb 10 11:47:20 1997
Message-ID: <32FEEE1D.67E1@barcode.co.il>
Date: Mon, 10 Feb 1997 11:45:01 +0200
From: Nadav Eiron <nadav@barcode.co.il>
X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m)
MIME-Version: 1.0
To: Steve Hearn <steveh@cetus.digicon-brs.com.au>
CC: questions@FreeBSD.org, Subject.@janus.cat.csiro.au,
        "install"@cetus.digicon-brs.com.au;
Subject: Re: 
References: <Pine.HPP.3.91.970210182643.404A-100000@cetus.digicon-brs.com.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Steve Hearn wrote:
> 
> I'm having trouble detecting my Adaptec 2940 UW PCI controller.
> I believe the ahc0 is the appropriate device.
> 
> But I can't see that particular device (ahc0) anywhere in the list
> as the machine boots.
> 
> 1. Does anyone know at what point in the 'list' it should be:
>    Should it be towards the end, following 'Probing for devices on PCI
>    bus'?
> 
> 2. Is it possible that that particular device isn't included in the
>    generic kernel, and that I have to build a special kernel?
> 
> Steve Hearn
> Exploration Geophysics Laboratory
> University of Queensland
> Brisbane
> Australia
> 
> Email:  steveh@cetus.digicon-brs.com.au

It should be automaticaly deteced. However, the probe seems to be
effected by other probes. Try booting -c and disable *all* the devices
you don't have (I think aha0 is what causes this specific problem). It
should then be detected. Also check if your card is of the -A variant.
The -A variants are only supported by 2.1.6R and higher. If you use
2.1.5R an -A card will not be recognized.

Nadav