[890] in linux-scsi channel archive
Re: 1542B problem
daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Thu Nov 7 09:16:18 1996
Date: Tue, 5 Nov 1996 14:39:56 -0800
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: alan@lxorguk.ukuu.org.uk
CC: submit-linux-dev-scsi@ratatosk.yggdrasil.com
In-reply-to: <55lr0d$tj7@lightning.swansea.linux.org.uk>
(alan@lxorguk.ukuu.org.uk)
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
Newsgroups: linux.dev.scsi
In article <327D4A88.726D@mclink.it>,
Roberto Nestico' <r.nestico@mclink.it> wrote:
>During the boot operation the system say:
>aha1542_in failed(3): Unable to determine Adaptec DMA priority.
>Disabling board.
This is normally due to one of two things either having the various jumpers
for DMA channel not matching, or having the buslogic driver in the kernel
too.
>I'm installing 1.2.13 version of Slackware, but the problem still
>persist on RedHat and Debian version too.
Boot with the command buslogic=0x330 (yes its junk, but it will probe for
a buslogic at 0x330 and not 0x334, that will stop it stamping on the
AHA1542B).
I wish people wouldn't ship install kernels with both of these enabled
This is only a problem with the obsolete BusLogic driver in 1.2.13. The new
BusLogic driver will not interfere with Adaptec 154x cards, and it should be
quite safe to have both drivers in the same kernel. In fact, the beta driver
now includes a probe algorithm that's based on the one BusLogic uses in their
own BIOS, and this avoids problems with some other SCSI cards as well.
Leonard
