Bug 52016 - natsemi NIC not recognized
Summary: natsemi NIC not recognized
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-18 21:17 UTC by Gene Czarcinski
Modified: 2007-04-18 16:36 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-08-27 22:34:19 UTC
Embargoed:

Attachments (Terms of Use)
lspci -v (2.80 KB, text/plain)
2001-08-19 09:50 UTC, Gene Czarcinski 		no flags Details
View All

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...)
Note You need to log in before you can comment on or make changes to this bug.