[7578] in linux-scsi channel archive
Re: aic7xxx autoscanning
daemon@ATHENA.MIT.EDU (Alan Cox)
Mon Nov 22 13:15:23 1999
To: Werner_Kliewer@MPIC.mb.ca
Date: Mon, 22 Nov 1999 18:10:35 +0000 (GMT)
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <VA.000001c4.0ea95052@verndesk.mpic.mb.ca> from "Werner Kliewer" at Nov 22, 99 11:00:38 am
Content-Type: text
Message-Id: <E11pxvA-0003sV-00@the-village.bc.nu>
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> Linux, as near as I can tell, does not yet support PCI token ring
> adapters, at least not any I have here. Therefore I am using an IBM ISA
We support the Olympic chipset based IBM adapters (ie non lanstreamer)
> 1. leave IRQ 5 in the PNP range. When I do this, the system boots fine,
> but my serial port communication through ttyS1 to the UPS is very
> unreliable. In fact only about 10% of the time will it establish
Did you also change the kernels view of the IRQ used for ttyS1 with
setserial ? If you didnt then this setup may work when you adjust the
irq
> 2. assign IRQ 5 to ISA Legacy resources. When I do this, the boot
> appears to hang discovering SCSI devices. If I leave it long enough,
> the tape drive is discovered at every possible SCSI address on the bus
> and then the process begins to loop.
That sounds like an interrupt isnt being delivered properly.
> What is the interaction of the device discovery process and IRQ's? What
> driver settings might I be able to use to circumvent this process? Or
> do I not have any options here?
You are in a maze of twisty little bios options all different. Im afraid
thats the unfortunate truth. The IRQ routing on a PC is BIOS controlled.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
