Hi,

i am an IT student at a german university. Currently i am working on my bachelor´s thesis about the PTP protocol. For this reason i got a Intel network adapter I210-T1, which has support for the IEEE 1588 (=PTP) protocol.

On Linux Ubuntu works everything pretty fine. The card is working as expected. The first time i wanted to use it on Windows, my system frezzed. And still after rebooting the OS, the network card can not be used.

First of all my HW specifications:

- MB:          Asus P7H55-M Pro

- CPU:        Intel Core I5 650 @ 3.20GHz

- RAM:       16.0GB DDR3

- Graphic:  Intel HD Graphics

- Storage:  223GB OCZ-VERTEX3 (SSD)

The SW specifications for Linux (everything is fine here):

- OS:         Ubuntu   16.04 LTS

- Driver:    igb-5.3.5.4

- Other:     linuxptp package

And for Windows (with the issue):

- OS:        Windows 7 Pro 64-bit SP1

- Driver:    Intel Network Adapter Driver for Windows 7 (Version 21.1, 64-bit)

Problem:

The main problem in Windows is located in the device manager. Here it says on my adapter, that the error code 31 appeared. See the attachment. This means, that i absolutely can not use the card. The first time after installing the card, Windows tried to search and install the driver by itself. Then, as i said, the whole system frezzed. I had to power it off with the switch. After rebooting Windows, it said, that it was not able to install the driver. I tried to do that manually with the driver of the support website, but with no success. Only the error code 31 appears.

What i already have done:

- Let Windows try to install the driver by itself -> No success

- Install driver manually -> No success

- Make sure Windows Update is up to date -> No success

- Reinstall and/or update the asus driver for the motherboard (also the chipset driver etc...) -> No success

- Update BIOS to newest version -> No success

- Testing the card on an other pc -> Success

- Testing the card under Ubuntu -> Success

- Tried to execute this solution -> http://www.tomshardware.co.uk/answers/id-1750879/code-error-network-adapter.htm -> No success

I know that there is always the possible solution for a reinstall of Windows, but this current installed OS is actually only a month old, so pretty new. What else can i do besides this?

Thank you,

doritsep

Update

Found an old post of another forum with the exact same problem, but with no solution. -> i210 driver installation freezes Windows 7 x64 | FreeNAS Community

I have an extremely odd situation with BPF expressions and VLAN tagging when using ixgbe devices on CentOS 6 (this is for Network Intrusion Detection software).

I have many other CentOS 6 boxes with igb devices and I'm successfully using complex BPF expressions to match VLAN IDs and port numbers, for example:

vlan and ( ether[14:2] == 0x0005 and port 25 || ether[14:2] == 0x0006 and port 25 )

Which means: Look for packets that are VLAN tagged, where the VLAN ID is 5 and the transport protocol port number is 25, or VLAN ID is 6 and the port is 25. The is necessary due to the way BPF works, which is it will shift the byte match by 4 bytes after each occurrence of "vlan" in the expression (hence you cannot construct an expression like (vlan 5 and port 25 || vlan 6 and port 25), because the second half of the expression would only match if traffic for VLAN 6 was encapsulated inside VLAN 5). Statically using ether[a:b] will always look a-bytes deep in the packet (starting at 0) and read b-number of bytes to match. This is supposed to work regardless of whether "vlan" has occurred in the expression (making it a reliable way to find the outer VLAN ID).

So here's the problem: It doesn't work on ixgbe (at least not in promiscuous mode). When I try to match on ether[15] (the low-order bytes of the VLAN ID) it will actually match on byte 19 (the 20th byte), which mean it's shifted 4 bytes over. If I try to match on ether[11], the expression returns true when *both* byte 11 (12) AND byte 15 (16) equal the expression, which is totally bizarre. I cannot seem to make a 2-byte pattern match at all (but maybe I just didn't run tcpdump for long enough for that amazing coincidence).

By the way, I can match any other bytes normally with ether[a:b] expressions, it's only the 12-15 bytes (VLAN ethertype and VLAN ID) that have bizarre behavior.

I strongly suspect this is due to rx_vlan_offload being enabled, but when I try to disable it with ethtool I get:

$ sudo ethtool -K eth1 rx-vlan-offload off

ethtool: bad command line argument(s)

For more information run ethtool -h

Edit: I found that 'ethtool -K <dev> rxvlan off' is the correct command, but disabling that didn't change the behavior.

This happens with both ixgbe driver version: 4.2.1-k (shipped with the CentOS kernel package), and also with version: 4.4.6 (built from source).

