Bug 52016

Summary: natsemi NIC not recognized
Product: [Retired] Red Hat Linux Reporter: Gene Czarcinski <gczarcinski>
Component: anacondaAssignee: 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:
Description Flags
lspci -v none

Description Gene Czarcinski 2001-08-18 21:17:31 UTC
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.

Comment 1 Bill Nottingham 2001-08-19 05:16:44 UTC
lspci -v output?

Comment 2 Gene Czarcinski 2001-08-19 09:49:50 UTC
The problem seems to occur with any NIC which needs the driver disk (e.g.,
pcnet32 also).

Comment 3 Gene Czarcinski 2001-08-19 09:50:34 UTC
Created attachment 28404 [details]
lspci -v

Comment 4 Glen Foster 2001-08-20 19:24:29 UTC
This defect is considered SHOULD-FIX for Fairfax.

Comment 5 Jeremy Katz 2001-08-29 19:28:16 UTC
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...)