From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Need new modutils aliases for 2.4.0? (Was) Re: Cannot hotplug cardbus cards.
Date: Tue, 23 Jan 2001 00:33:42 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98021018610942@msgid-missing> (raw)
Andrew Morton wrote:
> Miles Lane wrote:
>
>> ...
>> Jan 22 12:55:30 agate cardmgr[444]: module
>> /lib/modules/2.4.1-pre9/pcmcia/3c575_cb.o not available
>
>
> The hotplug command is doing the right thing - it's
> trying to load 3c575_cb.o. But you're using 3c59x.o
> under 2.4.
>
> I think you need an `alias eth0 3c59x' in modules.conf.
I'll try that. Is this something that modutils should
be doing? I kinda think it is. Basically, we'd need
aliasing of any pcmcia-cs drivers whose function is now
served by a new driver in the 2.4.0 kernel tree.
BTW: I would *really* like to see someone championing
creating a smooth transition path for pcmcia-cs users.
This means getting all the usermode stuff in place for
removing drivers (thanks, David) and also building a
way to prepare a PCMCIA/Cardbus card for removal.
I guess the tough part, here, is the PCMCIA support.
Which, I gather, isn't really there in the 2.4.0
kernel code, yet. Is that correct?
Thanks,
Miles
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-01-23 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 0:33 Miles Lane [this message]
2001-01-23 0:52 ` Need new modutils aliases for 2.4.0? (Was) Re: Cannot hotplug cardbus cards Miles Lane
2001-01-23 1:14 ` Bill Nottingham
2001-01-23 3:39 ` David Hinds
2001-01-26 16:44 ` Need new modutils aliases for 2.4.0? (Was) David Brownell
-- strict thread matches above, loose matches on Subject: below --
2001-01-23 0:47 Need new modutils aliases for 2.4.0? (Was) Re: Cannot hotplug cardbus cards Keith Owens
2001-01-23 0:59 ` Miles Lane
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=marc-linux-hotplug-98021018610942@msgid-missing \
--to=miles@megapathdsl.net \
--cc=linux-hotplug@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.