Hi,

we're currently setting up new hardware with Linux (Devuan Ascii / Debian 9) on Atom Denverton SoC systems utilizing the X553 NICs.

While general networking seems to work just fine, our go-to method to identify the NICs by LEDs blinking (ethtool -p / --identify ethX) doesn't seem to do anything. The command is being accepted (on unsupported hardware we'd get a "Operation not supported"), but there's simply no blinking happening .

Various other Intel NICs in use (older chipsets using the e1000 or igb drivers, for example 82574L or I350) display the expected behavior. We've tried the newest drivers 5.3.7. as well as the ones shipped with our kernel of choice (4.16. from backports) - neither seem to work.

Are we doing it wrong? Any hints appreciated

Hi.

So my problems is that with latest version of windows VLANS dont activate they stay disabled state, reinstalling drivers does nothing and they are newest version from intels website.

Ou snap

Message was edited by: Tiit Talts

Hello,

I have MSI x299 sli plus with I211 and I219-V

and since 2 to 3 weeks of connection problems to know more reception or upload for about 0.1ms.

This happens on both network cards randomly 1h like 10 minutes I tried also to go on a 4G connection and ADSL same symptoms.

The update of the drivers in 23.2 does not change anything and a complete reinstallation of windows 10 pro no change.

it's very annoying in online games if you have solutions ..

My Environment:

Server: Fujitsu PRIMERGY RX2530 M4

Ethernet Adapters: Intel Ethernet Connection X722 LOM (Two SFP+ ports)

Ethernet Adapters Firmware: 3.51

--

ESXi: 6.5 U2

i40en driver version: 1.5.8

--

Both ethernet ports are connected to Juniper EX4550 Virtual Chassis (Junos version 12.3R9.4).

Switch ports are in trunk mode with native vlan.

--

After server boot up ESXi show only one X722 port which is online and port pass traffic. When I assign vlan tag to this interface (also changing ip addresses) then port is online but no traffic.

By default dcbx protocol is enabled on all switch ports:

set protocols dcbx interface all

I disabled dcbx protocol on ports where ESXi server is connected:

set protocols dcbx interface xe-0/0/15.0 disable

set protocols dcbx interface xe-1/0/15.0 disable

After server reboot ESXi show two X722 ports which are online and vlan tag assignment is working.

Is this the i40en driver problem?

Hi there,

we are experiencing problems with the X710 series R630 Intel NIC built-in within our Dell server (running ESXi version 6.5.0 / build number 7388607).

As for the i40en driver version:

   Driver Info:

         Bus Info: 0000:01:00:0

         Driver: i40en

         Firmware Version: 6.00 0x800034ef 18.3.6

         Version: 1.4.3

Just yesterday we had another outage with a lot of upset customer calls, so this issue is rather urgent. I have seen the blog entry for a i40en driver update for 6.7 installations, but that doesn't help our specific case.

Can you at least give us an ETA for the driver update for 6.5 installations? As mentioned above, it's pretty urgent as we can not have any more outages like yesterday. Please advise.

Thank you in advance!

Best

Tommy

When I try to install the newest NIC driver 23.2 on my Windows 1803 X64 system the system freezes just after the installation start. What goes wrong ?

hello,