I found a reference to an extremely similar sounding bug here https://sourceforge.net/p/e1000/bugs/375/, but that seems to be a much earlier version of the driver. This one appears to check for RHEL_RELEASE_VERSION > 6.1 and enable 802.1P support accordingly:

#if (RHEL_RELEASE_CODE && RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(6,1))

#define HAVE_8021P_SUPPORT

#endif

So two questions:

1. How can I resolve this issue of not being able to use ether[14:2] to match VLAN ID in BPF?

2. Why can't I disable rx_vlan_offload with ethtool? (it does not say [fixed])

Message was edited by: Chort Zero

Someone on Twitter showed me 'rxvlan' is ethtool's shorthand for rx-vlan-offload, but it doesn't make any difference after disabling it.

Dear Intel Community

In our device we have two WGI210IT ethernet controllers and we are facing an issue with them: Very rarley, let's say less than once per 100 boot ups, we see that the device ID is 1531 instead of 1533. At the moment we cannot reproduce it, it just appears sometimes on our devices.

lspci under linux shows it like this:

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

02:00.0 Ethernet controller: Intel Corporation Device 1531 (rev 03)

After a reboot the Ethernet controller has ID 1533 again:

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

Early at bootup of Linux the following message apears:

kernel: pci 0000:02:00.0: [8086:1531] type 00 class 0x020000

So it we doubt that any operating system related action causes the wrong ID.

The configuration is as follows:

- Ethernet controller firmware: Dev_Start_I210_Copper_SMB_8Mb_A2_3.25_0.03.bin

- Changes in Flash (On some devices done with Lanconf.exe under DOS and in others with eeupdate64e under Linux):

--> Word 0x20: Set bit 4 to '1' (disables Gbit Ethernet)

--> Changed MAC Address

- Gigabit Ethernet is not supported on HW side. MDI_PLUS_2 / MDI_MINUS_2 / MDI_PLUS_3 / MDI_MINUS_3 are pull-up to 1.5V via 49.9R resistors

- Flash: MX25L1606EZNI-12G

