All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Matt Reppert <repp0017@tc.umn.edu>
Cc: Pedro Ribeiro <deadheart@netcabo.pt>, linux-kernel@vger.kernel.org
Subject: Re: Problem with mii-tool && 2.6.0-test1-ac2
Date: Sat, 19 Jul 2003 23:57:57 -0400	[thread overview]
Message-ID: <3F1A1345.7080301@pobox.com> (raw)
In-Reply-To: <20030719232804.08cc3689.repp0017@tc.umn.edu>

Matt Reppert wrote:
> On Sat, 19 Jul 2003 19:22:30 +0100
> Pedro Ribeiro <deadheart@netcabo.pt> wrote:
> 
> 
>>If I compile the 8139 ethernet support as a module (as I always did - 
>>module name >> 8130too) I will get an error in make modules_install. 
>>However, if I build it in the kernel it will work just fine. The problem 
>>is that now when I try to do a simple mii-tool -F 100baseTX-FD eth0 
>>(because my eth always stats at 100 Half duplex) I get this error:
>>
>>SIOCGMIIPHY on 'eth0' failed: Operation not supported
> 
> 
> What's the error you get on install? I don't have a problem doing it on
> my iBook.
> 
> You have to explicitly turn on MII support in 2.6-test; the kconfig option
> is CONFIG_MII; it's "Generic Media Independent Interface device support",
> the first item under "Ethernet (10 or 100Mbit)". This needs to be modular or
> on to use mii-tool, I imagine.


No, CONFIG_MII only occasionally affects mii-tool support.  Further, 
CONFIG_MII is forced on if it is needed.

As I explained in another mail, older mii-tool binaries use the 
traditional -- but non-standard -- ioctls for the MII operations.  Newer 
versions of mii-tool use the proper SIOC[GS]MIIxxx ioctls.

The proper fix is to obtain the latest version of mii-tool, possibly 
from net-utils cvs if nowhere else.

	Jeff




      reply	other threads:[~2003-07-20  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19 18:22 Problem with mii-tool && 2.6.0-test1-ac2 Pedro Ribeiro
2003-07-20  3:28 ` Matt Reppert
2003-07-20  3:57   ` 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=3F1A1345.7080301@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=deadheart@netcabo.pt \
    --cc=linux-kernel@vger.kernel.org \
    --cc=repp0017@tc.umn.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.