I have a HP ZBook 15 laptop, where the "Intel(R) Ethernet Connection I217-LM" device is used for wired Ethernet. I also have two GO-SW-8G Dlink Gigabit switch (https://eu.dlink.com/se/sv/products/go-sw-8g-8-port-gigabit-dlinkgo-switch ). Below, I will call these SW1 and SW2, for better understanding. Also from the Internet Service Provider, we have 1 Gigabit/sec bandwidth (T-Home Magenta1 pack).

There are two scenarios what I setup and the 1Gbps speed was not able to work (?) in the laptop in one case.

The scenario-1, when the 1G speed was working:

The internet modem is connected with a standard LAN cable to the PORT-1 in of the SW1. The Ethernet interface in my laptop is connected to the PORT-2 in SW1 with a standard LAN cable. In this case the Ethernet interface LinkSpeed was Gigabit. It was possible to see both in the indicator LED of the PORT-2 in SW1 -this was green-, and also in the Windows when checking the LinkSpeed of the Ethernet interface, please refer to this link, Google Photos

So, in Gigabit speed point of view there is no any issue in this scenario.

The scenario-2, when the 1G speed was not working, and the LinkSpeed down set to 100Mbps:

Just similar to scenario-1, the internet modem is connected with a standard LAN cable to the PORT-1 in of the SW1. Now SW2 comes to the path, thus PORT-2 in SW1 is connected to PORT-1 in SW2 with a standard LAN cable. The Ethernet interface in my laptop is connected to the PORT-2 in SW2 with a standard LAN cable. In this scenario, the indicator LEDs on the Dlink switches are green, meaning 1G speed in all used ports, except the PORT-2 in SW2 which goes to the laptop. The indicator LED was orange of this port, also checking the LinkSpeed in the Windows side, that shows 100Mbps speed, please refer to this link, Google Photos

I have tried set manually the LinkSpeed in the Windows for the Ethernet interface to 1G, but in this case the interface was "disconnected", so the wired Ethernet was gone in the list of  connections in Windows and the laptop has started to use my WIFI NW.

When I changed back the interface LinkSpeed to "Auto", that come back to 100Mbps, and the "internet connection" returned to use the wired connection.

I did other test by using another Gigabit device, what was a Gigabit router from Dlink, and when I was connect one of the LAN interface of the router to the PORT-2 (or 3, or so) in SW2, the indicator LED was green, meaning the speed was 1Gbps.

Last week, I was issued a support ticket to Dlink, but finally they have not seen any issue with my setup in their pint of view, and also got the info from them, the scenario-2 was working very well with 1G in their LAB.

Thus now, I think the problem is not with the Dlink switches, but with the Windows and/or I217-LM device, and I would like to get some instructions, hints, ect from you, about doing some kind of troubleshooting to identify the root of the issue I have.

This morning I just refreshed the driver of the I217-LM to "Intel ® Network Connections Version:"22.9.6.0"", but I got the same result, so the expected 1Gbps LinkSpeed is not seen when both Dlink switches are in the path.

For more detail info about the drivers on my laptop, please refer to the attached text file.

Please try help me.

Thanks for your help,

/Robi

Hello everyone,

My desktop motherboard uses an Intel l211 network adapter and on Windows Pro 1803 (with the latest 23.2 driver, but also with 23.1) I've noticed that TCP Checksum Offload cannot be enabled at all via Device Manager -> Advanced Adapter Settings or Windows PowerShell.

On Advanced Adapter Settings, the options seem to be set to Disabled by default, but once I set them to something else and apply the settings, the window is closed, connection is lost for a few seconds, and once I open the Settings page once again, the options are back to Disabled.

Then, I tried using Enable-NetAdapterChecksumOffload on Windows Powershell, but when I try reading the new values with Get-NetAdapterChecksumOffload, I see everything set to Disabled.

Any ideas?

Thanks!

I have completed a scan on the Driver and support assistant and it has come back as no updates available.

I find this hard to believe as the Ethernet Connection I219-V is showing the driver date 18/03/2015.

I was happily surprised that intel have given this great tool for those that are not very tech savvy like me but I would really like it if it worked so that I can get everything up to date.

Any help appreciated.

Hello, I've been having trouble with this NIC not booting off of PXE.  I've already set the 10Gbe interface as a booting interface in the BIOS.  During PXE, I get the error message: PXE structure was not found in the UNDI driver code segment.  When it first didn't work, I used nvmupdate64e to update the NIC firmware.  nvmupdate now tells me my firmware is up to date (at version 6.01).  However, I still get the same exact error message at PXE boot.  I have also tried enabling PXE flash firmware for the interfaces.  But I still get the same error after all these driver installs and configuration enables. 

lspci -vv | grep -i 'Intel Corporation Ethernet Controller X710'

81:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)

81:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)

./bootutil64e

Port     Network Address     Location     Series     WOL     Flash Firmware          Version

3          6805CA385DF0      129:00.0     40GbE    N/A       UEFI,PXE Enabled     1.0.66

4          6805CA385DF1      129:00.1     40GbE    N/A       UEFI,PXE Enabled     1.0.66

ethtool -i eth2

driver: i40e

version: 1.5.10-k

firmware-version: 6.01 0x80003483 1.1747.0

bus-info: 0000:81:00.0

./nvmupdate64e

Num      Description                                                       Ver.      DevId     S:B          Status

01          Intel (R) I350 Gigabit Network Connection      1.99      1521      00:0001   Update not available

02          Intel(R) Ethernet Converged Network             6.01      1572      00:129     Up to date

              Adapter X710-2

Any idea what I need to do to get this interface to PXEboot?  eth2 is the interface that I am using.

Hi,

     I’ve come across a need to hotplug PCI devices between dom0 and domU using SR-IOV NIC. But I'm experiencing problems when trying to detach VF more than one PV guests.

I can attach VF  to DomU successful as follow:

# xl pci-assignable-list

0000:05:10.0

0000:05:10.2

# xl pci-attach 1 05:10.0

# xl pci-attach 2 05:10.2

But when I can't detach VF and it report errors as follow:

# xl pci-detach 2 05:10.2

libxl: error: libxl_device.c:1269:libxl__wait_for_backend: Backend /local/domain/0/backend/pci/2/0 not ready

And only 05:10.0 can detach successful :

# xl pci-detach 1 05:10.0

# xl pci-assignable-list

0000:05:10.0

Each guest config is the same like this:

name = "ubuntu-pv-1"

bootloader = "pygrub"

memory = 256

vcpus = 1

vif = [ 'bridge=xenbr0' ]

disk = [ 'file:/home/ye/ubuntu-pv/ubuntu-pv-1/ubuntu-pv-1.img,xvda,rw' ]

pci_permissive = 1

Follow xl dmesg log:

# xl dmesg | grep -i vt-d | grep -i enable

(XEN) Intel VT-d Snoop Control enabled.

(XEN) Intel VT-d Dom0 DMA Passthrough enabled.

(XEN) Intel VT-d Queued Invalidation enabled.

(XEN) Intel VT-d Interrupt Remapping enabled.

(XEN) Intel VT-d Shared EPT tables enabled.

# xl dmesg | grep "I/O virt"

(XEN) I/O virtualisation enabled

And libxl-driver log:

# cat  /var/log/libvirt/libxl/libxl-driver.log

xc: detail: sysctl operation failed -- need to rebuild the user-space tool set?

libxl: error: libxl.c:4364:libxl_get_physinfo: getting physinfo: Permission denied

xc: debug: hypercall buffer: total allocations:7 total releases:7

xc: debug: hypercall buffer: current allocations:0 maximum allocations:1

xc: debug: hypercall buffer: cache current size:1

xc: debug: hypercall buffer: cache hits:6 misses:1 toobig:0

I'm running in Ubuntu 14 using Xen-4.6. I have tested in other machine using the same environment but encountering the same problem.

Hello,

We have the same issue. We have 30 Huawei servers with Intel X710 card and vsphere 6.5 u1 patch2. VM network connections on a Distributed Virtual Switch seem to freeze after this error appears in vmware logs:

"2018-03-30T07:35:50.216Z cpu5:66200)i40en: i40en_HandleMddEvent:6495: Malicious Driver Detection event 0x02 on TX queue 0 PF number 0x00 VF number 0x00

2018-03-30T07:35:50.216Z cpu5:66200)i40en: i40en_HandleMddEvent:6521: TX driver issue detected, PF reset issued

2018-03-30T07:36:20.213Z cpu48:70776)WARNING: NetPort: 1934: failed to disable port 0x300000d on DvsPortset-0: Busy

