mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Bauke <heiko.bauke@snafu.de>
To: linux-kernel@vger.kernel.org
Subject: Realtek Ethernet drivers
Date: Sun, 12 Sep 2010 21:04:44 +0200	[thread overview]
Message-ID: <20100912210444.76ebeee6@tron.localdomain> (raw)

Dear Kernel-Developers,

in the last few weeks I spend quite some time trying to fix a network
problem on my home server which has two Realtek onboard ethernet cards,
lspci-output:

00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet (rev 10)

The problem was that sometimes one of the two cards or both obtained
«no link» status while all cables where pugged in correctly. After
unplugging the power supply and rebooting or after removing the module
r8169 and reloading it all links where up again (or maybe not).  

Searching the web I found that many other users have or had the same or
similar problems with this kind of ethernet card. Some users suggested
workarounds but none of these did work for me. Only after installing
drivers [1] as provided by Realtek my «no link» problems disappeared. 

Taking into account that the Realtek divers for RT8168 [2] and RT8169
[3] cards seem to be more reliable than the drivers in the Linux kernel
tree and that the Realtek drivers [2, 3] are distributed under the
terms of the GPL I wonder is there any good reason not to include these
drivers into the Linux main source tree?


	Regrads,

	Heiko


P.S. I am running 2.6.32-24-generic on a 32-bit Ubuntu 10.04.1 LTS box.


[1] http://www.realtek.com.tw/downloads
[3] http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=4&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true
[2] http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

-- 
-- Man könnte viele Beispiele für unsinnige Ausgaben nennen, aber keines
-- ist treffender als die Errichtung einer Friedhofsmauer. Die, die
-- drinnen sind, können sowieso nicht hinaus, und die, die draußen sind,
-- wollen nicht hinein. (Mark Twain, am. Schriftsteller, 1835-1903)



             reply	other threads:[~2010-09-12 19:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-12 19:04 Heiko Bauke [this message]
2010-09-12 22:37 ` Francois Romieu
2010-09-13  7:59   ` Heiko Bauke
2010-09-13 16:14     ` Tim Gardner
2010-09-13 19:22       ` David Miller
2010-09-13 17:41     ` Ben Gamari
2010-09-13 19:01       ` dave b
2010-09-13 19:00     ` 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=20100912210444.76ebeee6@tron.localdomain \
    --to=heiko.bauke@snafu.de \
    --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 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®