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 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
Hi,
I am using network performance measurement tool nuttcp with IGB and E1000 cards on one of my development boards.
Issue: Observed crash/watchdog bite using testing with both IGB and E1000 cards.
Kernel: kernel_msm-3.18
Steps to reproduce.
1.) On device: ./nuttcp-8.1.4.arm -S
2.) On PC side run below command xxx.xx.xxx.xxx -> IP address of device.
./nuttcp-8.1.4.x86 -w2m -u -R 160M -i 1 -T 1m xxx.xx.xxx.xxx
3) After a couple of iterations we see the crash reported in the log.
IGB Log
------------------
Parsing debug information for MSM_DUMP_DATA_CPU_CTX. Version: 20 Magic: 42445953 Source:
Parsing CPU1 context start 171c8a800 end 171c8b000
Core 1 PC: arch_counter_get_cntvct+1c <ffffffc000a25164>
Core 1 LR: arch_counter_get_cntvct+1c <ffffffc000a25164>
[<ffffffc000a25164>] arch_counter_get_cntvct+0x1c
[<ffffffc000352ca0>] __delay+0x24
[<ffffffc000352c74>] __const_udelay+0x24
[<ffffffc00049235c>] msm_trigger_wdog_bite+0xd0
[<ffffffc0000f1d0c>] spin_bug+0x94
[<ffffffc0000f1e7c>] do_raw_spin_lock+0x104
[<ffffffc000eb38a0>] _raw_spin_lock+0x28
[<ffffffc000710768>] igb_get_stats64+0x30
[<ffffffc000cb8244>] dev_get_stats+0x4c
[<ffffffc000d249f8>] iface_stat_fmt_proc_show+0x98
[<ffffffc0001e77e0>] seq_read+0x18c
[<ffffffc000222874>] proc_reg_read+0x8c
[<ffffffc0001c5fcc>] vfs_read+0xa0
[<ffffffc0001c6758>] SyS_read+0x58
[<ffffffc0000864b0>] el0_svc_naked+0x24
From the code, it looks like it could be stuck in igb_update_stats and so the unlock might not be happening in time.
Code file:/kernel_msm-3.18/kernel/drivers/net/ethernet/intel/igb/igb_main.c
5160static struct rtnl_link_stats64 *igb_get_stats64(struct net_device *netdev,
5161 struct rtnl_link_stats64 *stats)
5162{
5163 struct igb_adapter *adapter = netdev_priv(netdev);
5164
5165 spin_lock(&adapter->stats64_lock);
5166 igb_update_stats(adapter, &adapter->stats64);
5167 memcpy(stats, &adapter->stats64, sizeof(*stats));
5168 spin_unlock(&adapter->stats64_lock);
5169
5170 return stats;
E1000 Log
-------------
[ 100.703446] init: Service 'atfwd' (pid 765) exited with status 255
[ 100.708673] init: Service 'atfwd' (pid 765) killing any children in process group
[ 104.343224] init: Untracked pid 2636 exited with status 0
[ 133.202677] BUG: spinlock lockup suspected on CPU#0, kworker/0:3/986
[ 133.208030] lock: iface_stat_list_lock+0x0/0x18, .magic: dead4ead, .owner: NetworkStats/1294, .owner_cpu: 1
[ 133.217936] Causing a watchdog bite!
[ 133.345512] Backtrace for cpu 1 (current):
[ 133.348758] CPU: 1 PID: 1294 Comm: NetworkStats Tainted: G W 3.18.31-g12d3836-dirty #2
[ 133.357697] Hardware name: Qualcomm Technologies, Inc. APQ8096v3 + PMI8994 DragonBoard (DT)
[ 133.366028] Call trace:
[ 133.368473] [<ffffffc000089d9c>] dump_backtrace+0x0/0x278
[ 133.373843] [<ffffffc00008a034>] show_stack+0x20/0x28
[ 133.378884] [<ffffffc000e70b08>] dump_stack+0x9c/0xd4
[ 133.383914] [<ffffffc000093700>] arch_trigger_all_cpu_backtrace+0x6c/0xdc
[ 133.390687] [<ffffffc0000f1e80>] do_raw_spin_lock+0x108/0x160
[ 133.396415] [<ffffffc000e7f428>] _raw_spin_lock+0x28/0x34
[ 133.401800] [<ffffffc0006d2de0>] e1000e_get_stats64+0x44/0x118
[ 133.407614] [<ffffffc000c83140>] dev_get_stats+0x4c/0xac
[ 133.412907] [<ffffffc000cef8f4>] iface_stat_fmt_proc_show+0x98/0x198
[ 133.419243] [<ffffffc0001e77e0>] seq_read+0x18c/0x3b4
[ 133.424277] [<ffffffc000222874>] proc_reg_read+0x8c/0xb4
[ 133.429571] [<ffffffc0001c5fcc>] vfs_read+0xa0/0x14c
[ 133.434520] [<ffffffc0001c6758>] SyS_read+0x58/0x94
cheers,
mohit
Using an updated driver, I cannot seem to get my interfaces up. Looks like the driver is not allowing the NIC to work due to the SFP+ module type, which worked previously on my Debian Stretch host. Clearly the NIC is detecting and reading the DAC, but I don't understand why it is not working. This is a 40G-breakout cable with 40-to-4x10G SFP+ DAC (TwinAx). I have tried adding the following to work around it, but it still does not work:
root@lab4:~# cat /etc/modprobe.d/i40e.conf
options i40e allow_unsupported_sfp=1
This was also discussed here, but there was no followup:
Intel Ethernet Drivers and Utilities / Mailing Lists
Output from dmesg:
[ 4.439190] i40e 0000:08:00.3: PCI-Express: Speed 8.0GT/s Width x8
[ 4.447918] i40e 0000:08:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 8 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA
[ 4.453414] i40e 0000:08:00.2: Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected.
[ 4.465288] i40e 0000:08:00.2: Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules.
Other pertinent output:
root@lab4:~# ethtool -m eth6
Identifier : 0x03 (SFP)
Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID)
Connector : 0x21 (Copper pigtail)
Transceiver codes : 0x00 0x00 0x00 0x00 0x00 0x04 0x00 0x00
Transceiver type : FC: Copper Passive
Encoding : 0x00 (unspecified)
BR, Nominal : 10300MBd
Rate identifier : 0x00 (unspecified)
Length (SMF,km) : 0km
Length (SMF) : 0m
Length (50um) : 0m
Length (62.5um) : 0m
Length (Copper) : 3m
Length (OM3) : 0m
Passive Cu cmplnce. : 0x01 (SFF-8431 appendix E) [SFF-8472 rev10.4 only]
Vendor name : Amphenol
Vendor OUI : 78:a7:14
Vendor PN : 624400003
Vendor rev : A
Option values : 0x00 0x00
BR margin, max : 0%
BR margin, min : 0%
Vendor SN : APF13470035GDT
Date code : 131122
root@lab4:~# ethtool -i eth6
driver: i40e
version: 2.4.3
firmware-version: 6.01 0x800034af 1.1747.0
expansion-rom-version:
bus-info: 0000:08:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
root@lab4:~# ethtool eth6
Settings for eth6:
Supported ports: [ ]
Supported link modes: Not reported
Supported pause frame use: Symmetric
Supports auto-negotiation: No
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: Unknown!
Duplex: Unknown! (255)
Port: Other
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: d
Wake-on: d
Current message level: 0x0000000f (15)
drv probe link timer
Link detected: no
root@lab4:~# ip link show eth6
5: eth6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
link/ether 68:05:ca:2f:7c:b0 brd ff:ff:ff:ff:ff:ff
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.
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.
Hello
I have a strange problem, I have an X710-DA4 card that works very well on a hp ProLiant DL380 Gen9 server
in 2012 r2 Intel (R) Xeon (R) CPU E5-2620 v3 @ 2.40GHz
The card has a strange behavior on hp ProLiant DL360p Gen8 with Intel (R) Xeon (R) CPU E5-2650 v2 @ 2.60GHz, whether in 2016 or 2012 r2 server and doing a new install, on the 4 ports I have a port that creates me BSOD, can not update the driver
if i boot on a livecd ubuntu desktop, my 4 network cards works well.
The card posing the problem has the FrindlyName "Intel (R) Ethernet Converged Network Adapter X710-4"
Is it a prerequisite related to the processor? The prerequisite for this card is just pcie 3.0.
I would like to understand why on 4 cards, 3 work normally and not the 4th.
Thanks in advance Julien
I've seen this posted on the forum a number of times, but there has been no posted solution. i have two know good 710 based network cards that have had their SPI flash chip replaced with a blank one. Now both cards are unable to be flashed with using the nvm utility. does anyone know the root cause of this? i am assuming since there is no firmware running from the SPI flash, that the nvm tool can not be used. does this mean that the SPI flash needs to be programmed manually?
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) Ethernet Controller XL710 154B 00:001 Access error
Generic ID
Tool execution completed with the following status: Device not found
Press any key to exit.
Hi,
under the firmware version info, what does all three fields indicates.i think first one is firmware version, second one is ETrakID, What does the third field indicate ?
driver: i40e
version: 1.3.46.1
firmware-version: 5.05 0x80002927 1.1313.0
bus-info: 0000:08:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
I am planning to upgrade the firmware version to "5.40 0x80002d35 18.0.17", but i am not able to get the file. Is this specific to any vendor or any dependencies ?
-
Vishruth
Hello,
The full product name is:
Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
I have a weird problem. My Intel card always shows Auto-negotiation : off .
1) Confirmed network switch is set to on;
2) When I set it manually, it prompted error:
[root@auspldccasssb01 ~]# ethtool -A em1 rx on tx on autoneg on
rx unmodified, ignoring
tx unmodified, ignoring
Cannot set device pause parameters: Operation not supported
[root@auspldccasssb01 ~]# ethtool em1
Settings for em1:
Supported ports: [ FIBRE ]
Supported link modes: 1000baseT/Full
10000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: 1000baseT/Full
10000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: external
Auto-negotiation: off
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
[root@auspldccasssb01 ~]# ethtool -i em1
driver: i40e
version: 1.6.27-k
firmware-version: 6.00 0x8000374f 18.5.17
expansion-rom-version:
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
[root@auspldccasssb01 ~]# uname -r
3.10.0-693.11.6.0.1.el7.x86_64
Hi ,
Can anyone tell me xl710 support win2k16?
thanks,
mashime
Hi Dan,
Thank you for the information. Can you tell me how many VFs are supported by XL710?
thanks,
mashime
Hi,
I am using SR-IOV on an i350 interface on a Linux machine and, even though I mainly need Virtual Functions (VFs) in PCI-passthrough mode, I would also like to be able to use VFs as regular interfaces in openvswitch (OVS) switches.
For instance, here's a simple setup with SR-IOV in PCI-passthrough. A VM communicates to an external machine through VF0 in PCI-passhtrough:
[VM] <-> [VF0] <-> [external machine]
If the PF is connected through a cable to another machine, I can ping this other machine successfully from the VM.
Now, if I remove the PCI-passthrough link and replace it with an OVS switch that contains the VM interface and VF0, I cannot ping the external machine from the VM:
[VM] <-> [ OVS switch ] <-> [VF0] <-> [external machine]
I suppose that this is related to some MAC address checking going on at the VF level. One workaround I found is to assign to the VM interface the same MAC address as VF0, but clearly this is not a scalable solution. Disabling spoof checking on the host on VF0 doesn't do the trick ($ ip link set eth7 vf 1 spoofchk off).
I know that I could just replace VF0 with the corresponding PF and it would work, but is there any additional step to take to make my setup work?
Hi, we have been redirected here from this thread in the embedded community: ARM tools for 82574 |Embedded Community
To summarize the important parts of our previous discussion, we have an Intel EXPI9301CT Gigabit CT PCI-e Desktop Adapter, which has an 82574 controller and a Winbond W25X40BVNIG flash. We are trying to use the eepromARMtool to reprogram the MAC address in the flash.
Running ./eepromARMtool -dump -NIC=1 gives us a file whose first line is:
8888 8888 8887 0C20 F746 2014 FFFF FFFF
We want to change the MAC address, so we edit the file that was dumped and change the first line to:
70B3 D501 C307 0C20 F746 2014 FFFF FFFF
Then we run ./eepromARMtool -write -NIC=1 -f=new_mac.otp. If we run the dump command again, the flash appears to have the correct contents. However, if we reboot or power cycle the machine and dump again, the output has returned to its original contents. This seems to imply that our changes were not actually flushed to the flash.
Do you have any advice for how to fix this problem? Thank you!
Vendor: 8086 DevID: 105E C57721-005
PS C:\Intel23.2\APPS\BootUtil\winx64> .\bootutilw64e -IV
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.6.59.0
Copyright (C) 2003-2017 Intel Corporation
Image versions in BootIMG.FLB
Combo Image Version Name 1.1927.0
Combo Rules v4.68.00
Clp-Loader Option ROM v3.0.90
40G Interface Module v1.0.53
iSCSI Option ROM v3.1.30
iSCSI Setup Option ROM v3.1.30
FCoE Option ROM v1.8.29
Intel(R) Boot Agent FE v4.2.08
Intel(R) Boot Agent GE v1.5.86
Intel(R) Boot Agent XE v2.4.19
Intel(R) Boot Agent XE (X550) v2.4.19
Intel(R) Boot Agent I40E v1.0.66
Intel(R) Boot Agent CL v0.1.13
UEFI x64 PCI gigabit driver v3.5.22
UEFI x64 PCI-E gigabit driver v8.3.10
UEFI x64 10 gigabit driver v6.7.10
UEFI x64 40 gigabit driver v3.0.11
UEFI IA64 PCI gigabit driver v3.5.22
UEFI IA64 PCI-E gigabit driver v8.3.10
UEFI IA64 10 gigabit driver v6.7.10
UEFI IA64 40 gigabit driver v3.0.11
OCD Option ROM v0.9.04
UEFI x64 FCoE Driver v1.2.21
Port Network Address Location Series WOL Flash Firmware Version
==== =============== ======== ======= === ============================= =======
1 001517A767BE 2:00.0 Gigabit NO PXE 1.5.86
2 001517A767BF 2:00.1 Gigabit N/A PXE 1.5.86
PS C:\Intel23.2\APPS\BootUtil\winx64> .\bootutilw64e -up=iSCSI -nic=1
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.6.59.0
Copyright (C) 2003-2017 Intel Corporation
ERROR: Flash too small for the image
Hey guys! Recently built a new PC. Haven't had any issues, but all of a sudden my Ethernet port stopped working today. My on-board wifi works fine, and I tried a different cable (which didn't work), so I know it isn't my internet. After doing some research online, I read that I needed to install the latest Intel network drivers. (Which makes sense, but why would it work and then stop working randomly?)
After downloading the Intel Network Adapter Driver for Windows 10, I ran the program. It has been about an hour, and the installer wizard is still trying to install the driver. However, the status bar hasn't moved an inch. It has been grey the whole time. Now, in my Windows 10 settings menu, I don't even have an option for ethernet. Only wifi.
I am new to the PC/windows realm after switching from Mac, and this issue is driving me nuts. I don't want to force quit the install wizard, as I know force quitting driver installs can cause issues.
Has anyone come across this issue before? Any ideas on what I can do?
I have a ROG STRIX Z370-E motherboard, and an I7-8700k processor if that information is of any help.
Thank you!
Hi ,
We upgraded firmware of X710-DA2 (EtrackID was added into .cfg file ) and after that card shows access error , how to recover it ?
Server : ProLiant DL380 Gen10
OS : 14.04.1-Ubuntu , 3.16.0-77-generic (our internal requirement )
NICs : HPE Ethernet 10Gb 2-port 562FLR-SFP+ Adapter (Embedded )
Intel(R) Ethernet Converged Network Adapter X710 (Field Replacable)
What we have done :
1. Upgraded driver to 2.4.10
2. Tried NVMUpdatePackage , it displayed update not available.
3. After looking at couple of forum threads for same issue ,we added EtrackID to the nvmupdate.cfg and tried again , upgrade failed with error .
4. After system reboot , ports are not showing in ifconfig .
Vendor ID IS : 8086 , DEVID is : 5172 , used in PCIe 3.0, x8
sudo lspci | egrep -i --color 'network|ethernet'
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
02:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
02:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01)
13:00.0 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)
13:00.1 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)
5d:00.0 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)
5d:00.1 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 Adapter (rev 01)
admin@versa-flexvnf: ~] # ethtool -i eth4
driver: i40e
version: 0.4.10-k <<<< First updated Driver .
firmware-version: f5.60 a1.5 n05.60 e800033b1 <<<<
bus-info: 0000:5d:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no
[admin@versa-flexvnf: ~] # sudo ethtool -i eth4
driver: i40e
version: 2.4.10 <<<<<<< Driver update ok
firmware-version: 5.60 0x800033b1 1.1752.0 <<<<<<<<
bus-info: 0000:5d:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
[admin@versa-flexvnf: Linux_x64] # sudo ./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) Ethernet Converged Network 4.65 1572 00:019 Update not
Adapter X710 available
02) HPE Ethernet 10Gb 2-port 562FLR-SFP+ 5.96 1572 00:093 Update not
Adapter available
We looked at forum for possible reason for displaying Update not available and found EtrackID is not available at nvmupdate.cfg , we added our EtrackID to the list .
800033B1 was added as shown below .
605 BEGIN DEVICE
606 DEVICENAME: XL710
607 VENDOR: 8086
608 DEVICE: 1572
609 NVM IMAGE: X710DA2_6p01_CFGID7p2_OEMGEN.bin
610 OROM IMAGE: BootIMG.FLB
611 EEPID: 80003483
612 REPLACES: 8000191B 80001920 80001DC0 80001F54 80001FA4 80002282 8000206E 800024C6 8000252E 8000252F 80002530 80002892 80002927 80002928 80002929 80002C44 800033B1
613 EEPROM MAP: PF_Alloc_WOL_DIS.txt
614 RESET TYPE: REBOOT
615 END DEVICE
[admin@versa-flexvnf: Linux_x64] # sudo ./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) Ethernet Converged Network 4.65 1572 00:019 Update not
Adapter X710 available
02) HPE Ethernet 10Gb 2-port 562FLR-SFP+ 5.96 1572 00:093 Update
Adapter available
Options: Adapter Index List (comma-separated), [A]ll, e[X]it
Enter selection:A
Would you like to back up the NVM images? [Y]es/[N]o: Y
Update in progress. This operation may take several minutes.
[****|.....]
Tool execution completed with the following status: An error occurred when updating a firmware module
Press any key to exit.
We rebooted device after failure and found ports are not coming and check the update again .
[admin@versa-flexvnf: Linux_x64] # sudo ./nvmupdate64e
[sudo] password for admin:
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) Ethernet Converged Network 4.65 1572 00:019 Update not
Adapter X710 available
02) HPE Ethernet 10Gb 2-port 562FLR-SFP+ 1572 00:093 Access error <<<<<<<<<<<<
Adapter
Options: Adapter Index List (comma-separated), [A]ll, e[X]it
Enter selection:X
Is there a way to recover the card back ?
Thanks,
Sai Chandra .
I recently got a new mobo, and upon installing win 10, i discovered the driver mentioned in the title (Intel(R) Ethernet Connection (7) I219-V) is not functioning properly.
It has no connection what so ever.
I have tried to update the driver in the following ways:
Mobo disc
Mobo manufacturer's site
Intels driver download site
Windows device manager
Even after the attempted updates, it still doesn't work. I have tried resetting my CMOS, and it did not have any effect.
Attempting to uninstall the driver is unsuccessful, as it automatically returns.
The LAN port itself when plugged in has LED's flashing.
The LAN controller is enabled/activated in my BIOS.
My BIOS has been flashed to the newest version.
I have windows 10 updated.
Even Intel's own driver updater doesn't do anything for me.
The error code I get from the device is:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
The mobo in question is the MSI B360 Gaming Plus
Is it a possibility that the mobo is faulty? The board is new, and other than the described issue, it works perfectly fine.
Hi
I'm trying to set a local or remote loopback to my adapter.
this is the result
/i40e-2.4.10/src$ sudo ethtool -t enp1s0f0 external_lb
The test result is FAIL
External loopback test was not executed
The test extra info:
Register test (offline) 0
Eeprom test (offline) 0
Interrupt test (offline) 0
Link test (on/offline) 1
Is there support to that ??
Yossi
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.