2018-03-30T07:36:20.213Z cpu48:70776)netschedHClk: NetSchedHClkPortQuiesce:4918: vmnic1: received a force quiesce for port 0x300000d

2018-03-30T07:36:20.213Z cpu48:70776)netschedHClk: NetSchedHClkHashQuiesceHierarchyIter:396: vmnic1: dropped 501 pkts from queue netsched.pools.vm.50331661 while quiescing port 0x300000d"

After this, multiple Dvs ports fail and packets are dropped (vmnic1: dropped 501 pkts from queue).

This has happened on 3 ESXi servers already, causing downtime on VMs.

The logs show the same sequence of events on all 3 servers:

1. Malicious Driver Detection event
2. failed to disable port ___ on DvsPortset-0: Busy
3. vmnicx: dropped ___ pkts from queue

Only way to recover the VM networking is to vMotion to a different host.

I am attaching the vmkernel log file for this server. Issues start at 2018-03-30T07:35:50.216Z

We are really DESPERATED... We are working in big migration project and we are totally frozen!!!

We have tried to installed the last drivers "1.5.8" and the issue happends again.

NEED URGENT HELP!!!

I had a pair of I210 NICs (a dual-NIC motherboard) teamed via Static Link Aggregation and all was working fine until today when Windows 10 x64 decided to apply the April 2018 cumulative update. The page providing the respective drivers with ANS support (https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=64399) states that the latest version is 23.1 (dated 2018-02-21). Even with this latest driver, however, I can re-create the team, but it cannot be enabled. The only way to keep things in a sort of working state is to disable one of the NICs as well as the virtual team interface and keep only the other NIC active (i.e., not an ideal scenario).

Is there any chance that a new version of the driver will be available soon?

Thanks.

nvx

I am trying to set up VLANs on one of our PCs. That PC is based on a DG33FB motherboard with a 82566dc-2 NIC running Windows 10. The properties of the NIC show VLAN and Priority enabled but I unable to select the VLAN itself. I understand that that I need advanced network services ANS) installed with the NIC driver.

The driver now in use is a Microsoft one without the ANS support. So I downloaded the latest PROSET driver, ran it for it to report no Proset NIC found. So I tried a manual install unpacking the PROSET driver and set the install point to the PRO1000 folder and on trying to install it ended up with Windows report that the best driver was already installed. If I search the driver files I see this NIC listed in several .inf files in NDIS62 & 64 and if I select either of these (using pick from list option) I am presented with a list of models (I218-LM etc) but not my NIC.

Any help suggestions much appreciated.

hi.

can i use PCI EXPRESS INTEL QUAD LAN CARD 10/100/1000 Intel® Ethernet Server Adapter I350T4-V2 on windows 10 computer to accelerate the network comunication to the router?

Hi.

So my problems is that with latest version of windows VLANS dont activate they stay disabled state, reinstalling drivers does nothing and they are newest version from intels website.

Ou snap

Message was edited by: Tiit Talts

Hello,

We have a problem with eepromARMTool using it on Nvidia Jetson TX2.

