Purchased in december the newly released asus workstation motherboard Z170-WS that included one I210 adapter and one I219-LM.

I was expecting to use ANS Teaming and VLAN features (still waiting on update drivers to fix these features generally on Win10)
But i don't see the I219-LM listed as supported for the Network Adapter Driver for Windows® 10, and searching on I219-LM it only list with drivers with OS Independent.

Will we that have purchased newly workstation motherboards with dual internet adapters in this case I210 and I219 not being able to use ANS features and VLAN on both connections?
Or is only missing due to being a new model?

USING I210-IT AND I210-IS for ethernet application.

Need ibis model for analysing SI ANALYSIS.

KINDLY UPDATE TO GET THIS DATA.

REGARDS,

SUDARSHAN.

Hello All,

I have 4 port X710 card

[root@localhost vcr]# lsmod | grep i40e

i40evf                 73728  0

i40e                  315392  0

geneve                 28672  1 i40e

vxlan                  40960  2 i40e,ixgbe

ptp                    20480  3 igb,i40e,ixgbe

[root@localhost vcr]# modinfo i40e

filename:       /lib/modules/4.5.5-201.fc23.x86_64/kernel/drivers/net/ethernet/intel/i40e/i40e.ko.xz

version:        1.5.16

license:        GPL

description:    Intel(R) 40-10 Gigabit Ethernet Connection Network Driver

author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>

srcversion:     D50DB0062A90F6C369842D1

alias:          pci:v00008086d00001588sv*sd*bc*sc*i*

alias:          pci:v00008086d00001587sv*sd*bc*sc*i*

alias:          pci:v00008086d00001589sv*sd*bc*sc*i*

alias:          pci:v00008086d00001586sv*sd*bc*sc*i*

alias:          pci:v00008086d00001585sv*sd*bc*sc*i*

alias:          pci:v00008086d00001584sv*sd*bc*sc*i*

alias:          pci:v00008086d00001583sv*sd*bc*sc*i*

alias:          pci:v00008086d00001581sv*sd*bc*sc*i*

alias:          pci:v00008086d00001580sv*sd*bc*sc*i*

alias:          pci:v00008086d00001574sv*sd*bc*sc*i*

alias:          pci:v00008086d00001572sv*sd*bc*sc*i*

depends:        geneve,ptp,vxlan

vermagic:       4.5.5-201.fc23.x86_64 SMP mod_unload

parm:           debug:Debug level (0=none,...,16=all) (int)

[root@localhost vcr]# modinfo i40evf

filename:       /lib/modules/4.5.5-201.fc23.x86_64/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko.xz

version:        1.5.14

license:        GPL

description:    Intel(R) 40-10 Gigabit Ethernet Virtual Function Driver

author:         Intel Corporation, <linux.nics@intel.com>

srcversion:     522158BAB323575B03D48C8

alias:          pci:v00008086d0000154Csv*sd*bc*sc*i*

depends:

vermagic:       4.5.5-201.fc23.x86_64 SMP mod_unload

host - fedora 23 kernel 4.5.5

guest OS is FreeBSD9.3 and VF driver for FreeBSD is 1.2.11(latest).

ixlv0: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfeb60000-0xfeb6ffff,0xfebe0000-0xfebe3fff at device 9.0 on pci0

ixlv1: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfeb70000-0xfeb7ffff,0xfebe4000-0xfebe7fff at device 11.0 on pci0

ixlv2: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfeb80000-0xfeb8ffff,0xfebe8000-0xfebebfff at device 12.0 on pci0

ixlv3: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfeb90000-0xfeb9ffff,0xfebec000-0xfebeffff at device 13.0 on pci0

ixlv4: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfeba0000-0xfebaffff,0xfebf0000-0xfebf3fff at device 14.0 on pci0

ixlv5: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfebb0000-0xfebbffff,0xfebf4000-0xfebf7fff at device 15.0 on pci0

