2.4.20 SCSI problems on NASRaQ

2.4.20 SCSI problems on NASRaQ

[Neurophyre]

Hello all.  I'm trying to get Debian 3.0r1 working usefully on a
MIPS-based Seagate (Cobalt) NASRaQ.  The system uses the same processor
as the Qube 2 and has an integrated 53c860 SCSI controller, which would
appear to be supported by no fewer than three kernel drivers!

I'm compiling the kernel source available at
ftp://ftp.linux-mips.org/pub/linux/mips/kernel/test/linux-2.4.20.tar.gz
WITH Paul Martin's tulip and PCIfun patches applied.  I should mention
that the stock 2.4.20 source with the debian kernel-patch-2.4-cobalt
package applied to it presented numerous problems and I had to give up.

The problem is that upon boot (or module installation), I get similar
messages from all three SCSI drivers.

Examples:

sym.0.8.0: IO region 0x10102000[0..127] is in use
or
ncr53c8xx: IO region 0x10102000[0..127] is in use

On boot, the boot process just goes on, but no 'scsi0 blah blah'
printout occurs, and nothing is printed about a tape drive I have
attached to the machine for testing.

When installing as a module (only tested with sym53c8xx driver) the
module installation fails and a message like above is printed to the
serial console.

Doing a 'cat /proc/scsi/scsi' yields

Attached devices: none

no matter what.

Does anyone have any suggestions?  We'd really like to modernize the
NASRaQ and still be able to use its SCSI port.

Re: 2.4.20 SCSI problems on NASRaQ

[Neurophyre]

A little update on the problems with none of the 3 drivers initializing 
the 53c860 SCSI controller on the Seagate (Cobalt) NASRaQ:

I've built the 2.5.47 CVS snapshot kernel from linux-mips.org, but even 
with just about everything modularized, the kernel is just over 100K 
too big for the NASRaQ's boot loader.  So, it would seem without 
getting very creative that 2.4.x is the end of the road for this 
hardware.. this means I can't test to see if any of the drivers now 
work in the linux-mips source tree.

I also thought it might be good to include /proc/pci, since someone 
off-list mentioned to me that perhaps some other device is reserving 
the controller's address space (?)..  again, here's what the message 
from all three drivers looks like (using the newest one as an example):

sym.0.8.0: IO region 0x10102000[0..127] is in use

here is /proc/pci.  The SCSI controller is device 8.

PCI devices found:
  Bus  0, device   0, function  0:
    Class 0580: PCI device 11ab:4146 (rev 17).
      Master Capable.  Latency=64.
      Non-prefetchable 32 bit memory at 0x0 [0x3ffffff].
      Non-prefetchable 32 bit memory at 0x4000000 [0x4000fff].
      Non-prefetchable 32 bit memory at 0x1c000000 [0x1dffffff].
      Non-prefetchable 32 bit memory at 0x1f000000 [0x1fffffff].
      Non-prefetchable 32 bit memory at 0x14000000 [0x14000fff].
      I/O at 0x14000000 [0x14000fff].
  Bus  0, device   7, function  0:
    Class 0200: PCI device 1011:0019 (rev 65).
      IRQ 4.
      Master Capable.  Latency=64.  Min Gnt=20.Max Lat=40.
      I/O at 0x100000 [0x10007f].
      Non-prefetchable 32 bit memory at 0x12000000 [0x120003ff].
  Bus  0, device   8, function  0:
    Class 0100: PCI device 1000:0006 (rev 2).
      IRQ 4.
      Master Capable.  No bursts.  Min Gnt=8.Max Lat=64.
      I/O at 0x10102000 [0x101020ff].
      Non-prefetchable 32 bit memory at 0x2000 [0x20ff].
  Bus  0, device   9, function  0:
    Class 0601: PCI device 1106:0586 (rev 39).
  Bus  0, device   9, function  1:
    Class 0101: PCI device 1106:0571 (rev 6).
      Master Capable.  Latency=64.
      I/O at 0xcc00 [0xcc0f].
  Bus  0, device   9, function  2:
    Class 0c03: PCI device 1106:3038 (rev 2).
      Master Capable.  Latency=22.
      I/O at 0x300 [0x31f].


If anybody has any suggestions of what I might be able to do to get the 
SCSI controller working, I'd love to hear it.  Also if there are any 
other things you would like to see besides what I've shown.  I'm not a 
kernel hacker.  :-(

As it stands now, anybody with a MIPS-based NASRaQ is out in the cold 
when it comes to upgrading their system.

Finally, since the SCSI controller obviously worked with Cobalt's 
(patched) 2.0 kernel, maybe an older kernel might work?  Does anybody 
have any snapshots of the 2.2.x source tree with MIPS patches applied?  
Or access to Cobalt's old patches even?