From: James Feeney <james@nurealm•net>
To: Realtek and the Linux r8169 crew <netdev@vger•kernel.org>
Subject: r8169 - it's dead jim
Date: Sat, 23 Nov 2013 12:46:00 -0700 [thread overview]
Message-ID: <529105F8.9030901@nurealm.net> (raw)
Hey
Going from 3.12.0-1-ARCH to 3.12.1-1-ARCH, the r8169 module is having the "link
detect" problem again.
Initially, "ethtool -s <blah> autoneg off" gives "invalid argument".
"sudo mii-tool -R enp22s0" - Reset the MII to its default configuration - will
allow a 10Mb/s half duplex connection, with "autoneg off".
"ethtool -s <blah> autoneg off" then will work, after the "mii-tool -R <blah>".
After some time, Auto-negotiation will spontaneously go on, and a 100Mb/s full
duplex connection will come up, on a 1Gb/s interface. Subsequent unplugging and
plugging the cable gives a 1Gb/s full duplex connection.
This problem has been recurring for so many years, I hope the solution is
something obvious, perhaps a recent change to the kernel?
Thanks
James
next reply other threads:[~2013-11-23 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 19:46 James Feeney [this message]
2013-11-24 0:07 ` r8169 - it's dead jim Holger Hoffstaette
2013-11-24 0:50 ` Francois Romieu
2013-11-27 23:14 ` Francois Romieu
2013-11-28 4:02 ` James Feeney
2013-11-30 20:39 ` Francois Romieu
2013-11-30 21:06 ` David Miller
2013-11-30 22:18 ` Francois Romieu
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=529105F8.9030901@nurealm.net \
--to=james@nurealm$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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