SOLVED: pcmcia service start problem

[Gregory K. Ruiz-Ade]

On Friday 16 January 2004 11:13 am, Joshua Penix wrote:
> Reading that script gave me my clue - it seems that the pcmcia script
> will look in one of *two* places for its modules:
>
> 1) /lib/modules/`uname -r`/pcmcia
> 2) /lib/modules/`uname-r`/kernel/drivers/pcmcia
>
> There's a bash 'if' structure which interestingly has the bug you refer
> to only if it follows path #1, but not path #2.  In a default Fedora
> install, path #2 is where the modules are found, and the #1 directory is
> nonexistant, so the bug is never triggered.  Upon installing the wlan-ng
> drivers from source, they create the #1 directory and the script winds
> up switching to look there, at which point it executes the buggy
> modprobe statements and throws the error.

I'd like to point out that I have not run into _any_ of these problems, 
primarily because of what I had to do to get pcmcia (let alone wireless) 
working on my laptop.  I had to completely disable pcmcia in the kernel 
(custom compile, only change being disabling pcmcia) and install from 
pcmcia-cs sources.

those worked just fine. :)

linux-wlan-ng apparently is geared to install against the same paths that 
pcmcia-cs installs to from sources.

So, for me, it all "just worked".

Gregory

-- 
Gregory K. Ruiz-Ade <gkade at bigbrother.net>
OpenPGP Key ID: EAF4844B  keyserver: pgpkeys.mit.edu