Unable to install NIC driver for Intel X710-DA2

[stephenw10]

Please attach the boot log for us to review: /var/log/dmesg.boot

If it has just booted that will be in the system log which you can view anyway in Status > System logs.

Steve

[N0m0fud]

I have the latest 3.4 release. I installed the GBICs and rebooted. I still don't see the interfaces. I know the Interfaces work in these machines as I had them working with Vyos.

pciconf -lv

Does not show the device in the pci device listings. I even removed one of the Broadcom 4 ports NICs thinking that there was an IRQ Resource issue. Not the case.

I then moved the 10 GB card to the other PCI slot and rebooted. Once that was done, The card was recognized and both ports show up:

ixl0@pci0:8:0:0:        class=0x020000 card=0x00078086 chip=0x15728086 rev=0x01 hdr=0x00
    vendor    = 'Intel Corporation'
    device    = 'Ethernet Controller X710 for 10GbE SFP+'
    class      = network
    subclass  = ethernet
ixl1@pci0:8:0:1:        class=0x020000 card=0x00008086 chip=0x15728086 rev=0x01 hdr=0x00
    vendor    = 'Intel Corporation'
    device    = 'Ethernet Controller X710 for 10GbE SFP+'
    class      = network
    subclass  = ethernet

So the drivers work but there is something about one of the PCI slots that I don't understand.

[N0m0fud]

I also installed on another host with 2.3.4 and the card in the other slot. The card was immediately recognized.

Very strange.

[Krishna27]

Hi NoMofd,

Do you mean changing the device slot and rebooting solved your problem even in 2.3.4 release?

I have Intel X710-DA2 CNA 10G NIC, which I have configured for SR-IOV on ESXi 6.0 and have assigned it as a PCIe device to pfSense. The devices don't show up as interface because of missing drivers. How were you able to install the drivers in pfSense 2.3.4 given that they don't come by default in 2.3.4?

It would be of great help if you could let me know.

Thanks

[N0m0fud]

I cannot explain why but changing the slot in which the card was installed and installing the current version of 2.3 showed the card as working with both NICs visible.

That is all I know. Wish I had more insight.

Just reporting the facts

[stephenw10]

I think you're seeing different issues here.

@Krishna; we need to see a boot log to see any errors generated since your card is detected and had a PCIID that should be used by ixlv.

Steve

[Krishna27]

Hi Steve..

Attached is the dmesg.boot file. Please review.

Thanks
Krishna

dmesg.txt

[stephenw10]

Ok, so the correct driver is trying to load for the card and failing:

ixlv0: <intel(r) ethernet="" connection="" xl710="" x722="" vf="" driver,="" version="" -="" 1.4.6-k=""> mem 0xebaf0000-0xebafffff,0xebaec000-0xebaeffff at device 0.0 on pci4
ixlv0: PF API 1.1 / VF API 1.1
ixlv0: VSIs 1, QPs 4, MSIX 5, RSS sizes: key 52 lut 64
ixlv0: Unable to allocate bus resource: AQ interrupt
device_attach: ixlv0 attach returned 6</intel(r)>

It's unable to hook to the Admin Queue which is how it communicates with the host device for some reason.

That doesn't appear to be a common error. Do you have an interface options in the hypervisor that might relate to that?

Steve

[Krishna27]

Hi Steve,

I have assigned this device as a PCIe device after enabling SR-IOV at the hardware (globally, in boot menu) and also at the hypervisor (as in enabling the max_vfs for the device). Do you think this is the reason?

Thanks,
Krishna

[stephenw10]

Hard to say what the reason is right now. That driver is not the newest but if there was a known issue with it I would expect to see bug reports….

There is a slightly newer version available from Intel. Or a significantly newer version in FreeBSD 11.1.

You can try importing 1.4.12 into pfSense.

A better test might be to try loading a FreeBSD 11.1 iso which has 1.7.12.

Steve