Bug 125250
| Summary: | pcmcia should be invoked before networking in /etc/rcX.d | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bugzkilla <linuxveteran> |
| Component: | pcmcia-cs | Assignee: | Pete Zaitcev <zaitcev> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2 | CC: | ed, mattdm, nikolayds, steph, uckelman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-04-26 18:21:05 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Bugzkilla
2004-06-04 03:01:40 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. This is been a bug on FC1, RH 9 and RH 8 too. *** Bug 131193 has been marked as a duplicate of this bug. *** *** Bug 44177 has been marked as a duplicate of this bug. *** *** Bug 72969 has been marked as a duplicate of this bug. *** 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. 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. It is fine in Fedora Core 3 now. |