SUMMARY: Xylogics 450/451 controller question

From: Chris P. Ross (cross@eng.umd.edu)
Date: Thu Jan 07 1993 - 00:43:44 CST


  Hi! Well, I actually got iy working. Took alot of playing, and a
lot of reading the docs, but it can be done. :-)

  Original question:

-----
  I have an old Sun 3/280. I have in it two xylogics 450/451 disk
controllers, but I have a couple extra disks sitting around. According to
any documentation I can find, more that 2 of these controllers can't be put
in a single machine. I was wondering if anyone knew of an "unsupported"
configuration to make 3 work.

  All help appriciated.

                                                - Chris

  ps,
        I already have one of the controllers rigged to handle more than
two disks. But, since upgrading to SunOS 4.1.1 (from 4.1) I can't get the
OS configured right to see it. Does anyone know the checklist I need to
make this work?
-----

  Most of the responces I got were about the ps. I figured out, after
I sent this, that my problem there was only a typo in the kernel. But,
for those who don't know how to do this and are wondering, all you need
to do is add config lines to the kernel. Should look like so:

controller xyc0 at vme16d16 ? csr 0xee40 priority 2 vector xyintr 0x48
controller xyc1 at vme16d16 ? csr 0xee48 priority 2 vector xyintr 0x49
disk xy0 at xyc0 drive 0
disk xy1 at xyc0 drive 1
disk xy2 at xyc0 drive 2
disk xy3 at xyc0 drive 3
disk xy4 at xyc1 drive 0
disk xy5 at xyc1 drive 1

etc...

  Note: Many people hadn't known that to access any drives above xy3
in address (ie, xy4, xy5, etc) via the format program, you need to change
the format.dat definition of "search_path". If you change this, format
sees them just fine...

  Thanks to the following for replying to the ps portion of my question:

Piete.Brooks@cl.cam.ac.uk
don@doug.med.utah.edu (Don Baune 581-6088 MIRL)
ups!kevin@fourx.aus.sun.com (Kevin Sheehan)
Gene Rackow <rackow@antares.mcs.anl.gov>

  Now, for the bigger problem. Getting the third controller online.
I added a controller line to my kernel so that I now have:

controller xyc0 at vme16d16 ? csr 0xee40 priority 2 vector xyintr 0x48
controller xyc1 at vme16d16 ? csr 0xee48 priority 2 vector xyintr 0x49
controller xyc2 at vme16d16 ? csr 0xee50 priority 2 vector xyintr 0x4a
disk xy0 at xyc0 drive 0
disk xy1 at xyc0 drive 1
disk xy2 at xyc0 drive 2
disk xy3 at xyc0 drive 3
disk xy4 at xyc1 drive 0
disk xy5 at xyc1 drive 1
disk xy6 at xyc2 drive 0
disk xy7 at xyc2 drive 1

  That was the easy part. The hard part was configuring the DIPs and jumpers
on the card itself. I can't really tell you what I set them too, tho, as much
of it is dependant on what you're using for other things. But, if you sit
down with the manuals for the 451 controller, and the manual for the VME-to
multibus converter card, you can figure it out. (Note: The VME-to-Multibus
card is the bear. It has a horribly complex system for figuring out DIP
settings. But, just aim for the numbers above, and it all works out.)

  Also note. It only worked when I moved cards around such that all of
the 451 controllers were contiguous on the VME bus.

  There's alot in here that's vague. If you want any more help/specifics,
let me know. I'd be glad to share what I've learned...

  Kudos to these people for alot of pointing me in the right direction(s)
to figure it out:

Jeff Nieusma <stortek!Jeff_Nieusma@csn.org>
dan@bellcore.com (Daniel Strick)
Dan Transue <odt@dcs.bellcore.com>

  Thanks again.

                                 - Chris

--
Chris P. Ross                         University Of Maryland
cross@eng.umd.edu                     Engineering Computer Facility
Work#: (301)/405-3689                 Project GLUE



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:20 CDT