Sorry bud, I just saw ythat you had replied. So, aafter some looking
just came across this -
Linux kernel
Linux 5.15.30-Unraid
oot: md/unraid: Upgraded to version 2.9.22 (revert setting min sector size to 4096)
oot: Added Intel ixgbe: version 5.14.6 so I am going to assume they likely still are on that but it'd be easy enough to check
from 6.10.rc4 changelog. That is dated March 21st, 2022.
I can't find where they added a later release in, could have missed it.
I think I / we may be barking up the wrong tree here though. Seems like this may be a PCIe lane issue. So, you added the network card, and then your m.2 slot went out? I don't think this is actually a firmware issue, per se. but a lane/motherboard/cpu issue.
Look at your error output, it is reporting for 0000:04:00.1 Now look at your eth tool -i references, they do not report the same info. I'm not a linux wiz, but I find this interesting and it's where I would start looking, which brought me to my own results (haven't had a chance to change defaults yet) - I'm guessing you just happened to grab that port as a copy and paste?
```
root@Tower:~# ethtool -i eth2 <-------
driver: igb
version: 5.19.17-Unraid
firmware-version: 1.63, 0x80000ae6
expansion-rom-version:
bus-info: 0000:04:00.1 <-------------
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
root@Tower:~# ethtool -i eth1 <-------------
driver: igb
version: 5.19.17-Unraid
firmware-version: 1.63, 0x80000ae6
expansion-rom-version:
bus-info: 0000:04:00.0 <-----------
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
root@Tower:~#```
Do you have a diagnostics zip by chance?
What does ' lspci | grep X5 ' (Or grep i) say?
Here are my results as an example:
04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
04:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
04:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
So, a few questions, is it only reporting on 0000:04:00.*? Or is that just one you happened to grab?
Havew you tried / are you able to try taking out the NIC, and putting it in a different slot?
Do you have your motherboard manuual, or can you name your motherboard so we can check the lane table?
Have you checked here: https://bugzilla.kernel.org/show_bug.cgi?id=207555 ?
Is your card of Dell origin? Who's name is slapped up there other than Intel? Sun Microsystems? HP? etc.
And also, take a look here, as this seems like it is interfering with your PCIe lanes, as the m.2 and the GPU and the, anything pcie all use lane resources. Perhaps you simply do not have enough lanes (a) or (b) need to properly bifurcate them (google brings up a pretty good explanation, but this can be and be done in the bios but is typically done automatically, although can be done manually on some boards) which is why I say may not be the problem that it seems to be. :
"Is it possible to fix, or should I ditch the NIC?" No, no, no, no , no, no, no, no --- We don't give up that easily, my friend! Every once in a while if you bash something so hard with a hammer, it can turn out to uncover some issues that don't actually pertain to the damage caused from the hammer, just keep at it! if you don't have an extra pcie slot, but have on board graphics, try taking out your graphics card and, as a good measure in regards to bifurcation, put the card in that slot. Boot, see what happens. Any error messages?