Red Hat Bugzilla – Bug 22979
RFE: pcmcia interfaces
Last modified: 2014-03-16 22:17:47 EDT
Many people are annoyed by the "Bringing up interface eth0: [Failed]" on
pcmcia cards (since pcmcia is started after network). For some reasons
don't really understand) redhat does not want to change this ordering.
propose a simple fix for this problem below. With this small patch you just
"PCMCIA=yes" into ifcfg-eth? if it is a PCMCIA device and the network
only bring it up if pcmcia is already started.
--- network.orig Fri Dec 29 12:08:04 2000
+++ network Fri Dec 29 12:18:27 2000
@@ -58,10 +58,12 @@
for i in $interfaces; do
- if egrep -L "^ONBOOT=\"?[Nn][Oo]\"?" ifcfg-$i >/dev/null
+ if egrep -q "^ONBOOT=\"?[Nn][Oo]\"?" ifcfg-$i; then
# Probe module to preserve interface ordering
/sbin/ifconfig $i >/dev/null 2>&1
+ egrep -q "^PCMCIA=\"?[Yy][Ee][Ss]\"?" ifcfg-$i &&\
+ [ ! -f /var/lock/subsys/pcmcia ] &&
action "Bringing up interface $i: " ./ifup $i boot
We can do this, but it won't help much unless the installer writes them.
There's no real way to know what driver arbitrary eth devices are controlled
by. The installer only knows that "there is an eth0 device" not that it is
controlled via PCMCIA.
Not actually true -- as long as they use the pcmcia install disks, the loader
keeps track of what's pcmcia and what isn't.
For 7.0, we set ONBOOT=no for PCMCIA devices to work around this though, iirc.
Is that not working?
This defect is considered MUST-FIX for Florence Gold release
Reporter: does setting 'ONBOOT=no' also solve your problem? (It won't
break anything; pcmcia-cs ignores ONBOOT...
Setting ONBOOT=no would also solve the problem, but I don't think its a clean
In fact, I think inserting a card could be considered "booting" it and hence
should bring the if up with the "boot" option. This way the user could control
card should be brought up upon insertion.
That would have to be done in the pcmcia package.
However, please note that the way the cards are currently configured,
you will *not* get this message.
After discussing this with the local pcmcia-cs maintainer, doing it
in this manner (suddenly honoring ONBOOT for pcmcia devices) would
totally break upgrades. So we're going to stick with the current
behavior for now.
Yes, I don't get the failed message anymore. But know the card isn't brought up
laptop wakes up from suspend;-(
Setting ONBOOT="no" has the effect of breaking apm suspend/resume, since
"service network start" will NOT bring up a pcmcia interface in this case.
See bug #34632.
Which card ?
This should be worked around in initscripts-6.12-1, in that the message is no
longer printed (the interface is just skipped...)