From owner-freebsd-questions  Fri Aug 11 14:33:19 1995
Return-Path: questions-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA12253
          for questions-outgoing; Fri, 11 Aug 1995 14:33:19 -0700
Received: from localhost (localhost [127.0.0.1])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with SMTP id OAA12229
          ; Fri, 11 Aug 1995 14:33:16 -0700
Message-Id: <199508112133.OAA12229@freefall.FreeBSD.org>
X-Authentication-Warning: freefall.FreeBSD.org: Host localhost didn't use HELO protocol
To: Matt Rosenberg <mar7@cec.wustl.edu>
cc: questions@freebsd.org
Subject: Re: Adaptec 2742W 
In-reply-to: Your message of "Fri, 11 Aug 95 15:25:17 CDT."
             <9508112026.AA04280@cec.wustl.edu> 
Date: Fri, 11 Aug 1995 14:33:15 -0700
From: "Justin T. Gibbs" <gibbs@freefall.FreeBSD.org>
Sender: questions-owner@freebsd.org
Precedence: bulk

>Earlier this week I had asked about my Seagate 43401N drive 
>which wasn't being read correctly.  I had several dozen people 
>mail me telling me to fix the partition table, and I tried to 
>tell as many as I could that BSD wasn't even getting as far as 
>reading the partition table, and the disklabeling program 
>wouldn't even let me access the disk to make any changes.  Even 
>turning off extended translation in the adaptor setup didn't 
>work.  After screwing around for a few days I found the 
>solution:
>TURN OFF THE "INITIATE WIDE NEGOTIATION" BIT IN THE ADAPTOR 
>SETUP!  That worked.

Is it a wide drive?  If it is, I'd like to know so I can see 
if I can correct the problem in the driver.

>Now I have another problem.  I recompiled a kernel to add a 
>second adhc device for my other Adaptec 2742, and took out all 
>of the superfluous device lines in the kernel configuration.  
>It compiled correctly, but hung right after finishing loading 
>the kernel and probing devices (but it did probe the second 
>adaptor correctly).  I started over from GENERIC and this time 
>the only change I made was adding the second adhc device.  Same 
>problem.  I made the device line exactly identical to the first 
>device line except for changing adhc1 to adhc2.  I am not 
>loading the BIOS from the second adaptor and I changed the IRQ 
>on the second one to 12 (the first IRQ is 11) because when they 
>were both set to 11 (Adaptec says to keep them the same) BSD 
>refused to probe the second bus.  Any suggestions?

We don't allow sharing of EISA irqs yet, so they must be different.

Hmmm.  I don't have any suggestions of the top of my head.  I've run
multiple aic7xxx based controllers in machines before (my home machine
has two of them) and I've not seen this type of problem.  Its sounds
almost like an IRQ conflict.

>=============================================
>Matt Rosenberg
>Washington University School of Law
>St. Louis, MO, USA
>
>mar7@cec.wustl.edu ; rosenbem@wulaw.wustl.edu
>http://www.cec.wustl.edu/~mar7/
>=============================================
>
>
>

--
Justin T. Gibbs
===========================================
  Software Developer - Walnut Creek CDROM
  FreeBSD: Turning PCs into workstations
===========================================