You are not logged in.
sudo ethtool eno1
Settings for eno1:
Supported ports: [ TP ]
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: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: on (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
My internet is of 400 Mb/s and the speed tested is limited at 100 Mb/s that I think have something to do with the "Link partner advertised link modes" been capped. I read that this is related with my internet provider, but the wifi of my Android phone is achieving greater speed than the cabled internet in my pc, which never happened. I have been using the same internet in years in a windows OS, now I changed to Arch and this happens. I really confused about it all. Thanks in advance.
Last edited by IgorSabadini (2025-11-22 06:42:56)
Offline
Yeah, from that, whatever you're plugging into only supports 100baseT.
Offline
I was able to solve it by installing Modem Manager by the steps described in https://wiki.archlinux.org/title/NetworkManager in section 1.3. After I installed the ethtool command generates:
Settings for eno1:
Supported ports: [ TP ]
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: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
MDI-X: off (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
And I was able to get full internet connection.
Last edited by IgorSabadini (2025-11-22 06:45:07)
Offline
Get ready for this to be a fluke and/or cable/plug related.
MM devices would start w/ "ww", it's not overly plausible that even iff you have such device the installation of MM would do anything about the modes advertised by a link partner on an ethernet connection…
Offline
Get ready for this to be a fluke and/or cable/plug related.
MM devices would start w/ "ww", it's not overly plausible that even iff you have such device the installation of MM would do anything about the modes advertised by a link partner on an ethernet connection…
Thanks for the answer. I'll be aware, if the problem return I'll open another post with this issue linked.
Offline