[4670] in RedHat Linux List

home help back first fref pref prev next nref lref last post

aha152x-failed probing

daemon@ATHENA.MIT.EDU (Steve Moore)
Sat Nov 16 09:35:01 1996

Date: Sat, 16 Nov 1996 08:33:09 -0600 (CST)
To: redhat-list@redhat.com
From: capsteve@reveregraphics.com (Steve Moore)
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com

just recently got our version of redhat 4.0, but we(there are three of us
who attemped this with equal success)can't get much beyond the install
stage without dismall failure.

anyone have a suggestion to what i can do to make redhat 4.0 recognize the
scsi card, specifically aha1522b with bios v1.15?

tried installing from scratch several times, but everytime during boot
up, redhat is failing to see the host.
the specific message in question is :

scsi : 0 hosts

during the install process, we choose the aha152x as the scsi adapter,
but we have to put specific params in since the autoprobe doesn't seem
to recognize it.

the specific params we're inputing are as follows:

aha152x=0x140,11,7,1

this based according to the board address,irq,scsi id, and reconnect option.

during the install, ther following slices were indicated:
hda2   /
sda1   swap
sda2   /usr
sda3   /usr/src
sda4   extended
sda5   /home
sda6   /usr/local
sda7   /misc

/ was installed onto the ide drive on a second partition, so we are
actually able to boot, but when it goes thru ext2fsck for the other
slices, we get a message that superblock not found. we're dumped into a
shell requesting to fsck or ext2fsck. after attempting to fsck with the
alternate superblock suggested(with no success), i su'ed and tried modprobe.

i was actually able to use modprobe, inputting the following:
modprobe -t scsi \aha152x.o

this immediately allowed me to mount all the slices, fsck them, no
problem. i tried to recompile a new kernel, both monolithic and mod, but
to no avail, i'm a bonehead! i can't get this thing to work...

what's really frustrating is that if we do a slackware install, during
the install process, there's a point where we're asked for special
params during boot up.  slackware see's the aha152x alright, why doesn't
redhat? what are we doing wrong? is redhat's kernel/modules not as current
as slackware?

i'd really like to standardize the linux installs we've got in the
office, but its gotta be an easy fix, otherwise we'll keep all the
machines slackware...

any suggestion would be appreciated...



--
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
  ________________________________________________________________________
  http://www.redhat.com/RedHat-FAQ   http://www.redhat.com/RedHat-Errata
  http://www.redhat.com/RedHat-Tips  http://www.redhat.com/mailing-lists
  ------------------------------------------------------------------------
To unsubscribe: mail -s unsubscribe redhat-list-request@redhat.com < /dev/null


home help back first fref pref prev next nref lref last post