[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f70dd186-e4a4-4650-9648-3a6383a9a5ba@lunn.ch>
Date: Sun, 16 Jul 2023 21:43:51 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Eric Chastan <ericchastan@...e.fr>
Cc: netdev@...r.kernel.org
Subject: Re: r8169 stuck at 100 Mbps
On Sun, Jul 16, 2023 at 09:26:09PM +0200, Eric Chastan wrote:
> Dear developers,
>
> I am getting in touch because I have trouble getting module r8169 handle gigabit speeds.
>
> You will find my setup attached.
>
> Here is the ouptput of ethtool:
>
> $ sudo ethtool enp2s0
> Settings for enp2s0:
> Supported ports: [ TP MII ]
> Supported link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Full
> Supported pause frame use: Symmetric Receive-only
> Supports auto-negotiation: Yes
> Supported FEC modes: Not reported
> Advertised link modes: 1000baseT/Full
> Advertised pause frame use: Symmetric Receive-only
> Advertised auto-negotiation: No
> Advertised FEC modes: Not reported
> Speed: 1000Mb/s
> Duplex: Full
> Auto-negotiation: off
So you have disabled auto-negotiation, and forced 1G. Have you done
the same on link partner? Without auto-neg, the link partners has no
idea what this device is doing, so it is probably doing 10baseT/Half,
unless you have also configured it to force 1G.
But lets take a step back. Put everything back to defaults with
auto-neg and show use the output from ethtool, so hopefully we can see
what the link partner is advertising.
Andrew
Powered by blists - more mailing lists