[3187] in linux-scsi channel archive
Re: AHA1542CF suddenly stopped working! Help!
daemon@ATHENA.MIT.EDU (Leonard N. Zubkoff)
Tue Feb 3 13:48:18 1998
Date: Tue, 3 Feb 1998 10:06:06 -0800
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: libove@felines.org
CC: linux-scsi@vger.rutgers.edu, redhat-list@redhat.com
In-reply-to: <Pine.LNX.3.96.980203085417.746C-100000@panther.felines.org>
(message from Jay Vassos-Libove on Tue, 3 Feb 1998 09:25:33 -0500
(EST))
Date: Tue, 3 Feb 1998 09:25:33 -0500 (EST)
From: Jay Vassos-Libove <libove@felines.org>
[snip]
first installed the software to test it out) and it too would load the
boot loader and kernel from the SCSI chain, and get the same SCSI bus
screwup when the AHA1542 driver initialized.
[snip]
Another experiment: I booted a DOS 5.0 floppy, ran FDISK, wiped out the
Linux (NON-DOS) partitions, made a single primary full-size (307M) DOS
partition and made it bootable, rebooted the DOS floppy, formatted the
drive with system files, and ... oh, right, gotta do FDISK/MBR or else it
will still read the boot loader from Linux and load the kernel from the
middle of the disk where the DOS "format" didn't actually erase it :)
Okay, so I did FDISK/MBR and booted fine in to DOS.
As far as I'm concerned, this proves that the hardware is good, and that
the fault is something in the Linux kernel/driver.
Any suggestions, please? I'd really prefer to be using that Pentium
instead of the old 486 on which I'm now typing this message...
This proves nothing so far. Accesses made through the BIOS, which includes
loading the boot loader and kernel, as well as DOS operation (possibly unless
you've loaded the ASPI manager) do not require interrupts to be operational.
The most likely cause of the problems you've reported is interrupts not getting
from the host adapter to the Adaptec 1542 driver. Check the IRQ channel
assignment on the host adapter and make sure that IRQ channel is assigned to
"ISA" rather than "PCI" in the motherboard BIOS.
Leonard
