[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference nlfdc::linux-users

Title:Linux, the Free Operating System
Notice:New here? Sign in on topic 2
Moderator:EST::DEEGAN
Created:Fri Feb 11 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:609
Total number of notes:2862

605.0. "Problem w/AHA152x + recent Linux kernel boot -- System hangs" by SUBPAC::BAIR () Sun May 25 1997 09:14

I am unable to get Linux to see my 2 RZ56's attached to my 
Adaptec AHA1520 SCSI controller when booting from a recent
(kernel 2.0.x) boot disk (either Red Hat or Slackware).

I have chosen a boot disk which supports the AHA152x,
and entered the "aha152x=0x340,11,7,1" parameter at boot.

In booting, the controller is seen:

aha152x0: vital data: PORTBASE=0x340, IRQ=11 SCSI ID=7, ... (etc)
aha152x: trying software interrupt, ok
scsi0: Apaptec 152x SCSI driver, $Revision: 1.18$
scsi: 1 host

However, at this point the system hangs.

If I omit the parameter at boot, the system boots, but I
(obviously) can't see the SCSI disks.

The strange thing is that everying worked find under earlier
versions of Linux (with the 1.2.x kernel), e.g. Slackware 2.0
and RedHat 2.1.

Any ideas where to start ?

T.RTitleUserPersonal
Name
DateLines
605.1spin up?OGBON::desgor.shl.dec.com::gordonDes Gordon@snoTue May 27 1997 09:042
just an idea but did they perhaps change how they handle spin up on 
power on?
605.2Not sure I understand ...SUBPAC::BAIRWed May 28 1997 01:1615
Thanks for the idea. 

I had modified the internals of the RZ56s to spin up on power on. In addition,
I applied power to the disks prior to booting the system.

Are you suggesting that the new (2.x kernel) drivers expect to have to
spin up and RZ56 ?

BTW I know that the system "sees" the AHA1520, since on powering _down_
the RZ56s, the system spits out multiple complaints about the SCSI bus
being freed and otherwise indicating the departure of the BA350 box at
the other end of the external SCSI cable. Powering up again, though,
doesn't make the system happy.

/Larry
605.3OGBON::desgor.shl.dec.com::gordonDes Gordon@snoThu May 29 1997 09:448
g'day,

I was thinking that you may have had 56's that had not 
had the setting changed and that the older kernel *may* had 
drivers that may have accomodated this. I have a 1520 in my 
system driving a CD and this works fine, this is with the 
latest 4.1 red hat, the older V3x red hat I never could get 
to work