[2595] in linux-scsi channel archive
Re: What is this???
daemon@ATHENA.MIT.EDU (Neon Spiral Injector)
Sun Oct 5 13:59:03 1997
Date: Sun, 05 Oct 1997 13:52:09 -0400
From: Neon Spiral Injector <clubneon@safari.net>
To: linux-scsi@vger.rutgers.edu
Neon Spiral Injector wrote:
>
> So far Richard's idea seems the best bet. I looked at the ncr5380
> drivers and in kernel 2.0.30 they have actually been patched to support
> the ncr53c400. So, I had to do some serious work to get a working
> Debian boot disk (they have some good ideas on making Linux easier to
> install, but still need to work some kinks out) with a kernel that had
> support for the ncr53c400 compiled in. But anyway, I did get what
> seemed to be a working disk, but when I boot with it I get a:
>
> scsi0: SCSI bus busy, waiting up to five seconds
> scsi0: bus busy, attempting abort
>
> So what to do now?
Well here is what I did now. The kernel I was using was from the
Slackware distro it said it was for the ncr5380 and the 53c400, but you
saw the error I was getting.
Well I sat down on my working system I'm sending this mail from and
built a new kernel here for the 52c400. I modified the
./drivers/scsi/Makefile for no IRQ and base 0x300. I took the resulting
kernel and put it on the Debian boot disk and tried booting with it.
This time it actually found the card and told me that the interupts were
disabled and to jumper the board for a free IRQ. But not too long after
that I got a:
scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0,
lun 0 0x00 00 00 00 00 00
scsi0 : aborting command
scsi0 : distination target 0, lun 0
command = 0x00 00 00 00 00 00
NCR5380 : coroutine is running.
STATUS_REG: 00
BASR: 00
ICR: 00
MODE: 01 ,MODE ARPITRATION
scsi0 : REQ not asserted, phase unknown.
NCR5380 core release=7. ncr53c400 release=2. Generic5380 release 1
Base Addr: 0x00300 io_port: 0000 IRQ: None.
NCR5380 : coroutine is running.
scsi0: no currently connected command
scsi0: issure_queue
scsi0: disconnected_queue
(all that repeated again)
scsi0 : warning : SCSI command probally completed successfully before
abortion
Well then I got busy, and pulled the cover off of the machine, and
pulled the SCSI card, and set it for base address 0x350 IRQ:5 just like
the defaults that were orginally in the Makefile. Remade the kernel and
tried it. Same thing minus the message about not having an interupt
enabled and in the errors the base address and IRQ were differnet.
Whoops I just found out, after rebuilding the kernel 3 more times, that
I am using the "Memory" mapping method, so the base address should be
0x0CC00. Only I rebuilt it that way, and I get the same errors. It is
actually when I use the "Port" method that I just get the busy,
attempting abort. Perhaps I am sort of on the right track. I haven't
tried the corrtect Memory base address with No IRQ. Is that worth a
shot? Or should I try different bases (memory or port) and other IRQ
combonations?
Sorry for the length of this. I'm building this computer for a really
stingy person, who I convinced that Linux was the least expencive way to
go, and I'm dreading proving myself wrong.
Thanks again,
Chris
P.S. Whoops, I just sent this one only to myself, here it is to
everyone. In the mean time I think I found that my base address quoted
above was wrong, and have tried all sorts of junk with 0xCC000. Is that
right now for a memory mapped card? I have also tried some of the dip
switches on the card, but don't know what they mean, or which ones I
should try. Can anyone tell me what, PIO, TERM, and OWS are? And which
way (On/Off) would be my best bet for compatibility?
