From: David Hinds <dhinds@sonic.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Need new modutils aliases for 2.4.0? (Was) Re: Cannot hotplug cardbus cards.
Date: Tue, 23 Jan 2001 03:39:14 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98022130632315@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98021018610942@msgid-missing>
On Mon, Jan 22, 2001 at 04:52:22PM -0800, Miles Lane wrote:
>
> Adding "alias eth0 3c59x" or "alias /dev/eth0 3c59x"
> or "alias 3c575_cb 3c59x" and then running "depmod -ae"
> before inserting the 3c575 card did not help.
The hotplug script should not need this alias. That's the whole point
of having the PCI ID matching stuff, right? (the driver gets loaded
based on the device ID, not based on a user request for eth0)
> Also, I am questioning whether /sbin/hotplug uses
> cardmgr to get the modules loaded. That means that
> the messages I sent earlier:
/sbin/hotplug and cardmgr do not interact. cardmgr decided to try
loading 3c575_cb based on /etc/pcmcia/config; no hotplug event was
involved.
-- Dave
_______________________________________________
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 prev parent reply other threads:[~2001-01-23 3:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 0:33 Need new modutils aliases for 2.4.0? (Was) Re: Cannot hotplug cardbus cards Miles Lane
2001-01-23 0:52 ` Miles Lane
2001-01-23 1:14 ` Bill Nottingham
2001-01-23 3:39 ` David Hinds [this message]
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-98022130632315@msgid-missing \
--to=dhinds@sonic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).