From: dhinds <dhinds@sonic.net>
To: Andreas Roedl <flood@flood-net.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pcmcia problems with IDE & cardbus
Date: Wed, 27 Feb 2002 12:57:36 -0800 [thread overview]
Message-ID: <20020227125736.A1502@sonic.net> (raw)
In-Reply-To: <20020227111008.A13182@sonic.net> <20020227204649.92C08AA40@flood-net.de>
In-Reply-To: <20020227204649.92C08AA40@flood-net.de>
On Wed, Feb 27, 2002 at 09:49:51PM +0100, Andreas Roedl wrote:
>
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: unresolved symbol dldwd_proc_dev_init
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: unresolved symbol dldwd_setup
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: unresolved symbol dldwd_shutdown
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: unresolved symbol
> dldwd_proc_dev_cleanup
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: unresolved symbol dldwd_reset
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: unresolved symbol dldwd_interrupt
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: insmod
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o failed
> /lib/modules/2.4.18/pcmcia/orinoco_cs.o: insmod orinoco_cs failed
>
> ?
Did you read my explanation?
You've somehow ended up loading the hermes module from the 2.4.18
kernel tree, and the orinoco_cs module from the pcmcia-cs package.
"modprobe" is probably getting confused by having several modules with
the same names, in different directories.
If you use just the pcmcia-cs modules, (or just the kernel modules),
then everything should work fine on 2.4.18.
-- Dave
next prev parent reply other threads:[~2002-02-27 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 19:10 pcmcia problems with IDE & cardbus dhinds
2002-02-27 20:49 ` Andreas Roedl
2002-02-27 20:57 ` dhinds [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 19:15 dhinds
2002-02-27 0:26 Herbert Rosmanith
2002-02-27 1:50 ` Andreas Roedl
2002-02-27 18:23 ` Gunther Mayer
2002-02-27 18:21 ` Andre Hedrick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020227125736.A1502@sonic.net \
--to=dhinds@sonic.net \
--cc=flood@flood-net.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.