All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Domen Puncer <domen@coderock.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3c59x on 2.6.0-test3->test6 slow
Date: Tue, 7 Oct 2003 19:43:40 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0310071349560.19396@montezuma.fsmlabs.com> (raw)
In-Reply-To: <200310070949.31220.domen@coderock.org>

On Tue, 7 Oct 2003, Domen Puncer wrote:

> > What is your link peer?
> 
> Not native english speaker, but if "link peer"  is the remote end, then this is a
> friend's computer. (and a hub is between computers)

Ok in this case it would be the hub, sometimes these aren't the best when 
it comes to advertising capabilities.

> # strace mii-tool eth0
> execve("/sbin/mii-tool", ["mii-tool", "eth0"], [/* 37 vars */]) = 0
> socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
> ioctl(3, 0x89f0, 0x804b460)             = -1 EOPNOTSUPP (Operation not supported)
> write(2, "SIOCGMIIPHY on \'eth0\' failed: Op"..., 54SIOCGMIIPHY on 'eth0' failed: Operation not supported
> ) = 54
> close(3)                                = 0

Could you try updating your mii-tool please.

#define SIOCGMIIREG	0x8948		/* Read MII PHY register.	*/

I'm not sure what your current binary is doing. I have the following 
version;

Name        : net-tools                    Relocations: (not relocateable)
Version     : 1.60                              Vendor: Red Hat, Inc.
Release     : 12                            Build Date: Tue 11 Feb 2003 09:33:32 AM EST
Install Date: Sat 19 Apr 2003 11:57:08 AM EDT      Build Host: tweety.devel.redhat.com
Group       : System Environment/Base       Source RPM: net-tools-1.60-12.src.rpm
Size        : 611073                           License: GPL
Signature   : DSA/SHA1, Mon 24 Feb 2003 01:37:21 AM EST, Key ID 219180cddb42a60e
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Summary     : Basic networking tools.
Description :
The net-tools package contains basic networking tools, including
ifconfig, netstat, route, and others.

  reply	other threads:[~2003-10-07 23:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 13:29 3c59x on 2.6.0-test3->test6 slow Domen Puncer
2003-10-06 21:23 ` Zwane Mwaikambo
2003-10-06 22:33   ` Domen Puncer
2003-10-06 22:43     ` Zwane Mwaikambo
2003-10-06 23:44       ` Domen Puncer
2003-10-07  0:18         ` Zwane Mwaikambo
2003-10-07  4:31           ` Malte Schröder
2003-10-07 11:05             ` Malte Schröder
2003-10-07 12:58               ` Profiling disk usage on selected branches of a file system Stephen Satchell
2003-10-07  7:49           ` 3c59x on 2.6.0-test3->test6 slow Domen Puncer
2003-10-07 23:43             ` Zwane Mwaikambo [this message]
2003-10-08 15:05               ` Domen Puncer
2003-10-09  1:53                 ` Zwane Mwaikambo
2003-10-09  8:49                   ` Domen Puncer
2003-10-09 23:10                     ` Zwane Mwaikambo
2003-10-09 23:55                       ` Domen Puncer
2003-10-13  0:22                         ` Domen Puncer
2003-10-13  0:37                           ` Andrew Morton
2003-10-13  2:28                             ` Domen Puncer
2003-10-13  3:03                               ` Andrew Morton

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=Pine.LNX.4.53.0310071349560.19396@montezuma.fsmlabs.com \
    --to=zwane@arm.linux.org.uk \
    --cc=domen@coderock.org \
    --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 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.