I have a USB-C 3.1 hub (which has its own power supply and is connected to 2x2 hard disk bays), USB wireless audio connector for my headphones, USB keyboard and USB wireless mouse receiver which I'd actually moved to front panel USB. USB webcam, USB microphone. So actually, all USB.
Currently it just has the keyboard plugged in with the mouse plugged in to the front panel.
]]>It's only been a couple of days but it's definitely lasted longer than before. I wonder if something was causing some kind of electrical interference or perhaps there's a power issue where with too many things plugged in, the board can't supply enough power for everything at once and forces the network adapter to run at a lower power level (this is purely speculation, I have no idea if this is the case)
]]>What I have noticed is that to reset the speed correctly I have to unplug the PC end, not the router end, reconnecting at the router end has no effect. I'm not sure why this would be, but perhaps physically disconnecting the PC causes something to reset.
]]>I've swapped it to a different port on the router, I've swapped the ports with another PC which hasn't had this issue and is also running arch, but has a realtek ethernet adapter.
I'll see if it breaks, but it does seem to be once every few days.
]]># ethtool enp5s0
Settings for enp5s0:
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: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: off
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
Current message level: 0x000060e4 (24804)
link ifup rx_err tx_err hw wol
Link detected: yes
sudo ethtool -s enp5s0 speed 1000 duplex full autoneg off
netlink error: link settings update failed
netlink error: Invalid argument
Autoneg on or off has the same effect. Setting speed to 100 works with autoneg on and off.
This is the same issue the original poster had, I cannot specify speed 1000, it always gives "Invalid argument". 100 works fine
sudo ethtool -s enp5s0 speed 100 duplex full autoneg off
Works successfully. With speed 1000 it gives "invalid argument"
]]>Does it happen if you turn autoneg off, duplex full and speed 1000?
(With ethtool, so we see what actually happens, and *before* the incident)
alx doesn't provide any parameters for power saving and I assume this isn't a notebook?
It's a desktop.
alx 0000:05:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [e0:d5:5e:23:6c:9f]
It took a while for this to happen this time
Boot:
Settings for enp5s0:
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
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
Current message level: 0x000060e4 (24804)
link ifup rx_err tx_err hw wol
Link detected: yes
After issue:
Settings for enp5s0:
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
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
Current message level: 0x000060e4 (24804)
link ifup rx_err tx_err hw wol
Link detected: yes
After physical reconnect:
Settings for enp5s0:
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
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Auto-negotiation: on
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
MDI-X: Unknown
Current message level: 0x000060e4 (24804)
link ifup rx_err tx_err hw wol
Link detected: yes
The modes are being reported correctly, if I manually try to set 1000Mb using KDE's NetworkManager GUI nothing happens. The only way I can get the full speed back is to disconnect and reconnect the cable.
]]>alx doesn't provide any parameters for power saving and I assume this isn't a notebook?
]]>I do not believe it's a cable issue, I've been using the same Cat7 cable for 2 years.
After some time, the adapter resets and the speed is stuck at 100mbs. No changes in the software can reset it, the only way I can reset it is to unplug the cable and plug it back in.
There's nothing obvious in dmesg:
[ 8.495117] alx 0000:05:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [e0:d5:5e:23:6c:9f]
[ 8.510285] alx 0000:05:00.0 enp5s0: renamed from eth0
[ 11.989920] alx 0000:05:00.0 enp5s0: NIC Up: 1 Gbps Full
[ 2453.620391] alx 0000:05:00.0 enp5s0: Link Down
[ 2473.519550] alx 0000:05:00.0 enp5s0: NIC Up: 100 Mbps Full
[ 3023.145846] alx 0000:05:00.0 enp5s0: Link Down
[ 3028.845658] alx 0000:05:00.0 enp5s0: NIC Up: 1 Gbps Full
On boot I got 1Gb, then after nearly an hour the adapter reset and changed to 100mbit. The second 1gb connection is me disconnecting and reconnecting the cable.
grininmonkey, have you noticed the same problem reoccur?
]]>Settings for enp2s0:
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
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Current message level: 0x000060e4 (24804)
link ifup rx_err tx_err hw wol
Link detected: yes
I repeated the following with consistent results and I don't understand it.... my only assumption is that the NIC on the MB is simply a cable snob of some sorts and is extremely picky.
I have 5 devices with 1G nics plugged into my dumb switch... all using 6ft 5e patch cables. 4 ( original ) have had no issue linking at 1000, never once messed with this. The new box is a repurpose older MB/CPU that I originally ran Arch on more than a year ago before new hardware... just dusted it off and decided to do something with it...
So anyway... I was unplugging from my main computer and plugging that cable into this box with this issue and same with others... after just trying lts I thought... hey.. I do have a Cat6 cable... let me try for giggles and why not.... [ pow ] it linked @ 1000... so I then decided to reboot into mainline kernel... [ rut row ] will only link @ 100 with new Cat6 cable... reboot into lts and it links @ 1000 with Cat6 cable.... plug in any of the other 4 in use and working fine @ 1000 Cat5e cables... and nope.. only links @ 100...
This is the oddest network experience I have had so far.... its a 2016 MB i7 6700K and going to be a dev LEMP box.. so LTS is fine... but very weird none the less..
]]># ethtool -s enp2s0 speed 1000 duplex full autoneg off
Cannot set new settings: Invalid argument
not setting speed
not setting duplex
not setting autoneg
under lts.... I also tried this
# ethtool -s enp2s0 speed 1000
Cannot advertise speed 1000
Cannot set new settings: Invalid argument
not setting speed
better verbose under lts.... anyway.....
]]>