[7776] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Convincing the aic7xxx driver that it's scsi1

daemon@ATHENA.MIT.EDU (ken@seefried.com)
Fri Dec 31 17:10:02 1999

To: linux-scsi@vger.rutgers.edu
From: ken@seefried.com
Date:   Fri, 31 Dec 1999 17:03:42 -0500
Message-ID: <OF5E12B73F.38D9E966-ON05256858.00793069@seefried.com>
MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<P>I've been pounding my head against this for quite a while, and I've draw=
n a blank. &nbsp;I've read every relevant HOWTO I can think of as well as t=
he driver sources. &nbsp;Clearly, I'm missing something.</P><P>I've got a C=
ompaq DeskPro XL 5133 (P200MMX, EISA/PCI thingy). &nbsp;It's got a built-in=
 AM53C974 SCSI chip (actually, the SCSI/ENet combined chip). &nbsp;This con=
trols 2 disks and the CD-ROM. &nbsp;One of the disks is esp. important beca=
use it has the EISA config utils on it, and it needs to be drive 80h (C:, o=
r whatever). &nbsp;Runs Linux like a champ.</P><P>Now...I add an Adaptec AH=
A-2744W (EISA-based wide diff SCSI, recognized by the aic7xxx driver). &nbs=
p;I want this card to be the second controller. &nbsp;The drive connected t=
o this controller is correctly recognized by the Compaq BIOS as disk 82h. &=
nbsp;</P><P>Load linux.</P><P>I cannot for the *life* of me figure out how =
to coerce the damn Adaptec card to be SCSI1, not SCSI0. &nbsp;No matter wha=
t I do, the aic7xxx driver gets loaded before the AMD driver, rendering the=
 machine unbootable (because what should be /dev/sda is now /dev/sdb). &nbs=
p;I've tried every BIOS &amp; EISA setting under the sun. &nbsp;The AMD is =
set in the EISA config to be the first controller. &nbsp;I've put driver di=
rectives on the boot string trying to get the kernel to recognize the AMD c=
hip first without luck. &nbsp;I've moved the SCSI controllers to every IRQ/=
mem combo possible. &nbsp;I've edited the builtin=5Fscsi=5Fhosts array host=
s.c to move the Adaptec detection directive after the AMD and get a kernel =
detects them in the order I want and then promptly that panics (streaming t=
oo much rubbish out for me to transcribe the relevant messages). &nbsp;Even=
 the rescue disk has let me down.</P><P>I assume that this has something to=
 do with the fact that the Compaq XL BIOS32 is in a funky location and the =
kernel isn't getting the clue about which controller should be first.</P><P=
>Anyone have an idea?</P><P>- Ken</P><P></P>=

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post