[2564] in linux-scsi channel archive
Re: scsi-problems
daemon@ATHENA.MIT.EDU (Jeff Noxon)
Tue Sep 30 15:20:02 1997
Date: Tue, 30 Sep 1997 14:16:11 -0500
From: Jeff Noxon <jeff@planetfall.com>
To: Kimmo Laine <kl2398@turkuamk.fi>
Cc: Jeff Noxon <jeff@planetfall.com>, linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.A32.3.93.970930210031.37458A-100000@bessel.tekniikka.turkuamk.fi>; from Kimmo Laine on Tue, Sep 30, 1997 at 09:22:33PM +0200
On Tue, Sep 30, 1997 at 09:22:33PM +0200, Kimmo Laine wrote:
>
> Sorry about that but I try again ...
>
> Problem 1. I have compiled kernel 2.0.30-3 many times with different
> options. The last one and the best as far I know was compiled in this way:
>
> I have included all these options ... and those are not modules:
>
> SCSI support , SCSI tape support , Probe all LUNs on each SCSI device
> Verbose SCSI error reporting
>
> and under SCSI low level drivers :
>
> Adaptec 152X/2825 support ( and I have added that -DSKIP_BIOSTEST in
> Makefile like somebody said in SCSI-howto )
>
> after I boot with this kernel it founds that scsi-adapter and then it
> tries to find something else. It prints a lot of different number lines,
> some of them are EIP:0019c0921 or something like that.
> Those other lines are [121jkls,345434,5656098 and so on.
> last line is begins with AIEE and then it totally hangs.
>
> Now any help ?
Find the I/O port, IRQ, and DMA (if applicable) for your card. (Is this a
Plug 'n Play card?) Then use kernel command-line parameters to force the
SCSI adapter at this address.
It might be easiest to compile the driver as a module first. This will
avoid probing altogether. Once you know what parameters you need, you can
try compiling it into the kernel again.
Finally, it might be worth visually inspecting the card. What are the
numbers on the Adaptec I/O chip? Is it really an AIC-6260 or AIC-6360?
I've never seen a card like yours before.
Jeff
