mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benny Amorsen <benny+usenet@amorsen.dk>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
	David Dillow <dave@thedillows.org>,
	linux-kernel@vger.kernel.org,
	Edward Hsu <edward_hsu@realtek.com.tw>
Subject: Re: Realtek 8168D: no active link (2.6.29.2)
Date: Thu, 28 May 2009 10:40:34 +0200	[thread overview]
Message-ID: <1243500034.25386.5.camel@ursa.amorsen.dk> (raw)
In-Reply-To: <200905280009.n4S094jJ032395@turbo.physics.adelaide.edu.au>

tor, 28 05 2009 kl. 09:39 +0930, skrev Jonathan Woithe:

> I'm not surprised one way or the other since I have no idea what to expect
> when doing these tests on this card with the patches applied.  Given that
> ethtool has a "duplex" option I naively thought that it controlled the
> card's duplex setting.

It does. The card is set to full duplex when you force full duplex.

> I interprete your comment to mean that duplex can't
> be controlled like this and it requires autonegotiation in order to active
> full duplex mode.  If that's the case then so be it - I'm only reporting
> what I did and what effect it had on the card.

No, you're reporting which effect it had on the SWITCH. The switch
detected that autonegotiation failed, so it picked half duplex mode.
Card full duplex, switch half duplex, recipe for disaster.

> FYI, turning off autonegotiation was the only way I had of forcing the
> card's speed.  If autoneg was left on the "speed 10" and "speed 100" options
> made no difference - the card would always configure for 1000 Mbps.

Correct. If you want to influence autonegotiation, you need to do
something like:

ethtool -s eth1 advertise 0x00F

This allows 10Mbps and 100Mbps with half or full duplex, but nothing
faster.

> Furthermore, in order to attain 1000 Mbps it was necessary to turn autoneg
> on - with it off, "speed 1000" would result in 100 Mbps only.  However, I
> seem to recall reading somewhere that 1000 Mbps required autoneg so I'm not
> all that surprised with that observation.

That is correct.

I can recommend man ethtool.


/Benny


  reply	other threads:[~2009-05-28  8:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-09 14:03 Jonathan Woithe
2009-05-13 22:04 ` Francois Romieu
2009-05-14 11:49   ` Jonathan Woithe
2009-05-14 12:08   ` Jonathan Woithe
2009-05-14 17:45     ` David Dillow
2009-05-14 23:22       ` Jonathan Woithe
2009-05-17 21:57         ` Francois Romieu
2009-05-17 22:22           ` David Dillow
2009-05-18  0:17           ` Jonathan Woithe
2009-05-18 22:17             ` Francois Romieu
2009-05-18 23:43               ` Jonathan Woithe
2009-05-19 21:32                 ` Francois Romieu
2009-05-22  7:18                   ` Jonathan Woithe
2009-05-25 10:14                   ` Jonathan Woithe
2009-05-27 12:27                     ` Benny Amorsen
2009-05-28  0:09                       ` Jonathan Woithe
2009-05-28  8:40                         ` Benny Amorsen [this message]
2009-05-28 13:15                           ` Jonathan Woithe
2009-05-18 12:39           ` Jonathan Woithe

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=1243500034.25386.5.camel@ursa.amorsen.dk \
    --to=benny+usenet@amorsen.dk \
    --cc=dave@thedillows.org \
    --cc=edward_hsu@realtek.com.tw \
    --cc=jwoithe@physics.adelaide.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /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

all inboxes | Powered by JetHome®