Hi, I'd like to do Signal Integrity simulation  for "JL82599ES SR1VN" PCIe.

but could'nt find an IBIS model on the site,

do you have a reference?

Thanks.

hi, i would like to report that the new intel nic drivers version 19.3 that just released recently has huge 6000+ dpc latency spike once in a few secs.

my specs

Intel(R) 82579LM Gigabit Network Connection

windows 7 SP1 32bit + lastest windows update

i downgrade to intel nic drivers previous version 19.1 and the problem is just gone.

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

This is the built in ethernet connection on my MSI Z170A Gaming Carbon Pro motherboard.

I just built this PC and installed Windows 10 on it.

I've checked everything as far as the actual wired connection, the modem itself, and all of that checks out.  The same ethernet cord that runs to this PC, I tested with a laptop.  The laptop gets proper up/down speeds.

Realistically, my down and up speeds should be 130-160mbps and 25-30mbps.

I am getting about 125mbps down, 2-4mbps up.

The drivers are up to date.  I do not know if this is an issue with windows 10, or the built in Intel Ethernet itself.  If anyone has any input, it would be greatly appreciated.  These upload speeds are killing me!

Hello,

I have a poweredge T630 - just arrived 2 weeks ago.   We put a x700 nic in it.   Win 2012 R2 (fresh install) didn't recognize the card so we downloaded the latest drivers 1.3.115.0 date of the drivers - 3/22/2016 - we downloaded it from Intel today.   The card is then recognized and it showed 4 ports.

