[realtek] /etc/modules.conf

[Juan Fco Rodriguez Hervella]

Hi:

I have do the following:

1. cd /lib/modules/kernel/drivers/net
2. ln -s 8139too.o rtl8139.o
3. reboot with 2.4.2
4. cd /lib/modules/kernel/drivers/net
5. insmod rtl8139.o
6. depmod -a 2.4.2

And it seems that all is OK. I can load the driver without 
modifier anything except the link...

What is your opinion ?? is it bad to have a link to 8139too.o ??

"Kenneth J. Hendrickson" wrote:
> 
> On Mon, Apr 23, 2001 at 09:11:31PM +0200, Juan Fco Rodriguez Hervella wrote:
> > I have in /etc/modules.conf:
> >
> > alias eth0 rtl8139
> > alias eth1 rtl8139
> > alias eth2 rtl8139
> >
> > And all is OK with 2.2, but when I reboot with 2.4,
> > the kernel dont load the 8139too.o module.
> >
> > I suppose that I have to modified the previous lines in
> > /etc/modules.conf,
> > but I does *not* want to have the same problem with kernel 2.2 if I set:
> >
> > alias eth0 8139too
> > alias eth1 8139too
> > alias eth2 8139too
> >
> > It is possible to combine the 2 modules so I can start both kernels
> > automatically ???
> 
> Yes.  You need the "path[net]=PATH" option for /etc/modules.conF
> The reason is that there is a different directory structure for the
> loadable kernel modules (device drivers) in Linux 2.4.
> 
> I can't tell you exactly how to structure your path statement, because
> I don't have access to my systems at home (where I do just this) right
> now.  However, if you study the man page for modules.conf(5), and look
> at the structure of /lib/modules/`uname -r` for both versions of the
> Linux kernel, you'll be able to figure it out.
> 
> If you were running Debian, you wouldn't need to do this, because Debian
> has upgraded versions of depmod(8) and modprobe(8).
> 
> Hope this helps ...
> 
> Ken Hendrickson
> Northrop Grumman

-- 
*********************************
Juan F. Rodriguez Hervella
Universidad Carlos III de Madrid
********************************