X550-T2 Bug With New VyOS Version

I’m having an issue with a new version of VyOS and 2500Base/T. I’m using a X550-T2 network card. By default, the card advertises negotiation at 100/1000/10000, but supports 2500BaseT/5000BaseT if you set the link speed/negotiation advertisement. I’m linking to a cable modem with a 2500BaseT support, and I was unable to set the speed as a fixed speed since I believe the modem or the card’s software requires you to autonegotiate. I was able to set the advertised link modes as 2500Base/T by running 'ethtool -s eth0 advertise 0x800000000000’. I put this in the postconfig boot up script.

I’m linking with an S33 cable modem.

On the June 08, 2021 version, my ethtool looks the following:
Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 2500baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 2500Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes

On the August 21st/August 28th versions (both tested but probably more in between and before). I get this. Running the ethtool command directly makes no difference. Even changing advertised link modes does nothing at this point. Maybe there was some driver change? My eth1 connected to my server also only links at Gigabit instead of 10G

Settings for eth0:
Supported ports: [ TP ]
Supported link modes: 100baseT/Full
1000baseT/Full
10000baseT/Full
2500baseT/Full
5000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 2500baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: no

When I switch back to the June 08 version, it all works again.
Any ideas or diagnostics I could do here? Maybe there was a driver change?

Hello @Hydra166 ,

Did you try to set speed and duplex manually on the version begin 21st Aug?
I see that speed ad duplex are Unknown

I tried that with 2.5gbps before and I did not have luck. But things may have changed.Auto negotiation seems to play better with the drivers for Intel. Don’t see a reason why autoeng shouldn’t work, and I think they’re unknown because ethtool thinks there’s no link (says "Link detected: no) considering it’s the same setup, but I’ll still give it a shot regardless in the next ~12-24 hours. I will try to see if there’s any logs when i try again as well.

Sorry for the delay, work has been super busy. Will do this tonight.

Unfortunately, that did not work. Speed and duplex are still unknown and a link is not detected. As soon as I switch back to the old version, my old way of setting autoneg advertisements at 2500Base/T work fine. Setting speed and duplex never really worked on either version for me that well for 2500Base/T. Any ideas?

Hi @Hydra166 , provide please show interfaces output.

For some reason on the very latest VyOS rolling version I had an issue getting my config to post but it worked fine on the 0807 version. I will investigate further.

Will update you tomorrow.

@Hydra166 anything to report? It sounds like it could be related to this thread. I was able to upgrade as far as 20210831 before I started getting errors relating to autonegotiate with an X520.

Nothing much yet, but I think it is the same bug. Autoneg was working fine before and suddenly I try updating and it all breaks. I believe 202108210117 was the first one that caused issues for me. @Dmitry - the interfaces look fine and the same as normal, it is just tough to get a screenshot when you can only see a little in console (I have a lot of VLANs)

Do you have Slack, Discord or Matrix? Maybe we could chat on this.

Just sent you a private message

I’m still experiencing those issues with my X550-T2.

(No Link)
(Config Success)
(dmesg conflicting info)

Originally, I was seeing a no failure on the configuration loading and then I was seeing “Unknown” on both interfaces of my X550-T2 network card (first update in May worked fine then August-now showed that behavior.). Then in the beginning of September, the configuration started to fail as well as that. Then there was some sort of bug found with autonegotiation that was fixed (⚓ T3874 D-Link Ethernet Interface not working.). After the fix, my VyOS is back to its state of the configuration not failing and both interfaces of the X550-T2 refusing to link or detect a link… I suspect some sort of driver issue or interaction issue between VyOS and Debian because the link information in dmesg conflicts with what actually happens with the card in ethtool. In dmesg, eth0 (notable that eth0 only supports 100/1000/2500) seems to link at some point but is not reflected at all in ethtool.

Do you have any ideas? I’m still running on the May version because of these issues and it’s killing me not to update.

Before-June: Worked fine

July-August Versions: No Configuration Fail, No Link Detected

Late August-September Versions: Configuration Fail, No Link Detected on X550-T2

September 31st-October 5rd: No Link Detected on X550-T2

eth0 should link at 2500Base/T and its advertisements are set as so via a startup script, and ethtool verifies this… eth1 should link at 10000Base/T and advertisements are set as defaults.

You can’t see the top but essentially ‘show interfaces’ shows eth0 with – because there’s a missing WAN IP which I acquire through DHCP and all the other interfaces and outputs look normal. The only difference is the lack of link in ethtool. I’m going to file a report on Phabricator when my account gets approved because I’m pretty confident there’s some sort of bug her.