On Fri, May 03, 2002 at 10:29:24AM -0700, Andrew Agno wrote:
> > I suspect my problems are unique to the modules I'm using:
> >
> > i82365: The i82365 module depends on isa-pnp. If the
> >
> > orinoco: It's not possible to build orinoco modules into the
>
> I use both the i82365 and the orinoco driver, and it works fine.
> Doing an lsmod shows:
> orinoco_cs
> orinoco
> hermes
> ds
> i82365
> pcmcia_core
It appears that when using modules from the kernel image with a
PCMCIA controller that's on the ISA bus, you have to build
isa-pnp into the kernel rather than building it as a module.
Or, I assume you could preload isa-pnp it at boot time by
listing it in /etc/modules. Building it into the kernel
probably takes less disk space.
You must either have isa-pnp built into the kernel or your
PCMCIA bridge chip is on a PCI bus. I suspect the latter.
Thanks for the help.
For the archives:
The fundamental problem is that /etc/init.d/pcmcia tries to
figure out if you're using pcmcia-modules. It guesses wrongly
on Debian systems. That causes it to use insmod in order to
try to override the normal search path used by modprobe. Then,
if any of pcmcia_core, ds, or PCMCIA-chip-driver (i82365)
modules depend on other modules, it breaks.
Here's a summary of the solutions I've found
Using modules from kernel-image:
Don't use PCMCIA controllers on an ISA bus[*]
or
Build isa-pnp into the kernel or preload it in /etc/modules[*]
or
Delete /lib/modules/<version>/pcmcia
Using modules from pcmcia-modules:
(all steps required)
Build kernel-image/pcmcia-modules with orinoco support
then
Install kernel-image
then
Delete all of the wireless modules [otherwise you'll get version conflicts]
then
Install pcmcia-modules
[*] The only solutions that won't be broken by a upgrade
--
Grant Edwards
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
