netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: androsyn@ratbox.org
Cc: linux-net@vger.kernel.org
Subject: Re: qfe problems on x86
Date: Tue, 23 Apr 2002 03:54:53 -0700 (PDT)	[thread overview]
Message-ID: <20020423.035453.96160070.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0204230714530.7811-100000@simon.ratbox.org>

   From: Aaron Sethman <androsyn@ratbox.org>
   Date: Tue, 23 Apr 2002 07:19:25 -0400 (EDT)

   I'm *certain* this is a switch, albeit a cheap, unmanaged one, I've got
   other devices hanging off of it that are just happy at 100MB/full duplex
   right now. Also I am not forcing it to full duplex, this is what it is
   trying to do on its own.
   
It means it cannot negotiate this with the switch for some reason.

Does trying to force full duplex using 'ethtool' have any
effect?

  reply	other threads:[~2002-04-23 10:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23  5:19 qfe problems on x86 Aaron Sethman
2002-04-23  5:24 ` David S. Miller
2002-04-23 10:47   ` Aaron Sethman
2002-04-23 10:23     ` David S. Miller
2002-04-23 11:04       ` Aaron Sethman
2002-04-23 10:44         ` David S. Miller
2002-04-23 11:19           ` Aaron Sethman
2002-04-23 10:54             ` David S. Miller [this message]
2002-04-23 11:57               ` Aaron Sethman
2002-04-23 11:31                 ` David S. Miller
2002-04-23 12:00                   ` Aaron Sethman
2002-04-23 11:35                     ` David S. Miller
2002-04-23 12:07                       ` Aaron Sethman
2002-04-23 11:43                         ` David S. Miller
2002-04-23 12:11                           ` Aaron Sethman
2002-04-23 11:47                             ` David S. Miller
2002-04-23 12:19                               ` Aaron Sethman
2002-04-23 12:00                                 ` David S. Miller
2002-04-23 12:57                                   ` Aaron Sethman
2002-04-23 12:33                                     ` David S. Miller

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=20020423.035453.96160070.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=androsyn@ratbox.org \
    --cc=linux-net@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).