Intel Ethernet I219-V Support

Oct 4, 2016, 6:38 PM

Does it work on Linux or Windows?

tucansam · Oct 4, 2016, 10:37 PM

Windows unknown. Linux Mint 17.2, no. IP Fire is passing traffic on it as we speak, however. But I have more familiarity with pfsense and would like to get it working.

Oct 4, 2016, 10:38 PM

@tucansam:

Windows unknown. Linux Mint 17.2, no. IP Fire is passing traffic on it as we speak, however. But I have more familiarity with pfsense and would like to get it working.

It's more about finding out of maybe it's a firmware or hardware issue, or figuring if the card is maybe broken.

tucansam · Oct 4, 2016, 10:41 PM

Well, like I said, ipfire is working on it right now, has been running perfectly since early this morning.

gjaltemba · Oct 5, 2016, 12:01 AM

Installed pfSense-CE-memstick-2.3.2-RELEASE-amd64. Works out of the box.

em0@pci0:0:31:6: class=0x020000 card=0xe0001458 chip=0x15b88086 rev=0x31 hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection (2) I219-V'
class = network
subclass = ethernet

Oct 5, 2016, 8:58 AM

I cannot get the i219V on my Gigabyte board to work

The i219V is normally working but it can be also based on some BIOS incompatibilities that
you will be not able to use it right now!

In OpenSUSE, ClearOS and CentOS this i219V is right working and fine!

gjaltemba · Oct 5, 2016, 12:28 PM

Intel I219-V works in pfSense 2.3.2 on Gigabyte H170N-WIFI and bios version F4.

tucansam · Oct 6, 2016, 2:19 AM

@gjaltemba:

Intel I219-V works in pfSense 2.3.2 on Gigabyte H170N-WIFI and bios version F4.

This is the exact setup I have tried, no luck with pf. There are three BIOS versions on Gigabyte's site, I may try all three.

I am open to any ideas you guys may have. ipfire is great but I've used pf for years and am much more comfortable with it.

gjaltemba · Oct 6, 2016, 4:50 PM

Maybe if you will provide details of what you have done to trouble shoot pfSense and I219-V.

What is the output of pciconf -lv
What is the output of cat /var/run/dmesg.boot
Is I211 working with igb0

dmesg.boot
igb0: <intel(r) 1000="" pro="" network="" connection,="" version="" -="" 2.5.3-k="">port 0xe000-0xe01f mem 0xdf100000-0xdf11ffff,0xdf120000-0xdf123fff irq 16 at device 0.0 on pci3
igb0: Using MSIX interrupts with 3 vectors
igb0: Ethernet address: <snip>igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
igb0: netmap queues/slots: TX 2/1024, RX 2/1024
em0: <intel(r) 1000="" pro="" network="" connection="" 7.6.1-k="">mem 0xdf200000-0xdf21ffff irq 16 at device 31.6 on pci0
em0: Using an MSI interrupt
em0: Ethernet address: <snip>em0: netmap queues/slots: TX 1/1024, RX 1/1024</snip></intel(r)></snip></intel(r)>

tucansam · Oct 8, 2016, 7:30 PM

I'll post the outputs of those commands in a day or two when I have some time, in the meantime I have tried everything in this thread:

https://forum.pfsense.org/index.php?topic=106813.msg599061#msg599061

and this one:

https://forum.pfsense.org/index.php?topic=101689.0

To paraphrase… Tried the binary of the driver available for download in the second thread, tried compiling my own binary using the source from Intel's site and a FreeBSD 10.3 machine, tried several 2.3.x snapshots of pfsense, along with the 2.4 version snapshot. Nothing works with this NIC. Tried resetting the BIOS to factory defaults, still nothing.

But again, ipfire works fine (I am using it in the network from which I am making this post) so I know the hardware/BIOS/etc on the motherboard works.