Bug 52511 - bootnet install hangs (natsemi driver problem?)
bootnet install hangs (natsemi driver problem?)
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-24 11:18 EDT by Gene Czarcinski
Modified: 2007-04-18 12:36 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-29 16:15:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
lspci (873 bytes, text/plain)
2001-08-24 16:08 EDT, Gene Czarcinski
no flags Details
lspci -v (2.80 KB, text/plain)
2001-08-24 16:08 EDT, Gene Czarcinski
no flags Details
lspci -vn (2.45 KB, text/plain)
2001-08-24 16:08 EDT, Gene Czarcinski
no flags Details

  None (edit)
Description Gene Czarcinski 2001-08-24 11:18:26 EDT
Description of Problem:
Doing an nfs install hangs if NIC driver needed by "dd" not specified

Version-Release number of selected component (if applicable):


How Reproducible:
everytime I tried

Steps to Reproduce:
1. boot bootnet floppy
2. have a NIC which needs drivers disk but don't specify dd
3. 

Actual Results:
install hangs when to tries to get anaconda

Expected Results:
error message about missing driver

better still, prompt for driver disk

Additional Information:
Comment 1 Glen Foster 2001-08-24 11:51:03 EDT
This defect is considered MUST-FIX for Fairfax.
Comment 2 Matt Wilson 2001-08-24 14:27:40 EDT
what hardware?
Comment 3 Gene Czarcinski 2001-08-24 14:34:27 EDT
Netgear card with National Semiconductor Corporation DP83815 (MacPhyter)
Ethernet Controller (natsemi driver).

This is on the driver disk.
Comment 4 Jeremy Katz 2001-08-24 15:04:50 EDT
natsemi should be on bootnet as of RC1.  What is this card's pci id?
Comment 5 Gene Czarcinski 2001-08-24 16:07:31 EDT
OK, I knew I should of attached lpci for this and was just lazy.

Attaches follow.
Comment 6 Gene Czarcinski 2001-08-24 16:08:10 EDT
Created attachment 29414 [details]
lspci
Comment 7 Gene Czarcinski 2001-08-24 16:08:34 EDT
Created attachment 29415 [details]
lspci -v
Comment 8 Gene Czarcinski 2001-08-24 16:08:55 EDT
Created attachment 29416 [details]
lspci -vn
Comment 9 Gene Czarcinski 2001-08-28 03:16:42 EDT
I believe that it will happen with any system with a NIC that needs the driver
disk!
Comment 10 Jeremy Katz 2001-08-28 17:49:04 EDT
But natsemi's not on the driver disk for rc1...  trying to find the card which
is floating around the office here to take a better look at it.

If you're saying this happens with "any" -- do you have any other examples?
Comment 11 Jeremy Katz 2001-08-29 16:15:29 EDT
okay, natsemi seems to be kind of busted for me too... reassigning to kernel
Comment 12 Arjan van de Ven 2001-09-04 15:25:57 EDT
Natsemi driver reverted to the 7.1 one; that should fix all these issues.

Note You need to log in before you can comment on or make changes to this bug.