[4593] in linux-scsi channel archive
Re: Insmodding NCR SCSI
daemon@ATHENA.MIT.EDU (Marc SCHAEFER)
Fri Aug 21 17:43:03 1998
From: Marc SCHAEFER <schaefer@alphanet.ch>
Date: 21 Aug 1998 21:47:16 +0200
Apparently-To: linux-scsi@vger.rutgers.edu
To: unlisted-recipients:; (no To-header on input)
Maarten van Leunen <etmmvle@etm.ericsson.se> wrote:
> into the kernel that's okay. The other modules NCR3C8xx.o or something
> give me a "Device busy or Resource occupied" or something when trying to
this is ncr53c8xx
insmod ncr53c8xx
The suggested order is
insmod scsi_mod; insmod ncr53c8xx; insmod sg
then you can use your scanner.
If you get a 'Device busy or Resource occupied', check with
`dmesg' if there is any error --- such as ``IRQ already in use''.
> P.S. It's kinda freaky, the SCSI card had the same IRQ as ttyS0, so used
> ISAPNP during startup to reset the IRQ to 7. Maybe I have to, because of
> this, put some parameters (which ones?) at the end of the "insmod
> ncr3c8xx.o"?
Isn't that a *PCI* chip ? So why are you using ISAPNP utilities ?
Also, if the SCSI card had the same IRQ as ttyS0, you have to fix
that before. 7 is not something common for a serial device,
so I assume you are using a ISA I/O card. If your BIOS has
a PCI/ISA-Plug and play configuration, go into it, disable
automatic allocation and reserve IRQ 7 for ISA only.
NB: all the above is wrong if your NCR card is not a PCI. In that
case maybe it's not even the ncr53c8xx driver.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
