Bug 80313 - start order between network and PCMCIA
start order between network and PCMCIA
Status: CLOSED DUPLICATE of bug 51322
Product: Red Hat Linux
Classification: Retired
Component: SysVinit (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-24 05:51 EST by Raphael Jacquot
Modified: 2014-03-16 22:33 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:50:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Raphael Jacquot 2002-12-24 05:51:01 EST
Description of problem:
The PCMCIA subsystem is started after the Network subsystem. This is non
practical if the only network card in the system is a pcmcia adapter.
Starting the two subsystems in that order poses a number of problems such as
delaying network interface initialization (which is a minor delay) to blocking
the machine several dozens of seconds (minutes ?) when using PPPOE to connect
for instance to a DSL provider, as the PPP process is trying to hook onto the
ethernet adapter which hasn't been started yet.

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


How reproducible:
always

Steps to Reproduce:
0. use a pcmcia network adapter
1. set up a DSL provider
2. boot the machine
3. hang when trying to launch PPPOE while the ethernet adapter is not even loaded
    
Actual results:
hangs the boot process for a while until if finally times out, not finding a
connection

Expected results:
should start the pcmcia so that the adapter is loaded, then start the network,
and all would be well

Additional info:
Comment 1 Bill Nottingham 2002-12-24 16:12:20 EST

*** This bug has been marked as a duplicate of 51322 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:50:32 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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