ixlv6: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfebc0000-0xfebcffff,0xfebf8000-0xfebfbfff at device 16.0 on pci0

ixlv7: <Intel(R) Ethernet Connection XL710 VF Driver, Version - 1.2.11> mem 0xfebd0000-0xfebdffff,0xfebfc000-0xfebfffff at device 17.0 on pci0

I have configured 2 ports each with 4 VF so in total i am getting only ~100Mbps which way less than what i get from virtio.

My performance per VF is ~10Mbps and 4 VFs are getting only 40Mbps/port however i am providing close to 2.5Gbps pcap

Also i have upgraded firmware to latest, 5.04

[73053.043664] i40e 0000:aa:00.3: fw 5.0.40043 api 1.5 nvm 5.04 0x800024da 0.0.0

is there anything i am doing wrong? What's official/profiled per VF performance in the guest.

Thank you in advance

-chintu-

Hi !

I use a 10 GbE Controller 82599EN. I need to update an EEPROM which is programed via ROM Writer.

I try to update by using ethtool.

Type as below:

ethtool -E eth2 magic 0x10FB0860 offset 0x0 length 0x1 value 0x07

Result as below:

Cannot set EEPROM data:Invalid argument.

Would you tell me what are invalid arguments ?

Or Would you tell another method for updating an external EEPROM ?

BR,

Taira

Hello, there.

This morning I upgraded my fully functionnal Windows 8.1 Enterprise installation to Windows 10 Technical Preview. Before that, I downloaded the Intel Network Adapter Driver from this website, version 20.1, for Windows 10 64 bits. After the driver installation, I had the VLANs tab in the network card properties. However, i'm unable to create a VLAN. The network card is automatically disabled then I receive an error message saying this (translated from french):

One or more vlans could not be created. Please check the adapter status and try again.

The window freezes and I have to force-close it. 802.1 option is of course enabled in the Advanced options tab. The event viewer always shows the same error when I try to create a VLAN:

Nom de l’application défaillante NCS2Prov.exe, version : 20.1.1021.0, horodatage : 0x554ba6a4

Nom du module défaillant : NcsColib.dll, version : 20.1.1021.0, horodatage : 0x554ba57d

Code d’exception : 0xc0000005

Décalage d’erreur : 0x0000000000264064

ID du processus défaillant : 0x19d4

Heure de début de l’application défaillante : 0x01d0ada33fd50576

Chemin d’accès de l’application défaillante : C:\Program Files\Intel\NCS2\WMIProv\NCS2Prov.exe

Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\NcsColib.dll

ID de rapport : eefb5842-9220-4bad-93d3-774828c5736e

Nom complet du package défaillant :

ID de l’application relative au package défaillant :

I already tried to uninstall all the packages and drivers related to the network card. I deleted fantom network cards then cleaned up the registry. I tried to set some compatibility options to the given executable file, with no success. I tried to reinstall the driver with Drivers Signature disabled, tried to disable IPv4/IPv6 from the network card before trying to add a VLAN... I tried everything I found on Google.

Could someone help me, please?

I have an urgent question for everyone. Let me go ahead and state that it is urgent as I am currently taking summer courses online and missed half of a class this morning due to my issue. This morning while in class my connection dropped, we use skype for class, and I could not be heard or hear anyone, but I could see everyone and they could see me. It might sound like a common small issue, but this made me realize that it happens a lot here. Ever since we received a new modem from Comcast/xfinity, we have the fastest internet speed they offer, we have had some issues that I have just ignored for months. Our wireless connection just randomly goes out for a few minutes throughout the day. Sometimes if we are watching Netflix it will just freeze and start playing or say the connection is lost. This originally led me to believe that the issue was the wireless router. However, my Xbox one is hooked directly to the modem and, as I said we have the fastest speed, always says it has a strict NAT type. Before the new modem I always had an open. It makes connecting card sometimes and as I see now can have an effect on my class work. Could this be some sort of settings issue with the modem? Or something else? Any advice would be appreciated! I just need to get this resolved quickly so if someone can help! Also if anyone needs more information to answer I can give it!

