Manuel,

I would write down the settings of the first card, remove it, and set the
second card to the those settings.  Reboot the system to see if it functions -
 that will test the second card.  If the card works you will remove some of the
guess work.  This will also allow you to test the new card with a known good
SCSI cable (potentially a big area of problems).

If you go to the Adaptec Web site you will find the information
you need about configuring this series of controllers.  The big things are:

Port Address (130, 134, 230, 234, 330, 334 (default))
DMA Channel (0, 5 (default), 6, 7)
DMA Xfer Rate (start with 5.0MB/sec)
IRQ (9, 10, 11 (default), 12, 14, 15) (I would avoid 9 if possible)

If the second card works,  set one to the defaults, providing no conflicts
with other cards and set the second to:

Port Address: 330 or 234 or 230... (in that order)
DMA Channel: this will require some experimenting on your part refer to docs
DMA Xfer Rate: 5.0MB/sec
IRQ: whatever one you can find that is free in the list.

Hope this helps.

			-Steve



> Hi Manuel and Tom,
> 
> Well, I changed some of the settings and so far
> nothing shows up in the dmesg about the scsi card.  I
> am wondering at this point if I should play around
> with some of the other setting and see what happens. 
> I hope we could get it working because I really don't
> want to deem it DOA.
> 
> Thanks again for all the help!
> 
> J Silverman
> --- Thomas Bieg <tomsbsd03@t-email.de> wrote:
> > (I'm sure Manuel could help you better on this, but
> > since
> > it's already late here in Europe he may be offline
> > by now,
> > so I thought I'd try to chime in in the meantime...)
> > 
> > Before you can access your drives in any way the
> > card has
> > to be recognized by your kernel at boot time, which
> > seems
> > to be not the case.
> > 
> > Your dmesg output should contain something like
> > 
> >      aha0 at isa0 ...
> >      scsibus0 at aha0
> >      sd0 at scsibus0 ...
> > 
> > 
> > There could be several reasons for the failure:
> > 
> > - Your kernel doesn't include support for this card
> > 
> >    Unlikely, since every GENERIC kernel has the
> > support
> >    by default.
> > 
> > - The jumper settings on your card don't match those
> >    expected by the kernel
> > 
> >    Could be the problem here; this card seems to be
> >    highly configurable (I don't have such a card)
> > 
> >    The (GENERIC) kernel searches the card at IO
> > ports
> >    0x330 or 0x334, so you have to make sure your
> > card
> >    is jumpered to one of these (or you will have to
> >    build a customized kernel).
> > 
> > - The settings of your card conflict with any other
> >    piece of hardware in your system
> > 
> >    Check that none of the "irq"s, "drq"s, ... from
> > your
> >    dmesg (or possibly from other unrecognized cards
> > if
> >    there are any) match the settings of your card.
> > You
> >    may also have to reserve the interrupt in your
> > BIOS
> >    setup.
> > 
> >    (Look for something like "PnP/PCI Configuration",
> >     set "Resources controlled by: manual", then
> > "IRQ-x
> >     assigned to: Legacy/ISA". )
> > 
> > - Any other reason I didn't think of... (Besides
> > some
> >    broken hardware.)
> > 
> > 
> > I hope this gets you a bit further.
> > 
> > (I'm off to bed now...)
> > 
> > Tom
> --- Manuel Bouyer <bouyer@antioche.lip6.fr> wrote:
> 
> > 
> > yes: dmesg
> > look for aha, scsibus and sd
> > 
> > --
> > Manuel Bouyer, LIP6, Universite Paris VI.          
> > Manuel.Bouyer@lip6.fr
> >      NetBSD: 24 ans d'experience feront toujours la
> > difference
> > --
> 
> __________________________________
> Do you Yahoo!?
> Exclusive Video Premiere - Britney Spears
> http://launch.yahoo.com/promos/britneyspears/
>