From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1)
Description of problem:
The 2.4.20-13.7 version of the kernel (i686 at least) changed the pcmcia modules
from /lib/modules/<version>/pcmcia (where it was my previous version) to
/lib/modules/<version>/kernel/drivers/pcmcia. As a result the /etc/init.d/pcmcia
script no longer runs since it looks for "/lib/modules/`uname -r`/pcmcia".
The pcmcia script needs to be changed or you need a symlink from
/lib/modules/<version>/kernel/drivers/pcmcia to /lib/modules/<version>/pcmcia
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install the 2.4.20-13.7 kernel
2. run "service pcmcia start" and it dies with an error that
"/lib/modules/2.4.20-13.7/pcmcia could not be found."
Actually, a symlink isn't the correct way to fix it as far as I can tell.
This is what I needed (for my boss's laptop at work) to give me a
/lib/modules/2.4.20-13.7/pcmcia that looked like the one from 2.4.18-27.7.x:
for z in `find ../kernel/drivers -type d -name pcmcia`
ln -s $z/* .
I too experience this problem with the i586 kernel 2.4.20-13.7. For me a
symbolic link /lib/modules/2.4.20-13.7/pcmcia ->
/lib/modules/2.4.20-13.7/kernel/drivers/pcmcia is a valid work around.
Joe Kotran, Lead Systems Administrator
Advanced Technology Laboratories
*** Bug 91446 has been marked as a duplicate of this bug. ***
I downloaded the kernel-source and recompiled it using make oldconfig to use
the default settings and I have the pcmcia drivers in both
/lib/modules/<version>/kernel/drivers/net/pcmcia however it did get my pcmcia
working again. Hope this helps.
I think, the kernel packager dropped /lib/modules/2.4.20-13.7/pcmcia directory
by mistake. Since this is a simple collection of links, I could copy it from
cp -R /lib/modules/2.4.18-27.7.x/pcmcia /lib/modules/2.4.20-13.7/
and it fixed the problem.
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.