Hi,

I was wondering if it is possible to get access to hardware timestamping on the NIC if you using SR-IOV virtualization.

Currently in a non-virtualized environment, I can configure HW timestamping by passing hwtstamp_config structure to ioctl().  However, when I do the same operation in a Xen based VM which uses SR-IOV (and Intel 82599 NIC) the same operation failed (I am getting Operation not supported message after calling ioctl()).

Reading the documentation on SR-IOV I couldn't figure out if accessing HW timestamps on a NIC is fundamentally not possible, or I just missing some configuration (such as Virtual Function for NIC).

Thank you

ntel(R) gigabit network adopter needs further installation?! PCI\VEN_8086&DEV_10f0&SUBSYS_00008086&REV_05...... can any one help? Intel for unknown reason does not recognise the original Intel adopter in my computer! hence i have difficulties connecting to internet.

Thnx

Hi,

I'm having one of the strangest audio problems I've ever seen on my PC right now, which seems to be linked to my internet connection (of all things), which uses an intel network driver.

First off I'm the sort of PC user that likes to leave the system on 24/7 and power off the displays when not in use, as this allows me to run certain background tasks (like automated file backups) overnight.

After leaving my system running for a few days I started to notice an erratic popping noise in my audio, a bit like static, but not as consistent. After doing some research online, I learned about something called DPC latency and used a program called 'DPC Latency Monitor' to try and diagnose the problem.

The data I collected pointed to my Intel network driver as a possible culprit for my audio issues, so I tried disabling the corresponding network adapter from the network and sharing center, and re-ran the latency test. The results with the network adapter disabled were greatly improved, and I could no longer hear the popping noises when listening to offline audio.

As soon as I re-enable the network adapter the problem returns, and so far the only solution I have is to randomly reboot my system, which I find rather inconvenient, as it also requires me to save all data in all open programs, exit out of everything, and then open it all back up again later.

I've already used Intel's driver update utility to ensure I'm on the latest drivers, and am unsure of what to do next.

The following is a compilation of the data I collected while trying to figure things out:

DPC latency monitor data, with network adapter enabled and before a system reboot:

With network adapter disabled and before reboot:

Network adapter enabled, after reboot:

Output from Intel system support utility:

I have a machine on Windows 10 that according to device manager is using the Intel(R) 82578DM Gigabit Network Connection.

The problem I have is that according to LatencyMon the ndis.sys and tcpip.sys drives are showing extremely large amounts of latency. This means everytime I refresh a web page my machine locks up for a split second and any audio or video currently playing stutters really heavily.

I've tried updating the drivers to no avail. At present device manager is showing the driver version as 12.12.50.6 provided by Microsoft.

I've tried downloading some drivers from the Intel website but those get to the "Copying drivers" stage and then fails stating that there were no Intel adapters found. This has confused me a lttile since device manager lists it as an Intel adapter.

Would massively appreciate it if someone could assist in resolving this issue.

Thanks.

Hello,

after the update to Windows 10 (x64, Build 10240) the creation of a teaming group (static or IEEE802.3ad) with a I211+I217-V NIC fails.

Drivers have been upgraded to the latest version available and multiple reinstallations with reboots din't help either. Whenever the group creation wizzard is used and a groupname (several tried), the adapters and LACP have been selected, a Windows pop-up appears to tell me group creation has failed.

However the Windows Device Manager shows a newly created "Intel Advanced Network Services Virtual Adapter", so some kind of configuration seems to get done.

Using Windows 7 SP1 x64 the exact same setup worked flawlessly for months, so Win10/the driver are the likely culprit.

Is anyone experiencing similar problems and/or is this a known bug? Feedback on this issue is greatly appreciated.

Thanks in advance!

Kind regards,

Famaku

I also posted this message on the motherboard manufacturers forum. If this is not the right place to put it, my apologies.

