i had the same problem, and here's what fixed it for me. normally, at boot time, PCMCIA is started by running "/etc/init.d/pcmcia start" -- no big surprise there. so i was more than a bit confused when it wasn't starting for me. however, take a look at the lines in that script around line 100 and after: 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 $CORE_OPTS /sbin/modprobe $PCIC $PCIC_OPTS /sbin/modprobe ds elif [ -d $KD ] ; then /sbin/modprobe pcmcia_core /sbin/modprobe $PCIC /sbin/modprobe ds else echo $" module directory $PC not found." break fi note that the script is looking to set two variables to the names of two possible PCMCIA module directories: PC or KD. if it finds the module directory /lib/modules/.../pcmcia, it runs the first set of modprobe's. however (and i've already fixed this), the original module names in those first three lines ended with ".o", which modprobe doesn't handle. all i did was remove the ".o" suffixes. everything worked. it's unclear when you should have a /lib/modules/.../pcmcia directory and when you shouldn't. but i just fixed the script and left it at that. can anyone else check this out, and let me know the result? rday
