Hello John.  Thanks for the updates.  I'll try these diffs and see how
they go.  I've tried your twedm program, and it works pretty well, but
of course, my firmware is older than the one you developed against, meaning
I have to tell it to be unconditional in its treatment.  One of my cards
goes out to lunch when ever a command is issued, causing the driver to
return resource temporarily unavailable errors, but the other works.  I
suspect the card is crashing because there may be multiple failed drives on
one logical unit.
-thanks
-Brian
On Feb 4,  3:10pm, john heasley wrote:
} Subject: Re: 3ware management tools for NetBSD using the FreeBSD binaries?
} Tue, Feb 01, 2005 at 06:37:32PM -0800, Brian Buhrow:
} > 	Hello.  I'm trying to use the FreeBSD binary tools for the 3ware RAID
} > controller cards under NetBSD-2.0, and I find that they cannot find the
} > controller cards.  It looks like they try to look for 3ware data in the
} > sysctl tree, and failing that, give up.  I've looked in the NetBSD-current
} > sources to see if anyone has made the sysctl stuff work with the 3ware
} > cards in the twe(4) driver, but it appears not.  So, since I assume someone
} > must be using some 3ware management utilities, I wonder what it is they're
} > using, and how they made them work?
} 
} Adding a few sysctls seems to get FreeBSD's tw_cli working.  You can try
} these diffs:
} 	http://shrubbery.net/~heas/twe.diff.tgz
} 
} I have NOT tested it, but it does display controller information.  Note
} that it needs /dev/tweN.  tw_cli tries to create these, but does so with
} the wrong major device number.  cd /dev; sh MAKEDEV twe0.  It will also
} remove them if it believes the controller does not exist, eg: twe1 and
} so forth.
>-- End of excerpt from john heasley