--- Eben King <eben1@tampabay.rr.com> wrote:
> On Thu, 7 Aug 2003, Robert Eanes wrote:
>
> > I have installed Core linux on an old PC350 with
> Module Support.
> > Everything comes up fine except for the Nic
> module... 8139too.o
> >
> > I get unresolved symbols when trying to insmod it.
>
> What NIC do you have? Are you sure it uses an
> RTL8139? I had one NIC
> (whose suckiness was much higher than average) which
> had "8139" printed on
> the main chip, but was NOT an RTL8139 (or variant).
I'm pretty sure it uses the RealTek chip driver 8139
or a variant... I've read that the older isa cards
could use the ne2000. This is a Belkin card with MPX
EN5038BB written on the chip. I googled on the card
and came up with the 8139too.o driver. So a mix up
with this is definitely possible, but if I compile in
support for 8139 nic chips into the kernel instead of
compile as a module then it works fine.
>
> I don't remember what type of card it was (it has
> since been replaced),
> but I apparently had to use the "fealnx" driver with
> it.
>
I'll look into this one... who knows, it may work
better than this one.
> > Does anyone know if module 8139too.o has
> dependencies that are not
> > declared in the documentation?
>
> When compiling it, run "make dep" before you compile
> it. That, and
> loading it with "modprobe" (not "insmod") should
> take care of any
> dependencies. Besides, once you ascertain that it
> works, you should never
> have to load it by hand.
>
I issued the following commands to compile the kernel
and modules:
make mrproper && make menuconfig
make dep && make bzImage
make modules && make modules_install
in this order, everything appears fine.. the compile
runs great and finishes as expected. I moved the
System.map ant bzImage over. Modified the startup
scripts ( I could be missing something here, because I
didn't have any modules running in lsmod when I
brought the system up ) Any advice in this area would
help :). The modules are where Linux Documentation
says they should be...
lib/modules/2.4.18xxx/net/drivers.. it's from memory
so pardon the inaccuracies.
In any case, I would like to know if I'm missing
something simple in this whole process, and to know
why the module gets these unresolved symbolic
references... assuming it is the correct driver.
Thanks
Rob
> --
> -eben ebQenW1@EtaRmpTabYayU.rIr.OcoPm
> home.tampabay.rr.com/hactar
>
> rm -f /bin/laden
>
>
>
-----------------------------------------------------------------------
> This list is provided as an unmoderated internet
> service by Networked
> Knowledge Systems (NKS). Views and opinions
> expressed in messages
> posted are those of the author and do not
> necessarily reflect the
> official policy or position of NKS or any of its
employees.
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:15:14 EDT