[3438] in linux-scsi channel archive
Re: Adaptech AHA-2940 SCSI problem (again)
daemon@ATHENA.MIT.EDU (Mike Amorose)
Tue Mar 3 15:29:48 1998
In-Reply-To: <34FC5C5F.5EE4@idt.com>
Date: Mon, 2 Mar 1998 11:48:52 -0800
To: redhat-install-list@redhat.com
From: Mike Amorose <mamorose@hitachi-soft.com>
Cc: linux-scsi@vger.rutgers.edu
I would suggest first trying to disable the bootable CD in BIOS. Some
BIOSes are set to ONLY boot from the CD, some are set for 'failover' where
if no bootable CD is found, then another device is used to boot. I would
try disabling bootable CD and reboot from the floppy and try it again.
If this doesn't work, i would strongly suspect it's a SCSI termination
problem. The 1st and last **physical** device MUST be terminated. No other
SCSI devices on the bus can be terminated. The behaviour you mentioned
sounds like either a termination or ID problem: if the termination isn't
right or there are ID conflicts, then many machines will just keep sending
a SCSI info request signal and never get a response from (the) drive(s) it
**thinks** are there. This is true for almost every machine, whether an
Intel PC, Sun, or Macintosh.
The moral of the story is to be sure that the 1st and last **physical**
device on the bus are terminated and all other devices are NOT terminated.
Make sure the terminators on your drives are set right and there are no ID
# conflicts.
I recently set up a Dual Pentium Pro ATX machine with an Adaptec 7770
controller integrated on the motherboard. I had a similar problem, except
that the machine **appeared** to lock up even tho it was in actuality only
waiting infintely for a **response** from a drive that turned out to be
improperly terminated.
I would check all of the above 1st and be sure that none of these are the
problem.
Also, how many SCSI devices do you have on this machine?
-mike
------------------------
At 11:39 AM -0800 3/3/98, Sanjay Bhatia wrote:
>hi,
> this is the second time i am sending this to the list with more
>information about what's happening with my machine. I am hoping that
>someone else has a similar setup and can give me some pointers about how
>to solve this issue.
>
> i have a machine with an Adaptech AHA-2940 SCSI controller. When i
>boot the machine with a redhat (5.0 and 4.0) install disk, the
>controller is detected correctly, and so is the CDROM and HD attached to
>it. then, for some reason the kernel goes into an infinite loop trying
>to detect other devices on the bus. it resets the bus because of
>timeouts.
>
> the controller BIOS is enabled and set to terminate automatically, and
>the MULTIPLE LUNS option is enabled. the machine BIOS is set to look
>for a bootable CDROM at startup.
>
>can someone please let me know what could be going wrong?
>
>sb
>
>
>--
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
>http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> To unsubscribe: mail redhat-install-list-request@redhat.com
> with "unsubscribe" as the Subject.
>
> Problems should be addressed to <listmaster@redhat.com>.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
