Bug 52016
| Summary: | natsemi NIC not recognized | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Gene Czarcinski <gczarcinski> | ||||
| Component: | anaconda | Assignee: | Jeremy Katz <katzj> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 7.3 | ||||||
| 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: | 2001-08-27 22:34:19 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: | |||||||
| Attachments: |
|
||||||
lspci -v output? The problem seems to occur with any NIC which needs the driver disk (e.g., pcnet32 also). Created attachment 28404 [details]
lspci -v
This defect is considered SHOULD-FIX for Fairfax. The driver disk always prompts for which driver you want to use. Note that they were autoloading before because they were on bootnet which does do probing (more on natsemi on 52511 in a minute...) |
Description of Problem: Normally, the install process recognizes that the natsemi NIC driver is needed. This was a network install. When I specified the natsemi driver, everything went OK. Roswell-1 worked OK. Version-Release number of selected component (if applicable): How Reproducible: everytime Steps to Reproduce: 1. do an NFS install specifying that the driver disk ("dd") is needed. 2. 3. Actual Results: had to manually specify the driver Expected Results: auto-recognition Additional Information: Roswell-1 auto-recognized.