Bug 162473
Summary: | FC4 cannot install because it does not identify SCSI HDDs (sym53c8xx) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sorin-Razvan Popa <sorin.popa> |
Component: | kernel | Assignee: | Tom Coughlan <coughlan> |
Status: | CLOSED CANTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | davej, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-11-19 09:04:55 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: | |||
Bug Depends On: | |||
Bug Blocks: | 169613 |
Description
Sorin-Razvan Popa
2005-07-05 10:59:14 UTC
[This comment has been added as a mass update for all FC4 kernel bugs. If you have migrated this bug from an FC3 bug today, ignore this comment.] Please retest your problem with todays 2.6.12-1.1398_FC4 update. If your problem involved being unable to boot, or some hardware not being detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE* installing any kernel updates. If in doubt, you can recreate this file using.. mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak mv /etc/modprobe.conf /etc/modprobe.conf.bak kudzu Thank you. Does this problem occur with the most recent FC 4 kernel? You mentioned the HP NetRAID controller, which uses the MegaRAID driver, but the console output shows the sym53c8xx driver loading. Is it accurate to say that this system works with the 2.4 kernel, but not with the 2.6 kernel? Please post the lspci output, and the /var/log/messages boot messages, if you have a system that boots up. 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. Due to the overhead involved in creating new ISOs (which is what would be required for fixing bugs seen at installation time that don't have workarounds), this bug has been closed. For more information and suggestions, please see bug 169613 Thanks. |