> >Hi,
> >Curious question:
> >I compiled enet driver as loadable module on Redhat v4.2. Why isn't the
> >module loaded
> >automatically when I boot linux with "ether=10,0x300,eth0"? I had to
> >add "modprobe -t net \*"
> >in rc2.d manually to bring it up. Is it supposed to be that way?
> >Also, where are the parameters (int 10, IO 0x310, dev eth0) kept ?
> >Thanks.
> >-Fred
> >Systematic Network, Inc.
> Did you also include support for autoloading modules ? If not, then
> all modules have to be loaded manually. If you did include
> autoloading support, then the module won't load until it's needed - if
> there is network traffic, for example. But if you want it to load at
> boot time, why not just compile it into the kernel, instead of as a
> module ?
I used to check the network card setup at boot time, but that gets
to be rather long and Microsoft-oriented. :) Just boot it the normal
way, without args, and make sure that your /etc/conf.modules has the
appropriate lines to load the module. (I'm assuming your kernel does
autoloading.)
It should look something like this:
alias etho ne
options ne io=0x330 irq=10
Then when you want to try it you can load the modules manually or
use (what I remember to be) depmod -a. I can't quite remember that for
some reason; check the man pages.
It'd also be a good idea to search DejaNews.com for this kind of
problem; this is the third message I've answered about this same thing
this week. With DejaNews you won't have to wait for a response, and you
get several different views on the subject.
Brian
--------------------------------------------------------------------------------
Brian Fahrlander Problem Solver, Technomad, and
Linux-head
Evansville, IN
ICQ:5119262
http://www.kamakiriad.com
--------------------------------------------------------------------------------
Whitewater isn't over until the First Lady sings.