Intel X550T2 Wont pull IP or Connect

Specs:
Motherboard: MSI Pro B550M-VC Wifi (MS-7C95)
CPU : AMD Ryzen 9 3950x
RAM : x2 Crucial Pro RAM 64 GB Kit (2x32GB) DDR4 3200MHz (CP2K32G4DFRA32A) 128GB total
Ethernet Card : Intel X550-T2

Onboard Ethernet disabled. Wifi removed.

This is driving me crazy. I cannot get this card to connect to my network on this machine. Truenas Scale sees it, but wont connect. Linux mint sees it, but cannot establish a connection. I put it in my Windows PC, it connects right up and works fine, even pulling its assigned static IP from the router.

When its on Linux or TNS, i get this…

[    9.999105] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
[    9.999110] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
[   10.735860] ixgbe 0000:2b:00.0: Multiqueue Enabled: Rx Queue count = 32, Tx Queue count = 32 XDP Queue count = 0
[   10.842703] ixgbe 0000:2b:00.0: 31.504 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x4 link)
[   10.967976] ixgbe 0000:2b:00.0: MAC: 4, PHY: 0, PBA No: H86377-007
[   10.967987] ixgbe 0000:2b:00.0: ec:e7:a7:12:3e:80
[   11.134665] ixgbe 0000:2b:00.0: Intel(R) 10 Gigabit Network Connection
[   11.908184] ixgbe 0000:2b:00.1: Multiqueue Enabled: Rx Queue count = 32, Tx Queue count = 32 XDP Queue count = 0
[   12.016332] ixgbe 0000:2b:00.1: 31.504 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x4 link)
[   12.142008] ixgbe 0000:2b:00.1: MAC: 4, PHY: 0, PBA No: H86377-007
[   12.142019] ixgbe 0000:2b:00.1: ec:e7:a7:12:3e:81
[   12.318593] ixgbe 0000:2b:00.1: Intel(R) 10 Gigabit Network Connection
[   12.320739] ixgbe 0000:2b:00.0 enp43s0f0: renamed from eth0
[   12.330695] ixgbe 0000:2b:00.1 enp43s0f1: renamed from eth1
[   43.269010] ixgbe 0000:2b:00.0: registered PHC device on enp43s0f0
[   43.562965] ixgbe 0000:2b:00.1: registered PHC device on enp43s0f1
[   48.705144] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[   55.989419] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[   59.486612] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[   86.022234] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[   89.529389] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  116.054033] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  119.958615] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  146.087067] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  150.006610] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  176.119239] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  179.502610] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  206.151834] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  210.046700] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  236.161864] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  239.601409] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  266.194301] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  270.145392] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  296.227212] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  300.214504] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  326.259030] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down
[  330.233879] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Up 1 Gbps, Flow Control: RX/TX
[  356.291732] ixgbe 0000:2b:00.0 enp43s0f0: NIC Link is Down

This happens with both ports. What is happening? Why wont this thing connect through Linux/TrueNas? I was told this card would be compatible.

I’m about to pull my hair out as ive been fighting this for two days.

My first guess is that it’s flapping since it’s not negotiating the link speed properly. Try changing it from auto to 1G on bot the card and switch, if that works then try setting them both to 10G. I am using almost the same card, but I have the DAC version but the RJ45 one should work.

What switch are you using? Is the switch using an SFP+ module or 10g twisted pair native connection?

I agree with Tom, it looks like it is failing to negotiate a speed and you’ll have to manually set both ends.

That snippet is with it set to 1g on the card. My switch is a 2.5G unmanaged so i cant change the speed on it, but i did plug it directly into my router, which is 1G, which stopped the flood of Link up/down, but now it just sits there, still not pulling an IP.

Nothing near that fancy. Its a basic 2.5G Treadnet Unmanaged switch.

These are the exact cards I’ve been using in my upgrade to 10G here at the house. They are working fine for me. I bought actual Intel cards though, not just Intel “chipset” cards.

Currently running 25.04.0, and mine just connected fine at 10G, didn’t have to select anything (mine is connected to a 10G switch).

This suggests that only under Linux can you manually set to 2.5 or 5:

Since a few have said something similar i will address this.

My X550 is a legitimate Intel network card. I bought it new from CDW, and verified the bradyID. The Intel logo is screen printed on the card itself, and the ID stickers on the box and card itself identify as Intel. So im confident I have a full Intel manufactured card and not just a ‘chipset’.

I know the card works with my 2.5g switch, as I said, it worked in my Windows machine (thought that did require windows to pull drivers from the internet first).

My TNS is currently 24.10.2.1 (tho ive been testing on 24.10.2.0 because ive been having random lockups on .1). I’ve been waiting to update to 25 until i got this network issue sorted out because i just switch hardware, and wanted to make sure the transition ‘took hold’ before making major upgrades that could break even more things.

Is it worth just buying a used i226 card?

@LTS_Tom @Greg_E

[edit] 2

Ok.. So TL:DR - after a lot of troubleshooting and testing, ive found two things.

  1. I didnt have the last port on my router enabled (which is why it wouldnt connect though that port when i tested it off my main switch.
  2. For some dumb reason, TrueNAS Scale/Linux, with the X550, and my 2.5Gig switch, do not like each other. Removed the switch from the mix (or rather bypassed it) and it works.

Here the long list of troubleshooting.

  • Original hardware, with onboard (1gb) NIC (Motherboard: Asus P8H77-I) worked and connected perfectly fine on the 2.5gb switch.
  • When i moved the x550 over to my old server machine and had it plugged into my 2.5gb switch, no connection.
  • When plugging that old server (with card) into a 2nd switch (1gb), which was plugged into the first (the 2.5gb) which then goes to the router of course (1gb), it connected.
  • When i moved the x550 back to the other (new) server hardware, plugged into the 2nd switch (1gb) which was still plugged into the first (2.5gb), it connected.
  • When i enabled my open router port and plugged it in directly (1gb), it connected.
  • Moved the cable back to the 2.5gb switch, no connection.
  • Using the x550 on my Windows PC, plugged into the 2.5gb switch, it connected (at 2.5gb speed).
  • Attempted to force 1gb speed on the NIC and disable auto-negotiation, it would not (or never indicated) disable auto negotiation, but did seem to set to 1gb speed. No connection.

So the NIC and the Switch, by themselves, seem to be ok with each other. But for some reason that combination with Linux, seems to do something that causes the NIC to not see or talk to the 2.5gb switch (or at least, not talk properly with it to get any kind of connection).

VERY weird. I now wonder if my onboard NIC on the new motherboard was having the same problem, but im too invested (time wise.. and some money) in getting this x550 to work that im not even going to worry about that one now. But it also means that I now have to be concerned about Switches (even ‘dumb’ ones) being compatible which is annoying and likely something ill never know until i actually test it.

From the prices im seeing? No. They are upwards of $60+ used (for genuine intel cards) and I’d reeeally rather avoid using Amazon knock offs. Not even sure i can return this 550 now its been so long.

You are right, I should have bought a few several months ago when I was seeing cheaper prices.