10Gtek 10Gb PCI-E NIC in M720q not registering

[toekneeknows]

I'm trying out my mini PC hardware to see if I want to move from ubuntu server to proxmox and I can't get my 10gbe NIC to show in proxmox.

The motherboard nic is working fine and I see no hint of the PCIE nic in any of the diagnostic lists I can find. I don't know where to go from here so I'm throwing up a bit of a hail mary to the crowd.

"ip a" and "lspci" results below

I'm not sure where to go from here. I've tried "modprobe ixgbe".
10Gtek 10Gb PCI-E NIC Network Card, Single SFP+ Port, with Intel 82599EN Controller
Any tips are apreciated. This hardware setup worked with ubuntu server. I only had to modify the netplan yaml.

root@pve:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 98:fa:9b:04:4f:42 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 98:fa:9b:04:4f:42 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.4/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::9afa:9bff:fe04:4f42/64 scope link
valid_lft forever preferred_lft forever
5: veth103i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
link/ether fe:da:1a:5b:64:c1 brd ff:ff:ff:ff:ff:ff link-netnsid 0
6: fwbr103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether e6:55:13:24:b7:2c brd ff:ff:ff:ff:ff:ff
7: fwpr103p0@fwln103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 96:bb:a0:ea:1c:e0 brd ff:ff:ff:ff:ff:ff
8: fwln103i0@fwpr103p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
link/ether e6:55:13:24:b7:2c brd ff:ff:ff:ff:ff:ff


root@pve:~# lspci
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630]
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 (rev f0)
00:1f.0 ISA bridge: Intel Corporation 300 Series Chipset Family LPC Controller (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal]

 

[toekneeknows]

I did a fresh install this morning but no change.

I decided to buy a Mellanox ConnectX-3 CX353A on ebay for cheap and I'll see if I can get that working. I can always throw my current PCIe NIC in something else.

Still interested if anyone can provide some additional troubleshooting steps. This is my last hurdle to moving all my existing network services over to this machine.

 

[Impact]

Since the card does not register in lspci at all I'd take a look at journalctl -kr for errors.

 

[toekneeknows]

Since the card does not register in lspci at all I'd take a look at journalctl -kr for errors.

I didn't see anything that stood out to me when I ran journalctl -kr but I had also restarted recently and it looks like it clears the log.


But I did find my issue just now, and it was a very stupid hardware error. With the mini PC I'm using, I have to use a PCIe riser card to turn the NIC card 90 degrees. I had checked the NIC was properly seated but I just found that the riser card was a little loose. After reseating, now I see a new connection called enp1s0.
Now it's time to move all my services over.