I've been pounding my head against this for quite a while, and I've drawn a blank. I've read every relevant HOWTO I can think of as well as the driver sources. Clearly, I'm missing something.
I've got a Compaq DeskPro XL 5133 (P200MMX, EISA/PCI thingy). It's got a built-in AM53C974 SCSI chip (actually, the SCSI/ENet combined chip). This controls 2 disks and the CD-ROM. One of the disks is esp. important because it has the EISA config utils on it, and it needs to be drive 80h (C:, or whatever). Runs Linux like a champ.
Now...I add an Adaptec AHA-2744W (EISA-based wide diff SCSI, recognized by the aic7xxx driver). I want this card to be the second controller. The drive connected to this controller is correctly recognized by the Compaq BIOS as disk 82h.
Load linux.
I cannot for the *life* of me figure out how to coerce the damn Adaptec card to be SCSI1, not SCSI0. No matter what 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). I've tried every BIOS & EISA setting under the sun. The AMD is set in the EISA config to be the first controller. I've put driver directives on the boot string trying to get the kernel to recognize the AMD chip first without luck. I've moved the SCSI controllers to every IRQ/mem combo possible. I've edited the builtin_scsi_hosts array hosts.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 too much rubbish out for me to transcribe the relevant messages). Even the rescue disk has let me down.
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.
Anyone have an idea?
- Ken
- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]