public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thanasis <thanasis@asyr.hopto.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
Date: Thu, 20 Sep 2012 20:28:15 +0300	[thread overview]
Message-ID: <505B522F.9090808@asyr.hopto.org> (raw)

I have an Acer Aspire One notebook, and it has a NIC as shown below:

# lspci |grep -i Realtek
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

The driver module that I use is r8169. It works with 2.6 series of
kernels, but it does *not* with the recent 3.x of kernels.

Here is the output of ethtool with the 2.6.38 kernel:

# ethtool eth0
Settings for eth0:
	Supported ports: [ TP MII ]
	Supported link modes:   10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	Supported pause frame use: No
	Supports auto-negotiation: Yes
	Advertised link modes:  10baseT/Half 10baseT/Full
	                        100baseT/Half 100baseT/Full
	Advertised pause frame use: No
	Advertised auto-negotiation: Yes
	Link partner advertised link modes:  10baseT/Half 10baseT/Full
	                                     100baseT/Half 100baseT/Full
	Link partner advertised pause frame use: No
	Link partner advertised auto-negotiation: Yes
	Speed: 100Mb/s
	Duplex: Full
	Port: MII
	PHYAD: 0
	Transceiver: internal
	Auto-negotiation: on
	Supports Wake-on: pumbg
	Wake-on: g
	Current message level: 0x00000033 (51)
			       drv probe ifdown ifup
	Link detected: yes

Question: Should I stick with 2.6 kernels, or are there any directions
on how to make the NIC work with recent 3.x kernels?

             reply	other threads:[~2012-09-20 17:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 17:28 Thanasis [this message]
2012-09-20 17:47 ` RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) Bjorn Helgaas
2012-09-20 18:10   ` Thanasis
2012-09-20 19:02     ` Bjorn Helgaas
2012-09-20 23:20       ` Francois Romieu
2012-09-21  4:59         ` Thanasis
2012-09-21 15:28           ` Francois Romieu
2012-09-21 16:30             ` Thanasis
2012-09-21 17:31               ` Thanasis
2012-09-21 16:41             ` Thanasis
2012-09-21 17:54               ` Francois Romieu
2012-09-21 19:20                 ` Thanasis
2012-09-21 20:29                   ` Francois Romieu
2012-09-21 21:17                     ` Thanasis
2012-09-21 22:53                       ` Francois Romieu
2012-09-22  6:20                         ` Thanasis
2012-09-22  8:28                         ` Thanasis
2012-09-22  8:44                         ` Thanasis
2012-09-21 19:56                 ` Thanasis
2012-09-24 23:12                   ` Francois Romieu
2012-09-25  8:55                     ` Thanasis
2012-09-25  9:54                       ` Francois Romieu
2012-09-25 13:05                         ` Thanasis
2012-09-25 20:53                           ` Francois Romieu
2012-09-26  5:41                             ` Thanasis
2012-09-30  8:03                               ` Thanasis

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=505B522F.9090808@asyr.hopto.org \
    --to=thanasis@asyr.hopto.org \
    --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