From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: kees <kees@schoen.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19.rc3{8139too as module}
Date: Sat, 27 Jul 2002 05:19:04 -0400 [thread overview]
Message-ID: <3D426588.6070704@mandrakesoft.com> (raw)
In-Reply-To: Pine.LNX.4.33.0207271054120.8193-100000@schoen3.schoen.nl
kees wrote:
> Hi
>
> I tried to use 8139too as module, but that failed. 4 mii_...... like
> mii_link_ok() could not be resolved (at load time). As a compiled in
> driver it works ok.
It requires the mii.o module. Use modprobe instead of insmod :)
prev parent reply other threads:[~2002-07-27 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 8:56 2.4.19.rc3{8139too as module} kees
2002-07-27 9:19 ` Jeff Garzik [this message]
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=3D426588.6070704@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kees@schoen.nl \
--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