From: "Chava Leviatan" <chavale@actcom.net.il>
To: <linux-kernel@vger.kernel.org>
Subject: Ethernet driver module compilation (8139too)
Date: Mon, 29 May 2006 11:05:58 +0200 [thread overview]
Message-ID: <003101c682ff$1b7c7350$c400a8c0@Chavalaptop> (raw)
Hello,
My Linux 2.4.18 machine has 2 ethernet interfaces: eepro100 and 8139too.
I need to put a minur changes (printk messages) into those drivers, which
are loaded as kernel modules .
I first changed the eepro then compiled it seperatly (with
_DMODULE, -D__KERNEL and the correct path into
/lib/modules/.....) and everything worked well (was able to see my printing
through dmesg).
When I tried to change 8139too, it did not work -- not because of the code
change -- rather , I had some
problems in compiling this module.
When i rebooted the machine the interfaces wer not up, and when I did lsmod
8139too was not there.
I then tried to manually install it (insmod) and was promp with unresolved
external. I found out that
those unresolved belong to mii.o which was not loaded during the boot
process.
When I changed to the original 8139too.o (luckily I have saved it ...) the
machine is ok, mii.o
is loadede , and also 8139too.
I am sure the problem is in the way I compile this module , but i don't know
what is missing ?
I have browsed many Makefiles and could not tell what flags make the
8139too.o tell the boot that
it needs mii.o . The modules.dep file create during boot tme shows that
8139too depends on mii.o,
but from some reason mii.o is ot loaded.
Maybe I can not compile kernel modules seperatly, i.e., kernel modules that
are loaded during bot time ?
Obviosly i can do this procee manually: insmod mii, then 8139 and finally
bring the interface up.
But, i really need to know what went wrong there
Any help will be much appreciated
Chava Leviatan
next reply other threads:[~2006-05-29 8:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 9:05 Chava Leviatan [this message]
2006-05-29 8:13 ` Ethernet driver module compilation (8139too) Brian F. G. Bidulock
2006-05-29 10:27 ` Chava Leviatan
2006-05-29 9:53 ` Brian F. G. Bidulock
2006-05-29 11:34 ` Chava Leviatan
2006-05-29 12:24 ` David Woodhouse
2006-05-29 12:34 ` test Suresh G
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='003101c682ff$1b7c7350$c400a8c0@Chavalaptop' \
--to=chavale@actcom.net.il \
--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;
as well as URLs for NNTP newsgroup(s).