Bug 152660
| Summary: | Installer Take Inordinate Amount of Time to Detect Boot Drives on SCSI Channel B of Aic7899 Controller on Tyan Thunder K7 (2462) Motherboard | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Allen <dallen> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | pfrields, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-05-04 13:36:12 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Allen
2005-03-30 23:23:06 UTC
What driver are you trying to load? (What is the kernel module called?) I am having the such a problem while I try to install redhat enterprise WS version 4 on an IBM Intellistation 6850-25G which have Aic7899 Controller. At the first stage of the installation, it searches the aic7xxx driver and gets stuck. I didn't wait 30 minutes, I was sure that something was wrong. I will try to wait and see if it ends. Typing on ALT-F4 I see that it finds the correct Adaptec AIC-7899 scsi controller, but then it gets stuck. I also tryed to boot with noprobe, but than choosing the aic7xxx driver, it got stuck again. Is it possible to get the scsi driver image so I will load it from a disk ? Thanks, Dr. Amihai Silverman Computer Center Technion "I also tryed to boot with noprobe, but than choosing the aic7xxx driver, it got stuck again." This is not likely to have any effect, except as you've already noticed. "Is it possible to get the scsi driver image so I will load it from a disk ?" I don't know what this will buy you. It is not a problem related to accessing the driver, it is a problem related to the SCSI card itself. I suspect that it has more to do with the way the card is being told to behave by the kernel. I have repeated my tests several times. The period before I get any on-screen response from the installer is always ~25 minutes. Up until this point, the HDD activity light on the box repeats a blinking pattern at regular intervals. There are no further problems once the install gets past the initial barrier. Best Regards, David Allen. (In reply to comment #1) > What driver are you trying to load? (What is the kernel module called?) The problem occurs using the standard distro-supplied aic7xxx driver. Like I said, it eventually resolves itself. It just takes nearly half an hour to do so. Googling dug up info from others that 'insmod'ing an i2o driver instead of using the aic7xxx module would cure the problem. But I found that after extracting the driver module from the kernel and putting it where it could loaded (floppy or installer's RAM disk, on HDD), neither insmod nor modprobe (both linked to the same binary in the installer's path) would touch the module. Probably something I did wrong. Mass update of -test bugs to update version to fc4. (Please retest on final release, and report results if you have not already done so). Thanks. I'm a bit afraid to do this because ... well, see Bug 167791. All 2.6.12 kernels fail to complete a boot on this motherboard (Tyan K7 2462). This is a working machine right now, albeit still running the 2.6.11 kernel, so I am reluctant to try moving it to FC4. However, I can try the final release of FC4 just far enough to see if this bug still exists. My experience with this particular motherboard is that as the kernel is "improved", SCSI support degrades. 2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you. This is a mass-update to all currently open kernel bugs. A new kernel update has been released (Version: 2.6.15-1.1830_FC4) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO_REPORTER state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. Thank you. Closing per previous comment. |