- 33R resistors in SPI lines (NVM_SI, NVM_SO, SVM_SK, NVM_CS#)

- Pin 12 is pulled-down with 10k (strap pin --> non secure mode)

Hardware checks:

- The I210 and the flash are powered from the same 3.3V source. First flash access happens after 25ms after 3.3V is reached. The flash itself requires 200us to be ready after Vmin is reached. So the flash is ready at first access.

- The signal levels of all SPI lines are fine.

- The solder points are checked and nothing wrong was seen.

We checked a few register values while the problem was seen:

Read at 0x90012010 | 0x40 0x2A 0x48 0x00 (Base address is 0x90000000)

The 1533 controller shows:

Read at 0x91312010 | 0x40 0x2B 0x08 0x06 (Base address is 0x91300000)

Differences:

EEPROM-Mode Control Register - EEC (0x12010) bit 8 is '0'. --> EE_PRES: No Flash with correct signature or empty iNVM

EEPROM-Mode Control Register - EEC (0x12010) bit 22 is '0'. --> Reserved: No info from datasheet

EEPROM-Mode Control Register - EEC (0x12010) bit 25 is '0'. --> SEC1VAL: Sector 1 not valid (but not meaning full due to bit 8 is '0')

EEPROM-Mode Control Register - EEC (0x12010) bit 26 is '0'. --> FLUDONE: No flash update done

Have you got any idea what could cause this problem?

Thank you in advance and best regards

Stefan

Hi,

We are struggling to get the JTAG chain working on WGI210.

Do we need to set some pins at a particular level before we can activate this? Is there a defined startup sequence needed for this?

Thanks in advance,

Mattias

Hi,

I'm looking for the Ibis model for the i218LM. Could you provide me the link to where this ibis model resides?

Thanks,

--Lisa

I have a problem very similar or identical to that experienced by nh29 here
i218-LM code 10 after restart without cable

Since purchasing my Let's Note laptop PC CF-LX3 I have been unable to connect to wired land only wifi.

I eventually got around to having a look in the device manager (I had thought that the problem must be mine since I had the problem from new)

In the device manager the driver for my Ethernet Chip has the yellow triangle and exclamation mark.

i am told that I have a can't start due to  Code 10.

I have tried installing your latest drivers from your site

Download Intel® Network Adapter Driver for Windows 8.1*

and installing them by first extracting them using 7-Zip and browsing to the 64 bit drivers using the method described on reddit here

ethernet driver issue : techsupport

I also tried letting the Device manage find drivers on the Internet (which told me that I had the most up to date drivers installed)

Add I also downloaded the Win81_64_d135311 file from my computer manufacturers site here in Japan

Let's note CF-LX3シリーズ 導入済みドライバー | パナソニック パソコンサポート

In all cases I am told that the driver installed but the the device can not be started

the driver was installed but

"this device cannot start. (Code 10)"

In all cases I uninstalled and deleted the previous drivers first.

Like nh29 I have a degree in electronic engineering (thought I am not chartered) .

On nh29's thread it was suggested that this has something to do with the Ultra Low Power settings. I am not sure how to turn these off.  You send a tool to nh29 apparently after which he did not respond to the thread above so perhaps that cured things for him.

I see that in the Power Plan settings there are Intel CPPC Energy Efficient Optimization but in both they are now set to Plugged in Disabled, and Aggressiveness when plugged in at 0%

(I could have sworn that earlier today these settings were different! Perhaps one of the more recent drivers that I installed changed the settings).

My system is Windows 8.1 Pro 64 bit Japanese (GUI language English)

The device manager says

This device cannot start. (Code 10)

{Operation Failed}

The requested operation was unsuccessful.

In the advanced settings

Wake on Link is Off

and (aha) "Low power Ethernet" was on. I set it to off and disabled, then re-enabled the device but it still says Code 10.

The other thing that surprises me is that under driver details the files are in the Windows sub folder "System32" is that as it should be?

C\windows\system32\Drivers\e1d64x64.sys

and the following three files in the same location

e1dmsg.dll

NicCo36.dll (this is the oldest file in system32)

NicINstD.dll

According to the page below the first file e1d64x64.sys is an Intel "Gigabit" driver (sounds right)

What is e1d64x64.sys from Intel Corporation? (id:21427853)

And the version number of the driver in my Device manager is the same as that mentioned on the page above

12.9.16.0

Tim

Hello,

I would like to know the  Packet timestamp sampling latency of X550 controller at different link spped.

For example in the i210 datasheet in the section 7.8.3.1 (Capture Time Stamp Mechanism) there is a table summarizing the packet timestamp sampling latency of the i210 controller.

In the X550 datasheet section 7.7.3.2 (Time Stamping Mechanism) this information is missing.

Please help find this information for the X550 controller.

Regards

Yacine

I have downloaded Intel NIC driver for “Intel(R) Gigabit 4P
I350-t rNDC“ NIC adapter for Windows 10 OS from below link

https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapters-Connections-CD?product=59679

Below are the steps I performed for driver installation

1. Extracted 21_1_cd.zip
   file to C drive on the target system.
2. Open
   command prompt in administrative mode.
3. Go to C:\21_1_cd\APPS\PROSETDX\Winx64
   path. (21_1_cd is the extracted folder name in C drive)
4. Execute
   below command to install the driver
   1. Start /w DxSetup.exe /qn /norestart

The driver does not get installed including proset software. If I
don’t pass /norestart, the driver and proset gets installed but it reboot
automatically.

I want to know how to install the driver and proset without
auto-rebooting. I will take care of rebooting the system immediately after the
driver is installed.

When I install the driver ver 21.1 Download Intel® Network Adapter Driver for Windows® 10  I get a message

"Important Note:  Creating Intel® ANS teams and VLANs on Microsoft Windows® 10 is currently not supported.  As a result, when created, teams and VLANs do not pass traffic.  We expect that ANS will be supported on Microsoft Windows 10 client in a future release"

I dont need teaming etc...but once the driver is installed, I dont see WOL in the ADVANCED option  ???

Where is the WOL feature???

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

Is there any possibility to get an 540-T2 running on Windows 10 1607?

After Driverinstallation i got an Code 10, Driver could not be startet Error.

Thanks for any Help.

I have an extremely odd situation with BPF expressions and VLAN tagging when using ixgbe devices on CentOS 6 (this is for Network Intrusion Detection software).

I have many other CentOS 6 boxes with igb devices and I'm successfully using complex BPF expressions to match VLAN IDs and port numbers, for example:

vlan and ( ether[14:2] == 0x0005 and port 25 || ether[14:2] == 0x0006 and port 25 )

Which means: Look for packets that are VLAN tagged, where the VLAN ID is 5 and the transport protocol port number is 25, or VLAN ID is 6 and the port is 25. The is necessary due to the way BPF works, which is it will shift the byte match by 4 bytes after each occurrence of "vlan" in the expression (hence you cannot construct an expression like (vlan 5 and port 25 || vlan 6 and port 25), because the second half of the expression would only match if traffic for VLAN 6 was encapsulated inside VLAN 5). Statically using ether[a:b] will always look a-bytes deep in the packet (starting at 0) and read b-number of bytes to match. This is supposed to work regardless of whether "vlan" has occurred in the expression (making it a reliable way to find the outer VLAN ID).

So here's the problem: It doesn't work on ixgbe (at least not in promiscuous mode). When I try to match on ether[15] (the low-order bytes of the VLAN ID) it will actually match on byte 19 (the 20th byte), which mean it's shifted 4 bytes over. If I try to match on ether[11], the expression returns true when *both* byte 11 (12) AND byte 15 (16) equal the expression, which is totally bizarre. I cannot seem to make a 2-byte pattern match at all (but maybe I just didn't run tcpdump for long enough for that amazing coincidence).

