Bug 18429 - Infinite loop resetting AHA-2940 during install
Summary: Infinite loop resetting AHA-2940 during install
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.2
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Doug Ledford
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-05 16:53 UTC by Vladimir Gendler
Modified: 2005-10-31 22:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-12-17 03:30:02 UTC
Embargoed:


Attachments (Terms of Use)

Description Vladimir Gendler 2000-10-05 16:53:05 UTC
At the step of loading aic7xxx for Adaptec AHA-2940U/UW
install hangs on. ALT+F4 shows timeout on CD-ROM quering
and endlessly resets the SCSI.
Hard drives look fine.
This problem exists for versions 6.0, 6.1, 6.2, 7.0.
 AHA-2940 BIOSes tried were 1.34.3 and the
lates one - 1.20.0.

This problem was verified on other machines with
different modification of AHA-2940.

Install with parameter aic7xxx=no_probe did not help.
Installation of RedHat LINUXes 5.x was without problems
The installation goes fine for Ultra2 AHA-2940U2W.
This is the same bug as 5994 which was closed without
any resolution.

                    Sincerely, Vladimir.

Comment 1 Juan Jose Portela Zardetto 2001-07-02 12:16:27 UTC
Problems appears in RH 7.1 too.

Comment 2 Need Real Name 2002-04-04 15:25:30 UTC
They appear in RH 7.2 too. I Tried hard with 2 Ciprico Rimfire 100GB Hard disks 
( SCSI Id's 2 and 3) but no luck.

If there is only one Hard disk in the chain, it is detected well.

Comment 3 Doug Ledford 2002-04-11 15:14:46 UTC
This sounds like a negotiation problem between the driver and the specific
peripherals you are plugging into the card.  Try going into the Adaptec BIOS and
setting the maximum allowed transfer speed and the bus width to no more than
what the CD-ROM will actually support and see if that solves the problem.


Note You need to log in before you can comment on or make changes to this bug.