linux-kernel - Re: RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAErSpo4ydsZzrQJCO73mvTEn8TBDVRxg2D0UaHY0XgdyPxJaLQ@mail.gmail.com>
Date:	Thu, 20 Sep 2012 11:47:29 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Thanasis <thanasis@...r.hopto.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)

On Thu, Sep 20, 2012 at 11:28 AM, Thanasis <thanasis@...r.hopto.org> wrote:
> 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?

Can you collect the complete dmesg logs from both 2.6.38 and the 3.x
kernel?  This should just work, so maybe something got broken.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/