Bug 125250 - pcmcia should be invoked before networking in /etc/rcX.d
Summary: pcmcia should be invoked before networking in /etc/rcX.d
Alias: None
Product: Fedora
Classification: Fedora
Component: pcmcia-cs
Version: 2
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact:
: 44177 72969 131193 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2004-06-04 03:01 UTC by Bugzkilla
Modified: 2007-11-30 22:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-04-26 18:21:05 UTC

Attachments (Terms of Use)

Description Bugzkilla 2004-06-04 03:01:40 UTC
Description of problem:
network connection fails on bootup on laptops with pcmcia network card

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

How reproducible:

Steps to Reproduce:
1. boot fedora core 2
2. network connection fails because networking gets started before 
Actual results:
network connection down

Expected results:
start pcmcia, then networking

Additional info:

Comment 1 Joel Uckelman 2004-06-05 03:35:43 UTC
Here's what I did to solve this problem:

Change the line 

# chkconfig: 2345 24 96

in /etc/init.d/pcmcia to

# chkconfig: 2345 09 96

And then run:

chkconfig --level 2345 pcmcia reset

network starts at 10, so this makes pcmcia start immediately prior to
it. Changing pcmcia from 24 to 9 seems to have caused no additional
problems for me.

Comment 2 David W. Legg 2004-06-14 14:10:35 UTC
This is been a bug on FC1, RH 9 and RH 8 too.

Comment 3 Bill Nottingham 2004-09-08 06:49:16 UTC
*** Bug 131193 has been marked as a duplicate of this bug. ***

Comment 4 Bill Nottingham 2004-09-08 07:00:56 UTC
*** Bug 44177 has been marked as a duplicate of this bug. ***

Comment 5 Bill Nottingham 2004-09-08 07:01:09 UTC
*** Bug 72969 has been marked as a duplicate of this bug. ***

Comment 6 David Hollis 2004-09-11 20:58:14 UTC
This really isn't a bug.  Set your ifcfg-eth0/1/whatever to ONBOOT=no
for your pcmcia device.  When pcmcia starts, it will discover the
device and start it at that point and everything continues normally.

Comment 7 Matthew Miller 2005-04-26 16:41:20 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.

Comment 8 Nikolay 2005-04-26 17:39:48 UTC
It is fine in Fedora Core 3 now.

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