By the way, I can match any other bytes normally with ether[a:b] expressions, it's only the 12-15 bytes (VLAN ethertype and VLAN ID) that have bizarre behavior.

I strongly suspect this is due to rx_vlan_offload being enabled, but when I try to disable it with ethtool I get:

$ sudo ethtool -K eth1 rx-vlan-offload off

ethtool: bad command line argument(s)

For more information run ethtool -h

Edit: I found that 'ethtool -K <dev> rxvlan off' is the correct command, but disabling that didn't change the behavior.

This happens with both ixgbe driver version: 4.2.1-k (shipped with the CentOS kernel package), and also with version: 4.4.6 (built from source).

I found a reference to an extremely similar sounding bug here https://sourceforge.net/p/e1000/bugs/375/, but that seems to be a much earlier version of the driver. This one appears to check for RHEL_RELEASE_VERSION > 6.1 and enable 802.1P support accordingly:

#if (RHEL_RELEASE_CODE && RHEL_RELEASE_CODE >= RHEL_RELEASE_VERSION(6,1))

#define HAVE_8021P_SUPPORT

#endif

So two questions:

1. How can I resolve this issue of not being able to use ether[14:2] to match VLAN ID in BPF?

2. Why can't I disable rx_vlan_offload with ethtool? (it does not say [fixed])

Message was edited by: Chort Zero

Someone on Twitter showed me 'rxvlan' is ethtool's shorthand for rx-vlan-offload, but it doesn't make any difference after disabling it.

According to the spec update multiple 82574L controllers have an SMBus address conflict.

" 7. SMBus ARP Fails with Multiple Devices Because Different UDIDs Collide "

I'm guessing this is the reason that I can no longer access the control/status registers of either of my Ethernet controllers. I'd like to assign the address manually per the spec update but I cannot access the control registers. Every time I try I get the following error:

Port Network Address Location Series  WOL Flash Firmware Version

==== =============== ======== ======= === ================

  1   (Cannot initialize adapter)

  2   (Cannot initialize adapter)

Any suggestions on how to disable ARP when the adapter won't initialize?

Thanks!

Hi.

Is it possible to change mac address on virtual NICs associated with VLANs created under Windows 10 using last Intel drivers for i210?

I cant find the way to do it.

Thanks.

Hello,
We have a dual nic x520 on a hypervisor, and planning to use sr-iov and bridge as well.
Nics VF are working fine, however there is also a bridge (on a tagged vlan) on that host and the machines behind sr-iov vf cannot talk to machine in the bridge.
I turned off mac spoofing to no avail....

This is Centos 7.2 with all updates.
The reason for this is that not all machines require sr-iov functions/maintenance so some of them are used classically with a vnet on bridge.
Both machines (vf and bridged) are in the same vlan, I did a tcpdump session and I can see it does an ARP request but no reply

Any help would be appreciated, thank you

During installation of Intel Network Adapter Driver for Windows® 10 64-bit, this warning message appear. I installed it anyway but after a week, my Ethernet driver starts to crash randomly and gets stuck in restarting when i restart my PC.

What does this excatly mean?

Image may be NSFW.
Clik here to view.

@Having a problem with Intel Driver Update Utility giving me repeatedly the same driver version like "Intel Network Adapter Driver V 12.15.23.7" than I install it after when ready I restart my PC. When I see the Windows screen and I repeat to open application again with Intel Update Driver Utility it will give me again the same driver version "Intel Network Adapter Driver V 12.15.23.7" and again I will repeat and hangs again in the Utility!

I followed the log file directory and send you a screenshot report of it so maybe it will help you!

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

Can anyone help me with this question? Thank you!

Hi,

I am developer on Linux system.  I have develop network tunnel with bridging interface.  I found problem in throughput performance.  It looks like serial packet.  From bandwidth monitoring, i can see packet flow from eth0 to eth1 as serialize not pararell. It need traffic from eth0 down to lowest then eth1 raise the traffic forward.

How can i fix this problem? I have been looking in Interrupt Throttle Rate (ITR) from your guide in "Tuning Throughput Performance for Intel® Ethernet Adapters".  But it does not any effect.

Thank you,

suchot