[ale] Module handling at boot
jeff hubbs
hbbs at mediaone.net
Fri Jan 11 01:47:09 EST 2002
Ken Nagorski wrote:
> Hmm, that was strange. I swear I typed a message...
>
> Anyway. Yes redhat is different from slackware and the fact that you are
> using the ifup command says that it is redhat or some form of.
>
> At anyrate. Do this add this line to your /etc/modules.conf
>
> alias eth0 <module>
>
> That should do it for you.
> Thanks
> Ken
That line is ALREADY in modules.conf; perhaps I should explain. This
machine was originally set up with Red Hat 7.2. I performed an
"express" installation of MOSIX (the clustering extension), which among
other things took a stock tarball of the 2.4.13 kernel source, ran
menuconfig for me, performed a compile and an install, modified
lilo.conf, etc. The problem was, when I went thru menuconfig, I totally
forgot about the Ethernet driver and so, the initialization of eth1
(eth0 is the onboard 10base-T NIC; I've disabled it) fails miserably.
So, what I'm wanting to do is to patch up my mistake and instruct the
compiled (NIC-less) kernel to find and use the right module. If I boot
it up with the previous SMP kernel (this is a dual P/133 box), the NIC
works normally.
At the moment, modules.conf looks like this:
alias parport_lowlevel parport_pc
alias scsi_hostadapter aic7xxx
alias eth0 pcnet32
alias eth1 8139too
"locate 8139too" produces (leaving out results from /usr/src which I
assume are not read by anything at boot time):
/lib/modules/2.4.7-10smp/kernel/drivers/net/8139too.o
/lib/modules/2.4.7-10/kernel/drivers/net/8139too.o
/lib/modules/2.4.13/kernel/drivers/net/8139too.o
(Note - at RH7.2 install time, a dual-CPU mobo was duly sensed and the
installer placed both a multiprocessor kernel and a uniprocessor kernel
in place and selectable by LILO- that's why there are two 2.4.7 entries;
note that one says "2.4.7-10smp")
If /lib/modules/<running_kernel>/kernel/drivers/net is where the ".o"
files go, then it doesn't appear to be missing. It just seems as though
somewhere downstream of modules.conf in the whole process, a reference
is not being made.
I could just uninstall MOSIX and start over, but I'd prefer not to have
to go through menuconfig and a compile all over again (although it would
be fun to watch its CPUs squirm).
Thanks,
- Jeff
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
More information about the Ale
mailing list