From: Mark Hounschell <markh@compro.net>
To: Jan Hudec <bulb@ucw.cz>
Cc: kernelnewbies@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Load kernel module automatically
Date: Thu, 06 Jun 2002 09:24:55 -0400 [thread overview]
Message-ID: <3CFF62A7.2AB5B0F1@compro.net> (raw)
In-Reply-To: <3CFD19D1.5768FCF8@compro.net> <20020605194716.4290.qmail@web14906.mail.yahoo.com> <20020606085907.GA28704@artax.karlin.mff.cuni.cz> <3CFF2880.8D697F90@cfl.rr.com> <20020606112234.GA20035@artax.karlin.mff.cuni.cz>
Jan Hudec wrote:
>
> On Thu, Jun 06, 2002 at 05:16:48AM -0400, Mark Hounschell wrote:
> > That isn't the case. There is no /etc/modules file on any Linux box I've
> > ever used. My network driver modules are loaded automatically by the kernel's
> > internal module loader "kmod" because the are set up correctly in /etc/modules.conf.
> >
> > "alias eth0 3c905"
> >
> > ALL device driver modules can be set up to load automatacally by "kmod".
>
> That I didn't know. However, I have a computer with four network cards
> in it. Since they are numbered dynamicaly, loading modules in different
> order results in different numbering of devices. How do I assure that
> upon request for eg. eth2 the loaded module is assigned eth2?
The order in which they are labeled is the order the are found during the pci scan.
The lspci command should tell you which is which. Then place the correct entries in
/etc/modules.conf
alias eth0 3c905
alias eth1 blabla
alias eth2 blablaaaa
.
.
Regards
Mark
next prev parent reply other threads:[~2002-06-06 13:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 19:38 Load kernel module automatically Michael Zhu
2002-06-04 19:46 ` Richard B. Johnson
2002-06-04 19:49 ` Mark Hounschell
2002-06-05 19:47 ` Michael Zhu
2002-06-05 20:07 ` Måns Rullgård
2002-06-06 0:00 ` Keith Owens
2002-06-06 8:59 ` Jan Hudec
2002-06-06 9:16 ` Mark Hounschell
2002-06-06 11:22 ` Jan Hudec
2002-06-06 13:24 ` Mark Hounschell [this message]
2002-06-07 3:42 ` Andrew Rodland
2002-06-04 22:27 ` Jan Hudec
2002-06-04 22:54 ` Austin Gonyou
2002-06-04 23:27 ` Mark Hounschell
2002-06-05 0:11 ` Austin Gonyou
2002-06-05 18:56 ` Eric Kristopher Sandall
2002-06-05 19:03 ` John Tyner
2002-06-05 19:08 ` Eric Kristopher Sandall
2002-06-05 19:41 ` Michael Zhu
2002-06-05 20:25 ` Eric Kristopher Sandall
2002-06-06 13:27 ` Thunder from the hill
2002-06-05 20:57 ` Oliver Wegner
2002-06-05 21:37 ` Richard B. Johnson
2002-06-05 22:23 ` Oliver Wegner
2002-06-05 23:45 ` Alan Cox
2002-06-05 23:12 ` J.A. Magallon
2002-06-05 22:33 ` Oliver Wegner
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 13:29 Thunder from the hill
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=3CFF62A7.2AB5B0F1@compro.net \
--to=markh@compro.net \
--cc=bulb@ucw.cz \
--cc=kernelnewbies@nl.linux.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox