[2767] in linux-scsi channel archive
Re: Linux does not see AHA-1740
daemon@ATHENA.MIT.EDU (Michael Weller)
Thu Nov 6 17:39:18 1997
Date: Thu, 6 Nov 1997 23:30:15 +0100 (MEZ)
From: Michael Weller <eowmob@exp-math.uni-essen.de>
To: "Martin J. Rowat" <Martin@rugbypl.demon.co.uk>
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <vEqh0AAndOY0Ewsa@rugbypl.demon.co.uk>
On Wed, 5 Nov 1997, Martin J. Rowat wrote:
> I have Tulip tr486dx-2/e-66 computer. This is a 486/DX2 66 MHz EISA
> machine and I am attempting to configure Linux (redhat 4.1/Linux 2.0.30)
> This is an older machine just retired from duty as a Novell server which
> I want to set up as a Linux box. I have had no problems setting up other
> machines (various hardware configurations) with Linux.
>
> Boot from floppy is fine but generic kernel image does not see AHA-1740.
> Autoprobe fails (SCSI Hosts:0 SCSI total:0)
The 174x driver does not use a dos dump, nor do you need (or can) to
specify a base address. This is an EISA device and easy to check for.
You should check if the 174x is configured to enhanced mode (this is
mandatory) and if the driver is really part of that kernel.
Also check if the IRQ used is really free. It might be you are sharing it
with a serial port or something. You didn't notice that under DOS, but
linux might refuse to use the adaptec coz of that.
> Attempts to subsequently probe for 174x or to specify base address for
> SCSI device later at 0xCC000 give "Could not find device anywhere on
> system".
I do not understand this, I assume you refer to using the 174x driver as a
module. I've no experience here myself. it might be that it does not work
as a module (though I think at least recent versions should).
Michael.
(eowmob@exp-math.uni-essen.de or eowmob@pollux.exp-math.uni-essen.de
Please do not use my vm or de0hrz1a accounts anymore. In case of real
problems reaching me try mat42b@spi.power.uni-essen.de instead.)
