From owner-freebsd-hackers  Mon Mar 17 18:50:38 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA25674
          for hackers-outgoing; Mon, 17 Mar 1997 18:50:38 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA25668
          for <freebsd-hackers@freebsd.org>; Mon, 17 Mar 1997 18:50:36 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA03560; Mon, 17 Mar 1997 21:50:03 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 17 Mar 1997 21:50 EST
Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id UAA00887; Mon, 17 Mar 1997 20:42:56 -0500 (EST)
Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id UAA00374; Mon, 17 Mar 1997 20:48:15 -0500 (EST)
Date: Mon, 17 Mar 1997 20:48:15 -0500 (EST)
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199703180148.UAA00374@lakes.water.net>
To: ponds!freebsd.org!freebsd-hackers, ponds!crh.cl.msu.edu!henrich
Subject: Re: aha2940 problems in 2.1-STABLE (any by inference, possible 2.2-RELE
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


See below..


> 
> > > The 2.1.6.1 kernel reponds with (from dmesg):
> > 
> > >  ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 15 on pci0:17
> > >  ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs
> > >  ahc0 waiting for scsi devices to settle
> > >  (ahc0:0:0): "HP C3323-300 4242" type 0 fixed SCSI 2
> > >  sd0(ahc0:0:0): Direct-Access 1003MB (2056008 512 byte sectors)
> > >  ahc0:A:1: refuses WIDE negotiation.  Using 8bit transfers
> > 
> > The quick and dirty solution is to go into your adaptec controller setup and
> > turn off wide negotiation on your narrow devices (I've had this same problem
> > for some time now)
> 
>  Ummmm  - am I mistaken; or perhaps I haven't communicated well.
> 
>  You see, at 2.1.6.1 the aha2940 driver works - it recognizes
> the drive isn't WIDE and does the right thing.
> 
>  At 2.1-STABLE (post 2.1.7) the aha2940 driver doesn't work.
> 
>  Now, if I understand you correctly, disabling WIDE negotiation for this 
> device in the CNTRL-A setup for the aha2940 will cause 2.1.7 to become
> functional?   
> 
>  I'll give it a try this evening.
> 
> 	- Thanks -
> 	- Dave R. -
> 

 Ok - that's it exactly...  When I disable the WIDE negotiation
in the BIOS setup; 2.1-STABLE is able to find my old micropolis
drive and seems pretty happy with it.

 Thanks for the tip!

 The question now becomes - why was 2.1.6.1 able to handle this,
but 2.1-stable unable to do so?

	- Dave Rivers -