Bug 59531 - Start Up freezes
Summary: Start Up freezes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kudzu
Version: 7.2
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-09 19:42 UTC by Need Real Name
Modified: 2014-03-17 02:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-03-13 23:40:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2002-02-09 19:42:26 UTC
Description of Problem: After the install, the start up freezes on "checking 
for new hardware".  This is caused because it can not recognize the ethernet 
card.  Tried to re-install the ifconfig package but that did not work even 
after intall.  Won't even loop back when trying to send info.  


Version-Release number of selected component (if applicable): Ethernet card-
Netgear FA311


How Reproducible: Tyan System board with a 750mhz AMD processor.  Netgear 
FA311 ethernet card. System running Grub. C: drive running Windows XP(works 
fine) and D: running Red Hat 7.2. (does not even start up but will if you 
don't allow it to look for the ethernet card). Cable modem is also running.


Steps to Reproduce:
1.Install Linux
2.Start Up
3.Stalls on 'Checking for new hardware'

Actual Results:check above


Expected Results: To get the ethernet card loaded properly because this is a 
very popular ethernet card and to get this machine online.


Additional Information: Please email me asap with a fix to this.

Comment 1 Bernhard Rosenkraenzer 2002-02-20 11:41:34 UTC
This has nothing to do with the internet-config package, reassigning to kudzu (which is 
what is running when it says "Checking for new hardware").

Comment 2 Bill Nottingham 2002-03-13 23:40:35 UTC
What happens if you disable the kudzu service, but run 'kudzu -p' after booting?

Comment 3 Bill Nottingham 2002-11-25 21:59:45 UTC
closed, no response


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