We are using your 82574L Gigabit Network Controller integrated on Intel Gigabit CT DESKTOP ADAPTER (EXPI9301CTBLK). Our platform is based on Nvidia Jetson TX2 modul (https://www.nvidia.com/en-us/autonomous-machines/embedded-systems-dev-kits-modules/) and we use Nvidia Jetson TX2 Developer Kit with integrated PCIeX4 interface.

Currently, 82574L is connected to Nvidia Jetson Tx2 Developer Kit. Operating system on Jetson TX2 is Ubuntu 16.04, kernel version is Linux tegra-ubuntu 4.4.38-tegra.

We have built eepromARMTool application only by running make on source files which you have provided.

When we run app eepromARMTool without arguments we recived expected answer:

Intel(R) Eeprom ARM Tool ARM OTP Programming Tool

Provided under the terms of a CNDA. Do Not Distribute.

Copyright(C) 2013 by Intel(R) Corporation

NIC BUS DEV FUN Silicon Memory Type Present

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

1 1 0 0 82574 FLASH

But when run app in dump mode, it causes Bus error (core dumped):

Intel(R) Eeprom ARM Tool NVM/OTP Programming Tool

Provided under the terms of a CNDA. Do Not Distribute.

Copyright(C) 2013-2014 by Intel(R) Corporation

Version 0.6.7

Bus error (core dumped)

dmesg prints:

Unhandled fault: alignment fault (0x92000061) at 0x0000007f7b59e014

Any help will be appreciated.

Regards,

Ilija

I downloaded the latest nvm package (6.01) from this link.

Download Non-Volatile Memory (NVM) Update Utility for Intel® Ethernet Network Adapter 710 Series

When I run the program nvmupdate64e, I got the output saying "update not available" although it finds my version is older (5.05). How can I force the program to update to 6.01?

# ./nvmupdate64e

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.30.22.3

Copyright (C) 2013 - 2017 Intel Corporation.

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [

Num Description                               Ver. DevId S:B    Status

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

01) Intel(R) I350 Gigabit Network Connection  1.99  1521 00:002 Update not    

                                                                available

02) Cisco(R) Ethernet Converged NIC X710-DA4  5.05  1572 00:004 Update not    

                                                                available

03) Cisco(R) Ethernet Converged NIC           5.05  1583 00:006 Update not    

    XL710-QDA2                                                  available

Tool execution completed with the following status: Device not found

Press any key to exit.

# cat version.txt

v6.01

#

Hi,

we have Intel XL-710QDA2 2x 40G QSFP+ NIC (driver 2.2.4) and SR-IOV configured on top of it.

So far we are using two VFs (one per physical interface/PF) total and we would like to add additional VF to each PF.

Additional VF will be in separate VLAN, but it should have same MAC address. Is this supported setup?

Can we have two VFs with same MAC address (in different VLANs) on the same PF?

MAC addresses are configred staticaly using ip link commands and rc.local script.

OS is Ubuntu 16.04.3 LTS.

cat /etc/rc.local

#!/bin/sh -e

#

# rc.local

#

# This script is executed at the end of each multiuser runlevel.

# Make sure that the script will "exit 0" on success or any other

# value on error.

#

# In order to enable or disable this script just change the execution

# bits.

#

# By default this script does nothing.

echo 2 > /sys/class/net/enp6s0f1/device/sriov_numvfs

echo 2 > /sys/class/net/enp6s0f0/device/sriov_numvfs

ip link set enp6s0f0 vf 0 mac aa:bb:cc:aa:00:01 vlan 11

ip link set enp6s0f0 vf 1 mac aa:bb:cc:aa:00:01 vlan 31

ip link set enp6s0f1 vf 0 mac aa:bb:cc:bb:00:01 vlan 51

ip link set enp6s0f1 vf 1 mac aa:bb:cc:bb:00:01 vlan 71

exit 0

BR, Mate

This issue was covered here but was NOT resolved and mark answered by accident.

VLANs disabled in Windows 10 Build 17133.1 Version 1803

My steps were as follows

1. Ran fine with Windows 10 Ver. 1709 for months using multiple tagged VLANs and one untagged VLAN on Intel NUC NUC6i7KYK (aka Skull Canyon) and Intel i219-LM NIC.
2. Clean installed Windows 10 Build 17133.1 Version 1803 with latest Drivers from Intel.
3. Recreated all my tagged VLANs only to find they were all DISABLED.
4. Permanently removed Intel NIC 23.1 driver and installed previous Intel NIC 22.9 driver with no luck still.
5. Clean installed Windows 10 Ver. 1709 with Intel NIC 23.1 driver.
6. Recreated all my tagged VLANs and BAM they all worked like normal.

In conclusion, the latest Intel NIC driver 23.1 seems fine but there is something wrong with Windows 10 Build 17133.1 Version 1803 Springs Creators Update, aka Redstone 4.