Solved

Adaptec 1520A/1522A troubles

Posted on 1997-07-08
3
343 Views
Last Modified: 2013-12-15
Hello all,

I have been having problems getting my adaptec AHA-1520A/1522A SCSI card working. It only has my ZIP drive hooked up to it. It worked fine a while back (I forget exactly how long, a month or so). Though I have done a system upgrade since then. I've upgraded to a SuperMicro P6DNF with dual PPro150s. I also started using DMA support
with my Western Digitial hard drives.

Some general info: I have kernel 2.0.30, libc-5.3.12. It's basically a RedHat 4.0 system that I've hand upgraded most of it to 4.1 with a few packages from 4.2.

Whenever I try to load the aha-152x driver (either using kerneld or with insmod). It seems to start up ok, then dies with the following errors (taken from /var/log/messages):

Jul  8 00:40:05 kali kernel: (all the lines below started with this)

aha152x: BIOS test: passed, auto configuration: ok, detected
      1 controller(s)
aha152x0: vital data: PORTBASE=0x340, IRQ=11, SCSI ID=7,
      reconnect=enabled, parity=enabled,
      synchronous=disabled, delay=100, extended
      translation=disabled
aha152x: trying software interrupt, lost.
aha152x: IRQ 11 possibly wrong.  Please verify.
scsi1 : Adaptec 152x SCSI driver; $Revision: 1.18 $
scsi : 1 host.
scsi : aborting command due to timeout : pid 0, scsi1,       
      channel 0, id 0,lun 0 0x00 00 00 00 00 00

(All the lines above each appeared twice, I deleted the
 duplicates and I idented the wrapped lines.)

I've tried changing the IRQ and removing all non-essential cards but the scsi-controller but it still gives that irq error. I've tried going back to kernel 2.0.28, and compiling it without SMP support. I've tried giving it specifics with insmod (ie. 'insmod aha152x aha152x=0x340,11,7). I've
even tried shutting off DMA support (ie. 'hdparm -d0').

I know it's not a hardware problem, as it all works perfectly fine in Dos. The IRQ and SCSI ID are set correctly on the board. The ZIP drive is set to SCSI ID 5 if that means anything to you.

Thanks,

John Eikenberry
[jae@ai.uga.edu - http://www.ai.uga.edu/students/jae/]
____________________________________________________________
"A society that will trade a little liberty for a little
 order will deserve neither and lose both."
                                         --B. Franklin


0
Comment
Question by:sakti070897
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 2

Accepted Solution

by:
cedric earned 100 total points
ID: 1628577
Hy,

well, it seems you forgot to assign an IRQ in your mother board's bios PnP/IRQ setup.

By default, on many brand new main board, the IRQ are all for PnP/ICU controlled cards. The 1520/1522 is NOT. So go into you bios and assign IRQ 11 to be free for ISA cards. Save reboot and you should be ok.
Byby.
0
 

Author Comment

by:sakti070897
ID: 1628578
Thanks a ton Cedric. I completely forgot about having
to change the bios settings. If you are ever going to
be in Athens, GA, drop me a line at jae@ai.uga.edu and
I'll buy you a beer. :)
0
 
LVL 2

Expert Comment

by:cedric
ID: 1628579
Hy,

i'm happy for you and thanks for the beer :^)

byby
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

rdate is a Linux command and the network time protocol for immediate date and time setup from another machine. The clocks are synchronized by entering rdate with the -s switch (command without switch just checks the time but does not set anything). …
Using 'screen' for session sharing, The Simple Edition Step 1: user starts session with command: screen Step 2: other user (logged in with same user account) connects with command: screen -x Done. Both users are connected to the same CLI sessio…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…

695 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question