We tried plugging in a 10g cable and a transceiver on this nice.  In network card properties it went from 4 ports down to two.   So I checked in device manager and 2 of the ports (the ones we plugged in have this message - This device cannot start. (Code 10).

I have tried turning off the server and turning it back on.

Hi, I have just upgraded to Windows 10 and it is coming up with error, I have read up online and the resolution for this is to update your drivers. Now my driver is Intel 82567v-2, it is saying I have the latest version, however the latest was 2012? I am unsure as to what to do next, as surely the driver needs an update from 2012?

Hello all,

For research purposes I am trying to improve the resume latency of a Linux machine, and specifically I need to speed up its network responsiveness when it wakes up from suspend-to-RAM. I have managed to get a latency of about 3s for now and I am looking for clues to further shorten this delay.

My setup includes an Intel 82579LM Gigabit NIC, which is controlled by the e1000e driver in the Linux kernel (the computer runs ArchLinux). For now it is only linked to my laptop so I have full control over the network characteristics.

On this setup, DHCP is disabled, as well as auto-negotiation; link speed and duplex mode are forced to 100Mbps full duplex. These (somewhat unrecommended) settings allow for a response time of about 3s on resume. This time is obtained by querying a very light HTML page via an Apache server running on the target machine.

So now I need to find other ways to shorten the delay. According to dmesg, the driver itself only takes about 50ms to wake up, and it is the restoration of the link that takes up a lot of time. Essentially, I need some ideas to quicken the process to restore the Ethernet link.

What is important here is that the NIC is waking up from suspend-to-RAM (and WoL enabled of course) so it might be interesting to avoid some steps when setting it up again because it is safe to assume the network hasn't changed during the sleep period. In the ideal case I would like a way to either keep the link up when the NIC goes to sleep (it stays almost awake because of the wake-on-LAN after all) or to have the link immediately available on resume.

So here I am asking for your help. If you have any hints about how these suggestions could be achieved, or any other idea about this, please answer And thank you!

Motherboard: Maximus VII Ranger

Bios: 3003

Driver version: 12.12.218.0

PROset version: 20.1.1022

Windows 10 64-bit (currently, problem started in windows 7)

Yesterday, in preparation of upgrading to windows 10, I decided to upgrade to the latest BIOS as well (version 3003). Everything seemed fine, until this morning when I discovered I had no network connection.

After some searching on the internet, I changed the link speed from auto negotiation to 100Mbps Half Duplex. This at least gave me the ability to download the files for windows 10, hoping that a clean install with the latest drivers would fix the issue, I proceeded to upgrade to windows 10.

Sadly I still have the same issue, any setting lower than 100Mbps Half Duplex works, anything over it wont let me me connect to the network (auto negotiation sets it to 1.0 Gbps Full Duplex and doesn't work either).

Running a speedtest gives me about 75Mbps, which is half my actual internet speed, so keeping it at this is unacceptable for me.

Attempted fixes:

- Tried several BIOS versions including the latest 3 and a version of around the time of purchase of my motherboard (mid 2014).

- Installed several driver versions including the one listed above (currently installed), the latest driver from the intel website and the one currently in the windows 10 driver section on the asus M7R support page.

- Reset TCP/IP

- Reverted to older firmware on my router (Netgear R7000), currently installed: 1.0.4.28

- Different cable and port on the router.

- Used a laptop to test the wired connection, worked without issues and gave me my full 150Mbps in a speedtest. (stable)

The only change I could think of was the BIOS update, but seeing as none of the other versions seem to fix it, I decided to post here because I have no clue where to look anymore.

I have not had any network issues prior to this.

If I do set the Link Speed to anything higher than 100Mbps Half Duplex and run diagnostics this is the error message:

Connection Status : Failed

        This test relies on a response from a

        gateway, DNS, DHCP, or WINS server and

        no such response was received. Any such

        server for this connection may be unavailable

        or misconfigured.

This adapter is configured

        to obtain an IP address automatically

        but no DHCP server is present on the network.

        Windows selected an IP address using Alternate

        Private IP Addressing.

None of the other diagnostics result in error messages.

Hello,

I am using intel igb driver with linux.

The driver strip the packet from vlan and this is not what we need.

We must have the vlan information.

How can we disable this vlan stripping ?

I've seen that there are many who had the same issue, but did not see any solution for that.

Please advise.

Regards,

Ran

Hi!

I'm a student at Umeå University and I am currently using an Intel® 82599EB 10 Gigabit Ethernet Controller to send and receive network packets. I'm using the Flow Director filter to direct the packets into different rx queues, and I want to use the queue statistic registers (QPRC and QPRDC) to count the number of received packets at each queue.

However, the numbers are not correct! The GPRC register gives one number for the total amount of received packets (which is correct, it's the same as the amount of sent packets), while summing the queue statistics gives another number, lower than the GPRC. Shouldn't these be the same? It works at low speeds, <5 Gbit/s, but not for speeds higher than that. All packets should be matching the filters. Where/why are packets lost after being received and counted at the GPRC register, but before being placed in a queue and counted at the queue statistics?

Any other suggestions for ways to count packets divided into different groups/queues are also very appreciated if the solution with the Flow Director filter and queue statistics is not working!

Thanks!

Johan Nilsson

Hello,

I need driver Winpe 5 x86 for hp elitebook 840 g3.

I have test with E1D6332.inf it's don't work.

Where can i find the good driver?

Thanks,

Okay, my original problem was:

ixl problems on FreeBSD (XL710)

I had marked it as resolved since I thought I found the issue and I didn't want to waste anybody's time.  Turns out that sadly, that wasn't the case.  In my original issue I had tagged vlan interfaces on top. I completely removed those to make testing easier.  So now I'm just left with the 4 ixl# interfaces (since I have the 4x10GE card) and then the lagg on top.  I've tried configuring the lagg using both lacp mode and loadbalance (Cisco EtherChannel) mode.

To make sure it wasn't an LACP bug as I previously read (and thought), I set the HPe switch to static LAGG and configured it using source_ip + source_port + destination_ip + destination_port (instead of the default of source_mac + destination_mac).  I then set the FreeBSD side to:

laggproto loadbalance lagghash l3,l4

To match.

So the revised config is:

ifconfig_ixl0="mtu 9000 up"

ifconfig_ixl1="mtu 9000 up"

ifconfig_ixl2="mtu 9000 up"

ifconfig_ixl3="mtu 9000 up"

cloned_interfaces="lagg0 tap0 bridge0"

ifconfig_lagg0="laggproto loadbalance lagghash l3,l4 laggport ixl0 laggport ixl1 laggport ixl2 laggport ixl3 mtu 9000"

ifconfig_tap0="mtu 9000"

ifconfig_bridge0="inet 192.168.4.101/24 addm lagg0 addm tap0 mtu 9000"

defaultrouter="192.168.4.1"

The symptoms are somewhat similar to:

https://lists.freebsd.org/pipermail/freebsd-net/2015-June/042593.html

I say this because some nodes on the same subnet can be pinged and sometimes they can't.  When they can't, adding a static ARP entry seems to fix it.  There's a patch in that thread, but that patch is already in ixl-1.4.27.

Here's the weird part.  Right now it's in a state where pinging the local subnet seems fine (so far), and even pinging the default gateway (the HPe switch) works.  However trying to ping through to the core Extreme networks switch, 2 of the interfaces (VLANs) on it work, and 1 doesn't:

Eg, 192.168.0.1 pings, 192.168.1.1 pings, 192.168.2.1 does NOT ping.  However another host with the same exact config except using ix instead of ixl (so X520 instead of XL710) doesn't have this problem.  Obviously since these IPs are outside of the subnet, ARP isn't the problem.  It's not a route/return route problem, as like I said, the other host works fine.

Connections that do work don't stay working, eg:

# svnlite checkout https://svn.FreeBSD.org/base/head/ /usr/src

...

A    sys/dev/hptmv/hptproc.c

A    sys/dev/hptmv/mv.c

A    sys/dev/hptmv/entry.c

A    sys/dev/hptmv/osbsd.h

A    sys/dev/hptmv/array.h

A    sys/dev/hptmv/access601.h

A    sys/dev/hptmv/hptintf.h

A    sys/dev/hptmv/amd64-elf.raid.o.uu

svn: E000060: Error running context: Operation timed out

So it works for about 30 seconds or so and then just stops.

If I rekick this node using Ubuntu Linux 16.04 LTS or ESXi 6.0U2, everything works great without touching any configuration on the network side.  So it really seems to be an issue with the FreeBSD driver (and not the card's NVm) when coupled with the lagg driver.

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

Hello, we have a Dell Latitude E7270 that has the Intel L219-LM Ethernet adapter. I am using a WDS server to deploy a Windows 10 Image onto the computer, but it does not get an IP address. I am able to deploy Windows 7 just fine, but not Windows 10. I loaded the Ethernet Driver version 20.7.1 to the boot.wim but when I boot up over PXE boot to deploy the image, it doesn't get an IP address. If you need clarification, more details or questions, please let me know. Thanks

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 HP Laptop i installed windows 8 and All my windows 7 drivers are working well on it except Intel 82566MM Network Card when i put my lan cable in it the system gone be mad alot of loss in packets and the device is laggy some times it gave me death screen i do all the trouble shooting for network and installed the update in compatibility mode for windows 7 nothing is worth it's driver problem as when i put the laptop battery mod to maximum performance some times it working well i do clean install and the same thing and tried to upgrade from windows 7 the same thing please suggest a working solution !!!!

Hi all,

I cannot figure out why I cannot enable SR-IOV on Intel Xeon-D 1541's X552 10gbe NIC, it must be the intel's latest ixgbe driver issue because on the same SoC board, the Intel i350 1gbe NIC's sr-iov can be enabled.

Following is the pci device info and also its ixgbe info

root@pve1:/sys/bus/pci/devices/0000:03:00.1# lspci -vnnk -s  03:00.0

03:00.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection X552/X557-AT 10GBASE-T [8086:15ad]

         Subsystem: Super Micro Computer Inc Device [15d9:15ad]

         Physical Slot: 0-1

         Flags: bus master, fast devsel, latency 0, IRQ 25

         Memory at fbc00000 (64-bit, prefetchable) [size=2M]

         Memory at fbe04000 (64-bit, prefetchable) [size=16K]

         Expansion ROM at 90100000 [disabled] [size=512K]

         Capabilities: [40] Power Management version 3

         Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+

         Capabilities: [70] MSI-X: Enable+ Count=64 Masked-

         Capabilities: [a0] Express Endpoint, MSI 00

         Capabilities: [100] Advanced Error Reporting

         Capabilities: [140] Device Serial Number 00-00-c9-ff-ff-00-00-00

         Capabilities: [150] Alternative Routing-ID Interpretation (ARI)

         Capabilities: [160] Single Root I/O Virtualization (SR-IOV)

         Capabilities: [1b0] Access Control Services

         Capabilities: [1c0] Latency Tolerance Reporting

         Kernel driver in use: ixgbe

root@pve1:/sys/bus/pci/devices/0000:03:00.1# modinfo ixgbe

filename:       /lib/modules/4.2.8-1-pve/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko

version:        4.1.5

license:        GPL

description:    Intel(R) 10 Gigabit PCI Express Network Driver

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

srcversion:     9781CEF8A3110F93FF9DBA8

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

depends:        ptp,dca,vxlan

vermagic:       4.2.8-1-pve SMP mod_unload modversions

parm:           InterruptType:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default IntMode (deprecated) (array of int)

parm:           IntMode:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default 2 (array of int)

parm:           MQ:Disable or enable Multiple Queues, default 1 (array of int)

parm:           DCA:Disable or enable Direct Cache Access, 0=disabled, 1=descriptor only, 2=descriptor and data (array of int)

parm:           RSS:Number of Receive-Side Scaling Descriptor Queues, default 0=number of cpus (array of int)

parm:           VMDQ:Number of Virtual Machine Device Queues: 0/1 = disable, 2-16 enable (default=8) (array of int)

parm:           max_vfs:Number of Virtual Functions: 0 = disable (default), 1-63 = enable this many VFs (array of int)

parm:           VEPA:VEPA Bridge Mode: 0 = VEB (default), 1 = VEPA (array of int)

parm:           InterruptThrottleRate:Maximum interrupts per second, per vector, (0,1,956-488281), default 1 (array of int)

parm:           LLIPort:Low Latency Interrupt TCP Port (0-65535) (array of int)

parm:           LLIPush:Low Latency Interrupt on TCP Push flag (0,1) (array of int)

parm:           LLISize:Low Latency Interrupt on Packet Size (0-1500) (array of int)

parm:           LLIEType:Low Latency Interrupt Ethernet Protocol Type (array of int)

parm:           LLIVLANP:Low Latency Interrupt on VLAN priority threshold (array of int)

parm:           FdirPballoc:Flow Director packet buffer allocation level:

                         1 = 8k hash filters or 2k perfect filters

                         2 = 16k hash filters or 4k perfect filters

                         3 = 32k hash filters or 8k perfect filters (array of int)

parm:           AtrSampleRate:Software ATR Tx packet sample rate (array of int)

parm:           FCoE:Disable or enable FCoE Offload, default 1 (array of int)

parm:           LRO:Large Receive Offload (0,1), default 1 = on (array of int)

parm:           allow_unsupported_sfp:Allow unsupported and untested SFP+ modules on 82599 based adapters, default 0 = Disable (array of int)

parm:           dmac_watchdog:DMA coalescing watchdog in microseconds (0,41-10000), default 0 = off (array of int)

parm:           vxlan_rx:VXLAN receive checksum offload (0,1), default 1 = Enable (array of int)

Hello,

I have had an I350-T2 in this PC for several months now without any trouble. Suddenly today, it started acting up. It now takes about 20 seconds longer to boot (before the POST screen even appears), and I have also noticed that the UEFI boot option list keeps growing. If I start with a list that has only the Windows 10 boot manager and the two onboard NICs in it, after the first boot there are two entries for the I350, after the next boot, three, and so on.

My POST code list says that the 20 seconds are spent in "PCI bus initialization"; if I remove the I350, that delay is completely absent.

I have tried to use bootutil to disable the boot ROM on the I350, but it had been disabled already and neither enabling it nor disabling it again had any effect (it keeps adding itself to the UEFI list, see above).

It appears that if I disable the UEFI network support entirely, it works, but I need to boot from the network occasionally.

Any hints, short of a new card?

Thanks,

--

Christian

Hello,

I need driver Winpe 5 x86 for hp elitebook 840 g3.

I have test with E1D6332.inf it's don't work.

Where can i find the good driver?

Thanks,

Had an issue with the latest v.20.7.1 intel ethernet driver download, for which I attempted to load the NDIS62 driver into SCCM 2012 (v.5.0.8239.1000) driver database, which crashed the system.  Tried this in both a test environment and live environment and had the same effect in both.

Just a warning to Intel development team and any other users trying to do the same thing!