Red Hat Bugzilla – Bug 88054
typoes in /etc/init.d/pcmcia startup script
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: lines 107-9 in /etc/init.d/pcmcia script, set of modprobe commands, have arguments that end with ".o". this is not possible -- modprobe only takes the module name, not the file name. this will cause loading of any newly-built kernels to fail to load the pcmcia modules. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. build a new kernel with pcmcia functionality 2. boot to new kernel 3. Actual Results: pcmcia modules are not loaded Expected Results: pcmcia modules should load Additional info: just get rid of the ".o" suffixes
Maybe that is why there is a bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=81282
Here's where the directory that fools the /etc/init.d/pcmcia script comes from. A quick fix: After you build a new kernel and reboot- type "rm -rf /lib/modules/`uname -r`/pcmcia" this directory is just full of symlinks. /usr/src/linux-2.4/Makefile: ------------------ # Backwards compatibilty symlinks for people still using old versions # of pcmcia-cs with hard coded pathnames on insmod. Remove # _modinst_post_pcmcia for kernel 2.4.1. .PHONY: _modinst_post_pcmcia _modinst_post_pcmcia: cd $(MODLIB); \ mkdir -p pcmcia; \ find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
*** Bug 112333 has been marked as a duplicate of this bug. ***
This appears to be a duplicate of Bug 81282 -- which is closed.
Latest update of kernel-pcmcia-cs-3.1.31-16 for Fedora core has the 3 ".o"s removed. This bug can be closed
pcmcia-cs-3.2.7-1.5 still has .o extensions in these lines: /sbin/insmod $PC/pcmcia_core.o $CORE_OPTS /sbin/insmod $PC/$PCIC.o $PCIC_OPTS /sbin/insmod $PC/ds.o
That's with insmod, which takes full pathnames. *** This bug has been marked as a duplicate of 81282 ***
*** Bug 97751 has been marked as a duplicate of this bug. ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.