Bug 18191
Summary: | NET install with driver disk won't find SCSI disks | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Alexandre Oliva <aoliva> |
Component: | anaconda | Assignee: | Brock Organ <borgan> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | dark.lite, dr, roch |
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: | 2000-12-08 19:54:05 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
Alexandre Oliva
2000-10-03 07:37:59 UTC
What is your network card? I had the same problem. I was doing an NFS install. I have an IDE-CDROM and a SCSI HD. The Installer would forget to load my SCSI driver. My network card (SMC EtherPower II) uses the epic100 driver from the driver disk. My SCSI controller (Tekram DC-390U2W, symbios 53c895 chipset) uses the ncr53c8xx (or the sym53c8xx) driver, also from the driver disk. I tried various combinations of "expert" and "dd" on the bootdisk's "pre-boot command-line" and using F2 to load the driver disk. My network card driver loaded fine everytime, but I could never find my SCSI driver. I also tried using the updates disk. It didn't help me with this problem. I simply did C-A-F2 and loaded the sym53c8xx driver manually with modprobe. This worked okay for the install, but no initrd was created to load my SCSI driver on my HD nor the Installer created bootdisk. QA needs to be able to reproduce this issue. What hardware do you have in your system so we can attempt to duplicate? verified this issue ... thanks for the report! This bug is fixed internally. You found a perfectly adequate workaround, and this bug won't be in the next release. Thanks for the report. Verified this as resolved. |