So I got myself an intel pro 1000/pt quad port network card, but it doesn't get detected by my motherboard. Here is a nice list of the what I've done, and what I've found:

When I say "it doesn't get detected" I mean the following: First time I installed it, and booted into windows 10 enterprise, it didn't show up in device manager (I also selected the "Show hidden devices" under "view" in device manager).

I didn't quite know what was going on then, so I grabbed a debian jessie live USB, booted into that. Neither "lspci" or "dmesg" mentions anything about seeing the device (so not even something like "failed to start" or other error conditions).

So finally I went into my bios "hardware monitor" thing, and it didn't show the PCIe slot it was in as containing anything.

Every time from now on I try something and it doesn't help, it means I went though the above three steps.

I've tested the network card in 2 other systems where it was fine: A supermicro server (Debian jessie, 2 xeon's - socket 1366, 64 gb ram, ...) and an Lenovo/emc storcenter (core2duo iirc, don't ask me what OS, it's something debian based). In both of these systems the card works just fine (well, I did only test debian on those systems since they can only suffer short periods of downtime, and I'm not in the mood to try and get windows running on either). The card thus works.

I've repeated this test a few times just to see that the card didn't die along the way, but it still works fine in those.

So here are the things I tried to fix it:

-Installed newest bios version (1.B) from the motherboards support page.

-Tried different PCIe slots - First I tried it in PCI_e3 according to the motherboards manual. After that, I tried every other slot that wasn't 1x.

-Swapped the GPU with the card (so, I put the gpu in PCI_e3, and the NIC in PCI_e1)

-Manually forced the PCIe gen of the slot the card was in to gen1 and gen2

-set the pci latency timed to 64 instead of 32 (while I've never, ever had to manually play with those (and I've built hundreds of systems), I was getting quite desperate at this point).

-I then tried all of the above shuffling around with system wake on PCIe device turned on

-Tried all the above with the intel onboard network adapter forcefully disabled

-Tried 2 other RAID controller cards, which all just work fine first-time (this to rule out something stupid going on with my CPU not wanting to do /any/ other pci device).

Oh, and all of this is without any overclock, the first thing I do when anything is acting up is set the overclock settings to default.

System specs:

Board: x99s SLI PLUS

BIOS:  1.B, as per the latest on the motherboards webpage

VGA:   AMD R9 280x

PSU:  Corsair RM1000

CPU:  i7 5820k, default clocks

