RE: [newbie] Adaptec SCSI Installation AVA 1505

2001-02-28 Thread Daryl Johnson

Well, the full story is :

Portbase = 0x340this is jumpered on the board
IRQ = 9 this too is jumpered on the board
SCSI ID = 7 which is fairly standard
recconect is enabled
parity is enabled
synchronous is enabled
delay = 500
extended translation is disabled

thus we get the command

insmod aha152x aha152x=0x340,9,7,1,1,0,500,0

and for a glorious half hour last night that seemed to be accepted so that
when I checked KDE/Information/IRQ against 9 it said AHA152x and against
KDE/Information/Ports against 340 it said AHA152x.
dmesg identified the board and wqas suggesting ftape as a tape device - even
though that didn't seem to work.

Anyway, now the command insmod etc no longer works, I have the same error
message I started with:

Using /lib/modules/2.2.17-21mdk/scsi/aha152x.o: init_module:
Device or resource busy Hint: insmod errors can be caused by
incorrect module parameters including invalid IO or IRQ
parameters

and dmesg says:

aha152x: BIOS test: passed, detected 1 controller(s)
aha152x0: vital data: PORTBASE=0x340, IRQ=9, SCSI ID=7, recconect=enabled
parity=enabled, synchronous=disabled, delay=500, extended
translation=disabled
aha152x: trying software interrupot, lost.
aha152x: IRQ 9 possibly wrong. Please verify.

So in the words of the prophet and philosopher Foul Ole Ron - 'buggrit,
millenium hand and shrimp, I tole 'em.' (Explanations upon request  :o)  )

So if anyone has any valid suggestions for my problem...

regards

Daryl

(ps Valid suggestions for my problem do NOT include 'rub ointment on it'!)


> [mailto:[EMAIL PROTECTED]]On Behalf Of mark
> Subject: RE: [newbie] Adaptec SCSI Installation AVA 1505
>
>
> What error message do you get?
>
>
> On Tue, 27 Feb 2001, you wrote:
> > Damn me if it hasn't stopped again. Any suggestions?
> >
> > regards
> >
> > Daryl





RE: [newbie] Adaptec SCSI Installation AVA 1505

2001-02-27 Thread Daryl Johnson

Damn me if it hasn't stopped again. Any suggestions?

regards

Daryl

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Daryl Johnson
> Sent: 27 February 2001 21:13
> To: [EMAIL PROTECTED]
> Subject: RE: [newbie] Adaptec SCSI Installation AVA 1505
> 
> 
> At Last!
> 
> I found a doc which suggested that the silk screening of the 
> jumpers on the
> board was faulty but use the diagram instead in the online manual 
> available
> on the Adaptec site.
> 
> I checked and found that I WAS using the correct jumper for IRQ 9 
>  and also
> port 0x140, neither of which were causing conflicts in the tables.
> 
> On a whim I jumpered the board top use port 0x340 and tried the insmod
> command
> 
> insmod aha152x aha152x=0x340,9,7,1,1,0,500,0
> 
> and the board loaded! 
> 
> All I have to do now is find out which tape device in /dev my Colorado
> likes.  Sheesh.
> 
> Thanks Mark
> 
> regards
> 
> Daryl
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of mark
> > Sent: 22 February 2001 02:12
> > To: [EMAIL PROTECTED]
> > Subject: Re: [newbie] Adaptec SCSI Installation AVA 1505
> >
> >
> > Try this:
> >
> > insmod aha152x aha152x=0x140,9,7,1,1,0,500,0
> >
> > Don't ask me what it all means, but it works on this card.
> >
> > [...]
> 
> 
> 




RE: [newbie] Adaptec SCSI Installation AVA 1505

2001-02-27 Thread mark

What error message do you get?


On Tue, 27 Feb 2001, you wrote:
> Damn me if it hasn't stopped again. Any suggestions?
> 
> regards
> 
> Daryl
> 
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Daryl Johnson
> > Sent: 27 February 2001 21:13
> > To: [EMAIL PROTECTED]
> > Subject: RE: [newbie] Adaptec SCSI Installation AVA 1505
> > 
> > 
> > At Last!
> > 
> > I found a doc which suggested that the silk screening of the 
> > jumpers on the
> > board was faulty but use the diagram instead in the online manual 
> > available
> > on the Adaptec site.
> > 
> > I checked and found that I WAS using the correct jumper for IRQ 9 
> >  and also
> > port 0x140, neither of which were causing conflicts in the tables.
> > 
> > On a whim I jumpered the board top use port 0x340 and tried the insmod
> > command
> > 
> > insmod aha152x aha152x=0x340,9,7,1,1,0,500,0
> > 
> > and the board loaded! 
> > 
> > All I have to do now is find out which tape device in /dev my Colorado
> > likes.  Sheesh.
> > 
> > Thanks Mark
> > 
> > regards
> > 
> > Daryl
> > 
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of mark
> > > Sent: 22 February 2001 02:12
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [newbie] Adaptec SCSI Installation AVA 1505
> > >
> > >
> > > Try this:
> > >
> > > insmod aha152x aha152x=0x140,9,7,1,1,0,500,0
> > >
> > > Don't ask me what it all means, but it works on this card.
> > >
> > > [...]
> > 
> > 
> >
-- 
***
fairlane at voyager dot net
www.geocities.com/dieseltempo
***




[newbie] Adaptec SCSI Installation AVA 1505

2001-02-21 Thread Daryl Johnson

I have come into posession of an Adaptec AVA 1505 scsi i/f board (isa bus),
which, if I can get it running will allow me to use my Colorado tape drive.

The board appears to have generated a lot of mails on one group and another.
What is common to all of them is that it is implied that the board is usable
with the aha152x driver - which certainly comes with the 7.2 distribution.

I have set the card's jumpers to use interrupt 9 and i/o port 140. It is
installed in my sole, available isa slot.

Using the command

insmod aha152 aha152x=0x140,9

gives me the message

Using /lib/modules/2.2.17-21mdk/scsi/aha152x.o: init_module:
Device or resource busy Hint: insmod errors can be caused by
incorrect module parameters including invalid IO or IRQ
parameters

I have tried including the device number (7) in the command.  I have tried
using modprobe instead (modprobe -a aha152x aha152x=0x140,9,7 etc)

If anyone can come up with the magic technique I would be thrilled,
grateful, ecstatic (insert adjective of choice).

regards

Daryl Johnson