Hi,
I tried to do the latest driver update for the Intel 82583V Gigabit Ethernet controller (version 21.1 date 10/11/2016), but after the update I checked the driver and it displayed version 12.7.28.0 dated 5/26/2015.
Before the installation I was running driver version 11.4.7.0 so I know it did update my driver but I do not understand why it did not update to the latest version available on the Intel website. Any insights?
Thanks.
Dear Intel Support,
I have a Latitude E5450 laptop and after a driver update, afaik, the device stopped working.
Tried reverting to the previous driver, messing with BIOS settings and doing a clean installation of Windows with no luck.
Seems to be the same issue that's been discussed in these threads:
i218-LM code 10 after restart without cable
i218-LM "this device cannot start. (Code 10)"
So I'd like to request the ULP tool to see if it resolves my issue.
Regards,
Alejandro.
Hello all,
We have newly installed Intel X710 NICs on Windows Server 2012 R2 connecting to a Juniper EX4500 with DCBX enabled. The Juniper DCBX information for the interfaces show enabled and everything looks good. The data center tab on the X710 shows the following:
Status: Non Operational
DCBx Version: IEEE 802.1Qaz
Priority Group: Operational
Priority Flow Control: Operational
iSCSI Status: Feature not present in peer TLV
Our other NICs we have are X520 and they show DCBX to be operational. All interface settings on the Juniper are identical.
To my knowledge the X710 devices have the latest drivers installed.
Has anyone seen something like this before or have any ideas?
Hi!
I am using latest IGB driver(5.3.5.3) for Intel I350-T2 adapter.
Enabled IOMMU, created two VFs ('modprobe igb max_vfs=2'), and added the first VF as a passthrough device to a guest VM.
Installed latest IGBVF driver(2.3.8.2) in the guest.
Whenever I transmit packets from the guest, I observe the following error in dmesg of the host.
"igb 0000:02:00.0 p4p1: VF 0 misbehaved. VF queues are disabled. VM misbehavior code is 0x18000000"
Following this error, the host machine hangs immediately.
Could anyone please explain what does the code '0x18000000' represent and how to fix it.
Thanks much in advance!
Regards
Karthik
Hello,
now that Windows Server 2016 is in general availability, when can we expect to have a stable driver release for Windows Server 2016? The TP5 beta drivers are not very stable.
thanks!
Hello, Can anyone please help me figure out what the difference between i350-t2 and i350-t2v2? The specs look exactly the same.
Hi,
We're developping software that runs under Windows Embbeded Standard and hardware using Intel I210 controler.
We require low-level access driver to be able to control TX timestamps or IPG in order to comply with real-time video delivery requirements.
Is I210 driver source code available for Windows Systems?
Thanks,
AdolfoMV.
Hello,
I'm using 82599 NIC with SR-IOV technology.
recently I've got an issue with following configuration.
as you can see there are two VFs that has same MAC on one PF. but each VF tagged different vlan. I thought that it should be work. but when after I create vf4, the vf3 is not working.
but vf3 is working when after I remove vf4 without any reboot/recreation operation.
Is there any limitation to use sr-iov (vf) with fixed-mac/vlan that created from a PF? any specific reason or specifications we have?
ip link show eth5
vf 0 MAC 12:00:00:00:03:00, vlan 812, spoof checking on
vf 1 MAC 12:00:00:00:00:50, vlan 812, spoof checking on
vf 2 MAC 12:00:00:00:00:c0, vlan 812, spoof checking on
vf 3 MAC 12:00:00:00:10:c0, vlan 812, spoof checking on
vf 4 MAC 12:00:00:00:10:c0, vlan 810, spoof checking on
Thanks.
Hello,
I recently installed an Intel X520-2 NIC to my windows server. Windows auto-installed it and I can access the device. It is currently working as just a regular ethernet adapter. I need to change it to iSCSI mode. I did some research and found that I need to use the Intel Ethernet Flash Firmware Utility. Here is what I am currently doing:
C:\Intel21.1\APPS\BootUtil\Winx64>BOOTUTILW64E.EXE
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.6.20.1
Copyright (C) 2003-2016 Intel Corporation
Type BootUtil -? for help
Port Network Address Location Series WOL Flash Firmware Version
==== =============== ======== ======= === ============================= =======
1 90E2BAC2EE98 8:00.0 10GbE N/A PXE 2.1.40
2 90E2BAC2EE99 8:00.1 10GbE N/A PXE 2.1.40
C:\Intel21.1\APPS\BootUtil\Winx64>BOOTUTILW64E.EXE -FLASHENABLE -ALL //Set to FlashEnabled
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.6.20.1
Copyright (C) 2003-2016 Intel Corporation
Enabling boot ROM on port 1...Success
Reboot the system to enable the boot ROM on this port
Enabling boot ROM on port 2...Success
Reboot the system to enable the boot ROM on this port
Port Network Address Location Series WOL Flash Firmware Version
==== =============== ======== ======= === ============================= =======
1 90E2BAC2EE98 8:00.0 10GbE N/A Reboot Required
2 90E2BAC2EE99 8:00.1 10GbE N/A Reboot Required
//I HAVE REBOOTED AFTER THIS STEP AND GOT SAME RESULTS
C:\Intel21.1\APPS\BootUtil\Winx64>BOOTUTILW64E.EXE -BOOTENABLE=iscsiprimary -ALL
Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.6.20.1
Copyright (C) 2003-2016 Intel Corporation
Found discrete ROM in the flash for NIC 1
The -BOOTENABLE command can only be used on flashed combo images
Found discrete ROM in the flash for NIC 2
The -BOOTENABLE command can only be used on flashed combo images
Port Network Address Location Series WOL Flash Firmware Version
==== =============== ======== ======= === ============================= =======
1 90E2BAC2EE98 8:00.0 10GbE N/A PXE 2.1.40
2 90E2BAC2EE99 8:00.1 10GbE N/A PXE 2.1.40
What is "The -BOOTENABLE command can only be used on flashed combo images"? I have tried to DISABLE as well and it does not take (same error message). I must be missing something but I am not sure what.
I have two computers, each with a XL710-QDA2, currently running Windows Server 2016 Tech Preview 5.
Is it possible to directly connect these two with the QSFP+ cable?
This does not seem to be working for me
Does the latest Intel driver for I219-V support Windows Server 2012 and Windows Server 2016?
I have an Intel NUC6i5SYH with I219-V gigabit Ethernet and discovered that the Intel Ethernet driver installs and runs with Windows 10, but not with Windows Server 2012 R2 or Windows Server 2016 OS. In looking for Intel Ethernet drivers on the downloadcenter.intel.com website, I found driver package 21.0 that lists support for both I219-LM and I219-V, but actual driver installation testing indicates that for Windows Server 2012 R2 and Windows Server 2016 OS, the e1d65x64.sys driver only installs against I219-LM but not I219-V.
Will Intel please clarify the support position of your Ethernet drivers for I219-V and Windows Server 2012 R2 and Windows Server 2016. If the drivers have no support for this HW/OS combination then a correction is in order for the downloadcenter.intel.com website, as the information on it currently is misleading.
The background:
I'm using the 82588EB SR-IOV function, and attach the VF direct to the VM. My app running inside the VM requires send and receive both VLAN tagged and untagged traffic, just like the VLAN trunk port on the switcher, and may require 4096 VLAN tags pre VF. The traffic will be tagged inside the VM by the app itself.
My questions are:
What kind of configuration should I do for the NIC or VF to achieve my goal?
Should the promisc mode be disabled?
Does it related with the VLAN filter parameter?
And does the hardware or driver has any limitation for the VF's allowed VLAN tagged/untagged traffic?
Before I asked the question, by searching the community, I saw some topic about VLAN filter, and seems there is limitation about supported VLAN tag number, 64 or 256 or 512, anyway, not all 4096 VLAN tags are allowed to pass to the VM.
If the limitation is true, I would like to know why, is it the hardware limitation or driver limitation?
I would like to be able to issue a command from LINUX to retrieve transmitted optical power, received optical power.
Is there any Intel software utility to get that info?
I have tried to PXE Boot to WINPE using NIC X710. I used iPXE and wimboot, iPXE uses snp drivers and when it hands over control to windows, WinPE hangs in the windows logo.
any suggestion?
I have an extremely odd situation with BPF expressions and VLAN tagging when using ixgbe devices on CentOS 6.
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
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])
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
Recently, I have had some issues with my PC that was built April 2016 and had to make some Bios changes. Before doing that, I found that my motherboard had a dual bios. The one that was not working and had to be repaired (side A) is now working but my network adapter I219-V is not. It says it needs drivers. So, I installed them from my board's manufacturer's site and that did not work. I tried the drivers from the Intel site and that did not work. I have Windows 10 Home - 64 bit. On side B of my bios, the internet works fine with this same adapter. I have been at it more than 24 hours trying to find a solution and I have come up with nothing.
In the device manager, the adapter (once the driver's were installed) has the yellow triangle and error code 10.
I'm trying to narrow down a connectivity issue with my ethernet adapter. I have an Intel(R) Ethernet Connection I217-V ethernet adapter connected to a Linksys RE6500 wireless extender. I've verified the Linksys has a full connection. The originating wireless AC signal is coming from an AT&T (Pace) 5268AC Residential Gateway. The machine is on Windows 10 64-bit with latest Anniversary Update.
Every so often at random, the connection drops and resets. I haven't been able to nail down a pattern that causes it, but it seems to happen mostly when browsing the web or connecting remotely via VNC. What's odd is that when I had it connected to an ASUS RT-AC68U via ethernet cable, it never dropped the connection, which leads me to believe it's an issue with the Linksys. I've got an open ticket with them right now, but to be sure, I want to make sure there isn't anything on my ethernet adapter settings I need to configure in order for it to work with the RE6500. Below are screenshots of the configuration and driver version, which seems to be the latest as far as I can tell.
All Power Management options are turned off on this tab:
No changes to the below settings have been made. All are set to the defaults:
I saw a few other posts where people had issues with the connection dropping, but there didn't seem to be any resolution to it. I welcome any and all assistance!
I have noticed that when I connect Cat6 cable to port1 none of the both ports are detected, if I connect Cat6 cable to port0 I was able to see both ports (0 & 1). Please let me know if you have any suggestion.
Hi,
I am trying to create an Ethernet AVB demo setup with the following configuration:
1. Talker running in a PC, with i210 - source code taken from Open AVB in Github - Linux 14.04
2. Listener running in a PC with Intel 82579 LM based Network Controller - Linux 16.04
I am able to build the code for talker and listener and talker application is running.
The listener application terminates after receiving a few packets from talker. It seems the driver used in listener is not AVB compatible. We used the e1000e driver, since we found that the intel card used in the listener supports IEEE 802.1AS and IEEE 802.1Qav protocols which are the bare minimum support needed in a listener.
Can anybody help me to resolve the issue? Should I get another driver or is the network card not expected to work in AVB?
thank you,
Radhika.