Hello All
Please help
A customer has several servers with Intel(R) Ethernet 10G 2P X520 Adapter NICs.
They want to connect to Cisco Meraki 425 10gb switches. The documentation is not clear, can we use twinax cables to connect between the meraki switch and the Intel x520 NICs instead of buying lots of separate 10gb sfp and cables?
Thanks
IAN I218 V connection in Windows 10, 64bit, i-5, 4590 processor. is slow. Do I upgrade to I219 -V?, ASUS Z-97E motherboard?
or this guide is private? not for every developer to use?
I recently converted a freeNAS server to a Windows 10 x64 Pro box which has a Supermicro MOBO with onboard dual i210AT adapters. I had no problem configuring aggregation in freeBSD, but have been stumped on how to do the same in Windows 10. After searching various forums, etc, I see that in some cases there is a "Teaming" tab which appears in the Properties window of the controller. Unfortunately, that tab is not there when I attempt the same.
The current driver for both controllers is shown to be: 12.15.184.0 dated 3/29/2017
Any assistance is appreciated.
Thanks
Hello,
I am using the newest driver for the Intel I219-LM network adapter in Windows 7. I need to change the size of the receive and
transmit buffers to:
Receive buffers : 512
Transmit buffers: 128
I can’t seem to find the option to change the parameters !
For the Intel 82579LM the option is easily available under the “advanced tab” for “network connection properties”.
Any suggestions?
Thanks
Regards
Jonas
Hi,
I have a bunch (actually around 50 boards) of Intel X710-DA2 adapters, and similar number of servers running ESX 6.0. The problem is: as soon as the server starts exchanging the traffic using X710, it reboots. Why I'm writing here instead of the VMWare support: because when the adapter stays idle (we use onboard copper gigabit i350 adapters to mitigate the issue), the server is rock stable. When using the Mellanox ConnextX-3 EN boards (recently we aquired a couple for testing purposes) the server doesn't crash either. So I'm quite sure either it's the board or it's driver.
As about the Intel drivers for ESX: the problem is persistent across all available versions of the driver from 1.2.48 to 2.0.6 (we also tried the 1.4.28 in the middle). The NVM firmware version also doesn't seem to solve this - today we performed the tests on the 5.05 firmware, with 2.0.6 drivers - and the uptime was just a couple of minutes before server rebooted. I've also tried to disable TSO and LRO, but this didn't change the result.
I would appreciate greatly if someone will help me to mitigate this issue, because right now the only possible solution for us is switching to the Mellanox boards, which is quite expensive, as the server number is way big.
Thanks.
Hello,
my situation is the following: I’ve got two tagged VLANs coming to my notebook via Ethernet connected to my Intel I217-LM Ethernet adapter.
Using device manager and the VLANs tab within the configuration window of the Ethernet adapter, I have configured both VLANs and two new disabled Ethernet adapters showed up in the adapter settings of windows. In the adapter settings of the physical Ethernet adapter, the item “Internet Protocol Version 4 (TCP/IPv4)” has been automatically unselected and “Intel® Advanced Network Services Protocol” has been automatically selected. So far so good, but I cannot enable the two new virtual Ethernet adapters corresponding two the two VLANs. If I try, a small windows pops up showing “Enabling…” and after a few seconds it switches two “Enabled” and disappears a couple of seconds later. Unfortunately, the two virtual NICs stay greyed out and dont work.
I am using Windows 10 version 1703, driver version 12.15.23.9 for my I217-LM NIC and driver Version 9.9.0.53 for the virtual NICs. I have already tried reinstalling the driver, which unfortunately did not work…
When the virtual NIC is created, an error is logged in the Windows Event log:
Type: System
Source iANSMiniport
Event ID 4
Basically telling me that binding to the physical adapter failed and that I should deleted the adapter group and create a new one which is weird, as I haven’t created an adapter group yet…
While looking for drivers, I noticed that older drivers in the list (Downloads for Intel® Ethernet Connection I217-LM) mentioned that this feature is not available under Windows 10. However, the most recent version does not so I assumed that this has been fixed. Is it?
Any help or idea is appreciated, thank you!
With best regards
A.G.
OK, I'm running CentOS Linux 6.9 x86_64, on a ASUS MB with a Intel Core I7-5820(?) with 64 GB RAM. My storage is 2 - 120 GB PNY SSD and 2 - WD 4TB Black with everything setup as software raid1.
I've been having some hardware error issues and the machine would terminate, so this came up after almost all of those errors were corrected.
On a warm boot (i.e. after upgrading from 6.8 to 6.9) I noticed that I'm getting a message 'Initialization Delayed) on the NIC card which causes the virtualization to fail (ifcfg-br0 and ifcfg-br1 are assigned to ports 3 and 4 on the 82571 NIC). Everything works just great on a cold boot.
What can I do to correct this? Is there a parameter I can set to get this to work on a warm boot? Should I remove this card and get a replacement? What should I replace it with?
TIA
Gene
Hi,
My company is using E10G41BFSR and I need to know the MTBF.
Thank you.
Our deployment system has been installing Intel network drivers for years using this approach:
Unzip "PROWinxXX ver XX.exe" and then running the appropriate DXSetup.exe (or setupBD for older versions) with the /qr argument.
This is in a way also working for 22.0.1... but after installation the "We invite you to join the Intel Product Improvement Program" popup appears, and deployment halts.
How do I suppress this popup during silent install?
Thanks,
How can I configure the i210-T1 nic in order to enable AVB streaming in win10?
We have experienced three occurrences on two servers of this error "tx_timeout" / "hung_queue", and packets stopped flowing for some number of seconds (but then recovered):
Apr 10 02:04:14 node39 kernel: WARNING: at net/sched/sch_generic.c:297 dev_watchdog+0x276/0x280() Apr 10 02:04:14 node39 kernel: NETDEV WATCHDOG: p2p1 (i40e): transmit queue 8 timed out ... Apr 10 02:04:14 node39 kernel: CPU: 0 PID: 0 Comm: swapper/0 Tainted: G OE ------------ 3.10.0-514.6.1.el7.x86_64 #1 Apr 10 02:04:14 node39 kernel: Hardware name: Dell Inc. PowerEdge R620/01W23F, BIOS 2.1.3 11/20/2013 ... Apr 10 02:04:14 node39 kernel: i40e 0000:42:00.0 p2p1: tx_timeout: VSI_seid: 390, Q 8, NTC: 0x113, HWB: 0x116, NTU: 0x116, TAIL: 0x116, INT: 0x1 Apr 10 02:04:14 node39 kernel: i40e 0000:42:00.0 p2p1: tx_timeout recovery level 1, hung_queue 8 Apr 10 02:04:14 node39 kernel: i40e 0000:42:00.0 p2p1: adding 3c:fd:fe:9f:b7:48 vid=0
This is within first 3 weeks of usage of Intel X710 duo adapters running firmware 4.53 (with supported Intel SFP+) recently installed in a cluster of two-year-old Dell R620s, running CentOS 7.3:
node39:/# lspci -vv | grep -A 1 10GbE pcilib: sysfs_read_vpd: read failed: Input/output error 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Intel Corporation Ethernet Converged Network Adapter X710-2 -- 05:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Intel Corporation Ethernet Converged Network Adapter X710 -- 42:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Intel Corporation Ethernet Converged Network Adapter X710-2 -- 42:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Intel Corporation Ethernet Converged Network Adapter X710 node39:/usr/local/bin# ethtool -i p2p1 driver: i40e version: 1.5.10-k firmware-version: 4.53 0x8000206e 0.0.0 expansion-rom-version: bus-info: 0000:42:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes
We have used X710s without issue in a few other servers, but in those cases they are HP OEM, and running firmware 4.60:
node93:/# lspci -vv |grep -A 1 10GbE 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Hewlett-Packard Company HP Ethernet 10Gb 2-port 562FLR-SFP+ Adapter -- 04:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Hewlett-Packard Company Ethernet 10Gb 562SFP+ Adapter -- 05:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Hewlett-Packard Company HP Ethernet 10Gb 2-port 562SFP+ Adapter -- 05:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01) Subsystem: Hewlett-Packard Company Ethernet 10Gb 562SFP+ Adapter node93:/# ethtool -i ens2f0 driver: i40e version: 1.5.10-k firmware-version: 4.60 0x80001f47 1.3072.0 expansion-rom-version: bus-info: 0000:05:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes
I have downloaded nvmupdate64e and updated a spare Dell to firmware 5.05, so if this is the correct solution I have confirmed the procedure. However threads such as this one Intel X710 vs VMWare ESX: crash and reboot give me pause-- crash and reboot would certainly be worse than a 10-20 second transmit hang.
My questions are:
Thanks in advance!
iQV driver is the backend driver for supporting the firmware(actually the flash) download tools on intel Ethernet adapter cards. eeupdate and lanconf tools use the iqv driver.
I am trying to rebuild this driver, and once I successfully build this driver, after I load this iqv module into Linux, I'm getting this message from both these tools.
I'm using the latest version of 1.2.0.4 of iqv driver.
However the older driver (version: 1.1.4.17) with the older tools works fine.
Anyone has any idea why this eeupdate or lanconf complaining about this message: Connection to QV driver failed - please reinstall it!
Thanks
Kongkon
Hello guy in those days i got 30 megabyte connection from my provider. And it works good on all my pc's with the same cable. the other devaices dont have a intel network driver and it works perfectly. any fix ?... My Motherboard is ASROCK H97M Pro . I've tried everything . I Don't know how to fix it im using Intel(R) Ethernet Connection (2) I218-V.
Gyazo - f0ce19c4bacee4c7533492943380d51d.png
Intel(R) Ethernet Connection (2) I218-V automatic negotiation doesnt let me use my 30megabyte connection but just 10. How to fix?
Hi,
My company is using I350T2V2 and I need to know the MTBF.
Thank you.
The eeupdate and the lanconf tool is not working. These tools need the IQV driver. However once I load the latest driver, these tools errors out with the following messages:
Connection to QV driver failed - please reinstall it!
This output is with the older iqv driver version: 1.1.4.17
[root@xrsdev29 ~]# ./lanconf64e /VERSION
Connection to QV driver failed - please reinstall it!
Using: Intel (R) PRO Network Connections SDK v2.28.29
LANConf v1.28.29.03
Intel(R) Diagnostic Tool for PRO Series Ethernet adapters
Copyright (C) 2006 - 2017 - 2017 by Intel (R) Corporation. All rights reserved.
Intel (R) Confidential and not for general distribution.
[root@xrsdev29 ~]#
Now, if I run the older tool, it does not complain. However, in both these cases the lanconf tool should have complained, as the iqv driver is not loaded in either of these cases.
root@xrsdev29 ~]# ./STX_3PF_UTIL_106/util/intel/lanconf /VERSION
Using: Intel (R) PRO Network Connections SDK v2.24.33
LANConf v1.24.33.07
Intel(R) Diagnostic Tool for PRO Series Ethernet adapters
Copyright (C) 2006 - 2015 by Intel (R) Corporation. All rights reserved.
Intel (R) Confidential and not for general distribution.
[root@xrsdev29 ~]# lsmod |grep iqv
[root@xrsdev29 ~]#
After I load the iqv driver (latest):
[root@xrsdev29 ~]# modinfo iqv
filename: /lib/modules/3.10.0-327.36.3.el7.0.1.63.xl7.x86_64/weak-updates/iqv/iqv.ko
version: 1.2.0.4
license: GPL
description: 1.2.0.4
author: Intel Corporation
rhelversion: 7.2
srcversion: EBD18E94CC97F7B1A7F08EF
depends:
vermagic: 3.10.0-327.28.2.el7.0.1.29.xl7.x86_64 SMP mod_unload modversions
[root@xrsdev29 ~]#
Driver version do not match, please reinstall driver
[root@xrsdev29 ~]# ./lanconf64e /VERSION <------- New lanconf tool came with iqv driver. It still complains after loading the iqv driver
Connection to QV driver failed - please reinstall it!
Using: Intel (R) PRO Network Connections SDK v2.28.29
LANConf v1.28.29.03
Intel(R) Diagnostic Tool for PRO Series Ethernet adapters
Copyright (C) 2006 - 2017 - 2017 by Intel (R) Corporation. All rights reserved.
Intel (R) Confidential and not for general distribution.[root@xrsdev29 ~]#
So, why the latest IQV driver does not work with the latest eeupdate and lanconf tools, whereas older driver with older tools works!
Thanks
Kongkon
Is there any reason we aren't getting Intel Windows 10 drivers for these cards?
The fact that were forced to use Windows 10 and cant using the teaming features of a high grade dual gigabit NIC is a bit crazy.
Windows 8 has drivers from March 2017, and yet we still lack Window 10 drivers.
Are they working on this, or have we just bitten the dust and have to dish out 150$ for a new dual gigabit NIC?
Hello:
This is Vincent from AEWIN.We should have one new model name of PC/104 CPU Module(Our SOC belongs to DMP DX3-9126 CPU).But we found out that we could not installed the Ethernet driver for the Intel I211AT/I211IT under MS Windows 7 OS
Hi all,
I'm trying the iSCSI Boot by the Intel i350 NIC card.
The card has the agent ROM and can connect to my iSCSI target server by 'Primary iSCSI'.
All work fine in Grub2 menu.
But, when initrd was loaded, the command 'blkid' cannot see any iSCSI driver which can be boot.
The version of Linux kernel is '4.4.0-28-generic'.
The kerenl and initrd is copy from a machine which is installed by LiveCD on a local drive.
The initrd doesn't have kernel module 'iscsi_ibft'.
Is the module necessary for booting from iSCSI target?
Does the iSCSI drive act as a local drive when initrd scan the scsi bus?
Thanks.