MEM: 4x8gb Crucial DDR4 (nothing fancy, if you really need it I'll go look for model numbers) - running stock speeds and all that
HDD/SSD: 2 Adata SSD's

OS: Windows 10 64bit enterprise, Debian Jessie

Anything else you guys suggest trying? If I can't get it fixed, I'll get a replacement board. My main worry is that it has nothing to do with my board specifically, but something like an odd compatability-clash between this board model and that card, in which case that will be to no avail, and I'm also not willing to shell out /even more/ for a newer model network card and risk that one not working either.

Hello,

I have several 2012 R2 systems with x710 NICs that blue screen and get network disconnects in the event logs when we have offloading turned on. If we disable offloading, the system is stable. We've tried the Dell version of the drivers, as well as the Intel drivers (v20.7). It appears to be very similar to the issue in the thread x710-DA2 iSCSI Connections Keep Disconnecting .

Is anyone else having problems with offloading on these NICs?

I tried using the 20.7 UEFI Ethernet Driver E7006X3.EFI, but I see that I217 support has been removed.  Why? 

I need I217-LM support in this driver.

Going back I see the last time it was in the Driver was version 20.0, E6604X3.EFI.

Can I217 support please be added back into future builds?

Thank You

I try to install windows 10 on a ISCSI disk but during the second phase of installation the ISCSI Disk become inaccessible during the boot.

I use the latest NDIS 4 driver version 21.0 Network card is X540-T2.

All other OS version its working fine.

Hi,

I'm having problems measuring RTTs with 82574L cards. In a simple experiment, I have two servers with 82574L directly connected with a cable. Server A sends a probe packet to server B and measures TX hardware timestamp tx_a. Server B replies an echo packet after receiving the probe packet, and notes down the RX hardware timestamp of the probe packet and the TX hardware timestamp of the echo packet as rx_b and tx_b. Finally server A notes down the RX hardware timestamp of the echo packet as rx_a. The RTT is computed as (rx_a - tx_a) - (tx_b - rx_b).

Since the NICs are connected back to back, I was expecting the RTTs measured to be very consistent. However this is not the case. The resulting RTTs varies from 1.4us to 100us.

Could anyone here shed some light on this problem?

My source files attached.

Thanks,

Yilong

Hello,

I have an issue with I350 Quad port NIC with driver version 20.7. The following features are missing on port 1,2 and 3:

• *WakeOnPattern
• *WakeOnMagicPacket
• ReduceSpeedOnPowerDown
• *PMNSOffload
• *PMARPOffload

On port 0 are the missing features available.

Do somebody knows something about that issue.

Kind regards

Matthias

There are the XML files needed for further analysis

I am developing a Miniport device driver for an 82574l based NIC on Windows CE 5.0, using NDIS 5.1. Transmission setup works OK and the NIC transmits OK. I setup receive as the documentation dictates:

1. Allocated a region of memory for legacy receive descriptor list using NdisMAllocateSharedMemory and setup a descriptor ring.
2. Setup receive buffers of appropriate size and allocated and pointers to these buffers and stored these in each descriptor in the descriptor ring.
3. Programed the descriptor base address with the address of the descriptor ring.
4. Set the length register to the size of the descriptor ring.

However the when I process receive related interrupts the memory buffers pointed to by the memory allocations I got from NDIS point to regions filled with 0s. Using the diagnostic registers it shows that data was received and the Receive Data FIFO Packet Count register indicates how many packets were received and analyzing the RX FIFO PBM region seems good. So I must be doing something really bad when setting up my RX registers to not be able to handle RX packets. I will gladly provide my code to anybody who can help me.

getting the below with 3.3.3 and 3.3.4 -  can compile 3.1.0.2  but it doesn't have the I219 in it which is the nic in the laptop we are trying to bring online

I can compile 3.3.3 under the 2.6.27.7-9 kernel - once I added some undeclared variables to kcompat.h - but don't know how to get around this error on the 2.6.27.7 -

And it has to be 2.6.27.7 -  I can't use a newer kernel - due to other dependencies in our shop.

In file included from /tmp/e1000e-3.3.3/src/e1000.h:32

                        from /tmp/e1000e-3.3.3/src/netdev.c:48

/tmp/e1000e-3.3.3/src/kcompat.h: In function '_kc_napi_alloc_skb';

/tmp/e1000e-3.3.3/src/kcompat.h:4601:error ;'struct napi_struct' has not member named 'dev'

gcc is 4.3.2

thank you

Hi,

I'm using an ASRock Rack EPC612D8A-TB motherboard with two Intel onboard NICs (I210 (Ethernet 2) and I217-LM (Ethernet)), running Win 8.1 Pro x64 with all Windows Updates installed and the latest Intel Ethernet driver package (20.2.3001.0). My problem is with the I217-LM, according to the Intel spec sheet it does support RSS (cp. figure on page 2).

In the I217-LM's advanced driver settings there is an option to enable and disable RSS. However Windows itself always says that the I217-LM is not RSS-capable.

The same option in the I210 driver options has the expected effect: With the PowerShell command get-SmbClientNetworkInterface you can see the RSS capability changing from True to False and vice versa.

Can anyone tell why the I217-LM is not getting the RSS feature?

Further system details:
CPU: Xeon E5-1620-V3

RAM: 2 x 16 GiB Crucial DDR4-2133 ECC

The motherboard does not have a later BIOS/UEFI release than the one installed.

Thank you very much for your help!