From: Benny Amorsen <benny+usenet@amorsen.dk>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: romieu@fr.zoreil.com (Francois Romieu),
dave@thedillows.org (David Dillow),
linux-kernel@vger.kernel.org,
edward_hsu@realtek.com.tw (Edward Hsu)
Subject: Re: Realtek 8168D: no active link (2.6.29.2)
Date: Wed, 27 May 2009 14:27:04 +0200 [thread overview]
Message-ID: <m3octeu3xj.fsf@ursa.amorsen.dk> (raw)
In-Reply-To: <200905251014.n4PAEi0k027544@mercury.physics.adelaide.edu.au> (Jonathan Woithe's message of "Mon\, 25 May 2009 19\:44\:44 +0930 \(CST\)")
Jonathan Woithe <jwoithe@physics.adelaide.edu.au> writes:
> ethtool -s eth0 autoneg off speed 10
> - 10 Mbps speed set
>
> ethtool -s eth0 autoneg off speed 100
> - 100 Mbps speed achieved
>
> ethtool -s eth0 autoneg on speed 1000
> - 1000 Mbps speed attained
>
> The duplex setting might not be having an effect though since my switch's
> FDx (full duplex) LED was extinguished for both the 10 and 100 Mbps cases
> above. Explicitly setting the duplex flag using
>
> ethtool -s eth0 autoneg off speed 100 duplex full
>
> didn't make any difference - the FDx LED remained off.
You turned auto negotiation off, and you are surprised that the switch
doesn't autonegotiate full duplex?
/Benny
next prev parent reply other threads:[~2009-05-27 12:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 14:03 Realtek 8168D: no active link (2.6.29.2) 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 [this message]
2009-05-28 0:09 ` Jonathan Woithe
2009-05-28 8:40 ` Benny Amorsen
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=m3octeu3xj.fsf@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