PCMCIA does not start on bootup. Receiving cannot find pcmcia_core.o, yenta_socket.o and ds.o. However after logging in and running modprobe pcmcia_core modprobe yenta_socket and modprobe ds then executing service pcmcia start. Pcmcia load but the card is not recognized and initialized. Starting Redhat-config-network and closing, then reinserting the pcmcia network card allows it to get detected and initialized. Any ideas?

I've had a similar problem and just solved it my way...

modprobe normally uses just the name of the modules without the full path and .o extension. Seems like the .o was provided.

If you look into boot scripts (/etc/rc.d/init.d/pcmcia) there is logic like this:

if [ -d /lib/modules/preferred ] ; then
PC=/lib/modules/preferred/pcmcia
else
PC=/lib/modules/`uname -r`/pcmcia
fi
KD=/lib/modules/`uname -r`/kernel/drivers/pcmcia
if [ -d $PC ] ; then
echo -n " modules"
/sbin/modprobe pcmcia_core.o $CORE_OPTS
/sbin/modprobe $PCIC.o $PCIC_OPTS
/sbin/modprobe ds.o
elif [ -d $KD ] ; then
/sbin/modprobe pcmcia_core
/sbin/modprobe $PCIC
/sbin/modprobe ds
else
echo $" module directory $PC not found."
break
fi

So, if you have a /lib/modules/`uname -r`/pcmcia dir, modprobe will load modules with .o extension. The dir just contains the links to real modules, so it is somewhat safe to remove it (I just renamed it to pcmcia.orig so the script does not see it).

Aleks