I upgraded Windows 7 too Windows 10, but I miss the ProSet features in the Win10 Device-Manager. I tried to install a lot of drivers without success. It tells me I have no Intel-Adapter installed....
Will there be a "full" driver support for my adapter in the near future?
Thank 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
Realize I posted this to an answered question earlier. Thought I might get a response with a new discussion:
We are running 82599 10 Gigabit Dual Port NICs with the 4.1.2 Linux driver. Is it still the case that the driver only supports two queues pairs per VF? The driver documentation [1] seems to say the VFs will use pools with up to 8 queue pairs is this not correct? If not, are there plans to support more than 2 queue pairs per VF?
[1] Intel® 82599 SR-IOV Driver Companion Guide
Thanks,
-tom
Hi, I try to create VFs with Intel X520-SR2 on Gigabyte Z97-D3H.
I enable Intel Virualization Technology and VT-d in BIOS setting and add boot parameter "intel_iommu=on".
I use PF driver (ixgbe driver version: 4.0.3) and VF driver (ixgbevf driver version: 2.16.1) on Ubuntu 14.10 with kernel version of 3.16.0.23
After insert ixgbe and ixgbevf module, I fail to see VFs with lspci -n command.
Can anybody help me? Thank you!
Hi everybody.
Lately I've been experiencing lots of troubles with my wired connection on my new windows 10 computer. Connection keeps dropping every now and then. Plus, when it is working, I noticed that the speed is significantly decreased (I hired a 10 mb/s broadband but I am getting about 2.5 mb/s these days). My knowledge in computering is quite basic and limited, so I tried several things I found on different sites. Nothing seems to put things right for me so far, so I decided to try in this community...
The first thing I tried was looking up for new ethernet drivers. And here is the first curious thing: although the latest driver version published on the download center is 20.4.1, after I run the installation wizard it keeps showing a different version. Why? I have no idea.
I also tried running a command prompt, "netsh winsock reset". It kind of scared me at first because it somehow disabled my mouse drivers , but after fixing those, I had a look at the internet and the connection problems persist.
If I run the troubleshoot thing it keeps pointing at a "default gateway" issue. I am not sure what that is, but everywhere I look on the internet people talk about drivers and w10 being flawed.
Does anyone have any new inputs? I'd appreciate some new ideas. The computer is quite new, I don't like struggling with all this after such a short time enjoying it.
Thanks in advance.
I've been trying to update the flash on an Intel i350-T4 NIC I got off Amazon but for some reason bootutil won't let me.
First when I just run bootutil it show all four ports on the card to be in "FLASH not present" mode.
When I run "bootutil -nic=1 -fe" it says the command has succeeded and to reboot to enable flash. After a reboot nothing has changed and trying to update the flash with "bootutil -nic=1 -up=pxe -file=bootimg.flb" results in a "Flash is not enabled on port 1" error (using the Intel bootutil) or an "Adaptor port is not bootable on port 1" error is using an IBM or Dell version of bootutil.
Trying to execute "bootutil -nic=1 -bootenable=pxe" with either Dell or IBM bootutil gives the same "Adaptor port is not bootable on port 1" error. Using the Intel bootutil for the same commands gives a "Found discrete ROM in the flash for NIC 1" error.
I'm at a loss as to how to update the flash. Tried to get the Cisco version of bootutil to see if that worked any better but the Cisco support site is a mess and won't let me login to download their tools.
Does anybody have any suggestion on any other version of bootutil to use or anything else to try to update the flash on this card? I tried to contact the Amazon vendor to find out exactly what system manufacturer's server this card was taken out of but haven't had any luck yet.
Hello, there.
This morning I upgraded my fully functionnal Windows 8.1 Enterprise installation to Windows 10 Technical Preview. Before that, I downloaded the Intel Network Adapter Driver from this website, version 20.1, for Windows 10 64 bits. After the driver installation, I had the VLANs tab in the network card properties. However, i'm unable to create a VLAN. The network card is automatically disabled then I receive an error message saying this (translated from french):
One or more vlans could not be created. Please check the adapter status and try again.
The window freezes and I have to force-close it. 802.1 option is of course enabled in the Advanced options tab. The event viewer always shows the same error when I try to create a VLAN:
Nom de l’application défaillante NCS2Prov.exe, version : 20.1.1021.0, horodatage : 0x554ba6a4
Nom du module défaillant : NcsColib.dll, version : 20.1.1021.0, horodatage : 0x554ba57d
Code d’exception : 0xc0000005
Décalage d’erreur : 0x0000000000264064
ID du processus défaillant : 0x19d4
Heure de début de l’application défaillante : 0x01d0ada33fd50576
Chemin d’accès de l’application défaillante : C:\Program Files\Intel\NCS2\WMIProv\NCS2Prov.exe
Chemin d’accès du module défaillant: C:\WINDOWS\SYSTEM32\NcsColib.dll
ID de rapport : eefb5842-9220-4bad-93d3-774828c5736e
Nom complet du package défaillant :
ID de l’application relative au package défaillant :
I already tried to uninstall all the packages and drivers related to the network card. I deleted fantom network cards then cleaned up the registry. I tried to set some compatibility options to the given executable file, with no success. I tried to reinstall the driver with Drivers Signature disabled, tried to disable IPv4/IPv6 from the network card before trying to add a VLAN... I tried everything I found on Google.
Could someone help me, please?
Hello there,
I have recently bought the desktop HP ENVY 750-079NA. The system is Windows 8.1 (64 bit). The problem is that the Ethernet randomly drops out about ten times a day. Also, the Ethernet is re-connected quickly after each internet dropping. I have checked the network adapter and it shows that the adapter is up-to-date. The network adapter is Intel (R) Dual Band Wireless-AC 7260. I also tried a lot of possible methods for solving the Ethernet dropping but they do not work.
So, I do really appreciate if anyone could help me in figuring out this problem.
Many thanks.
Brian
Hi,
I'm using an ASRock Rack EPC612D8A-TB motherboard with two Intel onboard NICs (I210 (Ethernet 2) and I217-LM (Ethernet)), running Win 8.1 Pro x64 with all Windows Updates installed and the latest Intel Ethernet driver package (20.2.3001.0). My problem is with the I217-LM, according to the Intel spec sheet it does support RSS (cp. figure on page 2).
In the I217-LM's advanced driver settings there is an option to enable and disable RSS. However Windows itself always says that the I217-LM is not RSS-capable.
Image may be NSFW.
Clik here to view.
The same option in the I210 driver options has the expected effect: With the PowerShell command get-SmbClientNetworkInterface you can see the RSS capability changing from True to False and vice versa.
Can anyone tell why the I217-LM is not getting the RSS feature?
Further system details:
CPU: Xeon E5-1620-V3
RAM: 2 x 16 GiB Crucial DDR4-2133 ECC
The motherboard does not have a later BIOS/UEFI release than the one installed.
Thank you very much for your help!
Hello,
I'm using ethernet card which is based on Intel 82546 chipset,
I would like to know how is it possible to access (read) low level registers of the chipset such as CRC error counter
and other information thath can be used to debug physical layer problems.
It is also known as MIB's.
Appreciate for your help
Shai
I have an XL710 VSI that is running in a VF and uses RSS queuing across multiple queues on input. In fact there are 4 RSS queue sets in the VF. For various reasons I want to put frames on each XMIT queue in the VF and loop them back to the matching RCV queue. I have modified the VSI to set the "Allow destination override" bit in the ADD_VSI command. I've also set the SWTCH field in the context transmit descriptor to 11b and set the TARGET_VSI field to the VSI id. This all then works in that the transmitted frame is looped back to a receive ring. But there is a catch. Frames put on transmit queues 0 thru 3 all end up being looped back to the rcv ring of rcv queue 0, instead of back to the appropriate matching rcv queue eg Xmit 3 to Rcv 3. Can anything be done about this?
Hi, I try to create VFs with Intel X520-SR2 on Gigabyte Z97-D3H.
I enable Intel Virualization Technology and VT-d in BIOS setting and add boot parameter "intel_iommu=on".
I use PF driver (ixgbe driver version: 4.0.3) and VF driver (ixgbevf driver version: 2.16.1) on Ubuntu 14.10 with kernel version of 3.16.0.23
After insert ixgbe and ixgbevf module, I fail to see VFs with lspci -n command.
Can anybody help me? Thank you!
Hi to all, I'm new here, I'm trying to find a solution or someone that can help me to a issue that is taking me no slep.
I've a Synology SAN with a 10Gb Synology adapter with a direct attach cable HP spf+ cable and a DL80 HP Server mounting an X520-DA intel 10Gb dual board.
All the components where bough according with compatibility table on Synology site for a direc attached 10Gb storage.
Compatibility - Synology - Network Attached Storage (NAS)
I'm using Vmware Vsphere 5.5 (tried also 6.0), when i attach directly spf cable on San and Intel board lights go on in both board. If i see into SAn's networking i can see "connected" behind the 10Gb nic...but in Vmware the Intel Nic is in Down state. In this way i can't use it for direct attach storage.
I've read about some firmware problems...but i'm unable to understand how to update firmware of the Intel Nic and where to find the right one. This is a NON branded X520-DA so i need the intel one.
Thank you for any help you can give me.
Alex
Hi all,
I've installed FreeBSD 10.2-STABLE on a server with 2*CPU E5-2643v3 (with HyperThreading on) and Intel XL710 4*10G SFP+ card.
At first I updated FreeBSD drivers to 1.4.0 (from download.intel.com).
I see next strange thing - Every acive ixl interface creates 24 queues (6 core *2 (HT) *2 CPU) but uses only 16-17 of them:
irq284: ixl0:q0 164383663 1941
irq285: ixl0:q1 371238730 4384
irq286: ixl0:q2 378286557 4468
irq287: ixl0:q3 365073427 4312
irq288: ixl0:q4 371116376 4383
irq289: ixl0:q5 372589584 4400
irq290: ixl0:q6 361879025 4274
irq291: ixl0:q7 354607200 4188
irq292: ixl0:q8 223602267 2641
irq293: ixl0:q9 199067474 2351
irq294: ixl0:q10 212598000 2511
irq295: ixl0:q11 202534854 2392
irq296: ixl0:q12 212050675 2504
irq297: ixl0:q13 209106917 2469
irq298: ixl0:q14 201452403 2379
irq299: ixl0:q15 203896634 2408
irq300: ixl0:q16 76328643 901
irq301: ixl0:q17 6030 0
irq302: ixl0:q18 5433 0
irq303: ixl0:q19 6804 0
irq304: ixl0:q20 6098 0
irq305: ixl0:q21 6603 0
irq306: ixl0:q22 6476 0
irq307: ixl0:q23 7141 0
irq309: ixl1:q0 161169757 1903
irq310: ixl1:q1 402042077 4748
irq311: ixl1:q2 399166615 4714
irq312: ixl1:q3 389702886 4602
irq313: ixl1:q4 383371508 4528
irq314: ixl1:q5 388621686 4590
irq315: ixl1:q6 385533771 4553
irq316: ixl1:q7 390478220 4612
irq317: ixl1:q8 232313544 2743
irq318: ixl1:q9 248387076 2933
irq319: ixl1:q10 233942388 2763
irq320: ixl1:q11 237794942 2808
irq321: ixl1:q12 227292626 2684
irq322: ixl1:q13 222151566 2623
irq323: ixl1:q14 234209020 2766
irq324: ixl1:q15 217878026 2573
irq325: ixl1:q16 80177041 947
irq326: ixl1:q17 83 0
irq327: ixl1:q18 74 0
irq328: ixl1:q19 201 0
irq329: ixl1:q20 98 0
irq330: ixl1:q21 95 0
irq331: ixl1:q22 91 0
irq332: ixl1:q23 87 0
# top -aSCHP
last pid: 28661; load averages: 7.06, 6.35, 6.23 up 0+23:35:07 17:15:12
391 processes: 31 running, 215 sleeping, 145 waiting
CPU 0: 0.0% user, 0.0% nice, 0.0% system, 39.4% interrupt, 60.6% idle
CPU 1: 0.0% user, 0.0% nice, 0.0% system, 48.8% interrupt, 51.2% idle
CPU 2: 0.0% user, 0.0% nice, 0.0% system, 42.1% interrupt, 57.9% idle
CPU 3: 0.0% user, 0.0% nice, 0.0% system, 40.2% interrupt, 59.8% idle
CPU 4: 0.0% user, 0.0% nice, 0.4% system, 41.3% interrupt, 58.3% idle
CPU 5: 0.0% user, 0.0% nice, 0.0% system, 37.0% interrupt, 63.0% idle
CPU 6: 0.0% user, 0.0% nice, 0.0% system, 35.8% interrupt, 64.2% idle
CPU 7: 0.0% user, 0.0% nice, 0.0% system, 39.0% interrupt, 61.0% idle
CPU 8: 0.0% user, 0.0% nice, 0.0% system, 22.0% interrupt, 78.0% idle
CPU 9: 0.0% user, 0.0% nice, 0.0% system, 26.0% interrupt, 74.0% idle
CPU 10: 0.0% user, 0.0% nice, 0.0% system, 17.7% interrupt, 82.3% idle
CPU 11: 0.0% user, 0.0% nice, 0.0% system, 19.3% interrupt, 80.7% idle
CPU 12: 0.0% user, 0.0% nice, 0.4% system, 25.2% interrupt, 74.4% idle
CPU 13: 0.0% user, 0.0% nice, 0.0% system, 23.6% interrupt, 76.4% idle
CPU 14: 0.0% user, 0.0% nice, 0.0% system, 22.4% interrupt, 77.6% idle
CPU 15: 0.0% user, 0.0% nice, 0.0% system, 26.8% interrupt, 73.2% idle
CPU 16: 0.0% user, 0.0% nice, 1.2% system, 1.6% interrupt, 97.2% idle
CPU 17: 0.0% user, 0.0% nice, 0.8% system, 0.0% interrupt, 99.2% idle
CPU 18: 0.0% user, 0.0% nice, 1.2% system, 0.0% interrupt, 98.8% idle
CPU 19: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt, 99.6% idle
CPU 20: 0.0% user, 0.0% nice, 3.5% system, 0.0% interrupt, 96.5% idle
CPU 21: 0.0% user, 0.0% nice, 1.6% system, 0.0% interrupt, 98.4% idle
CPU 22: 0.0% user, 0.0% nice, 0.8% system, 0.0% interrupt, 99.2% idle
CPU 23: 0.0% user, 0.0% nice, 2.0% system, 0.0% interrupt, 98.0% idle
# netstat -I ixl0 -w1 -h
input ixl0 output
packets errs idrops bytes packets errs bytes colls
235K 0 0 126M 300K 0 321M 0
233K 0 0 114M 297K 0 312M 0
232K 0 0 116M 300K 0 315M 0
227K 0 0 108M 297K 0 316M 0
Where is the source of problem that network adapter doesn't utilize all queues ?
Hi,
Does intel 82580 1000Base-X(fiber) transmit clock use local reference clock or
rx recovered clock ?
Thanks in advance.
Hi everyone,
We purchased a few DELL Optiplex 9020s that came with an Intel Ethernet Connection I217-LM ethernet controller, and I've been unable to find the correct WinPE x64 drivers for this adapter.
From the Download Center I found what I thought were the correct drivers. In the EXE, I found some WinPE drivers, but apparently these aren't it as I'm not able to connect to my network when I boot up using WinPE.
Can anyone point me in the right direction to get the correct drivers please?
Thanks!
Ive got the Intel DQ67EP board with the Intel 82579LM onboard NIC. Ive got the machine running Windows7 64bit. Ive got this problem where randomly it drops from Gigabit to 10Mbps and will never negoiate back to gigabit. I can disconnect the cable, reconnect it, dont work. I can plug that same cable into another machine like my Lenovo T420 laptop, and it has no issues connecting gigabit, so I know its not the cable, or port, or Hub. However still plugged into a different port of the hub, still dont work. Plugged it into a different hub, still dont work, still keeps sitting at 10Mbps.
Ive rebooted it, still negoiates at 10Mbps. Shut the PC down, wait 1min, turn it on, still sitting at 10Mbps. So at this point dont believe its driver. I have the latest 16.5 running on the Windows.
ONLY way I can get this working is one of two ways. I have to unplug power, not just shut it down. I need to kill power from the board entirely. Wait 10secs, then plug it back in. Then upon starting up, its set to gigabit with no issues. Other way is to change a setting in Bios which when you exit/save it causes it to kill power to the board for a second. So the fact that killing power to the board fixes it, tells me its some hardware or firmware level issue, clearly not the driver.
Now to explain when it happens, I do have the machine set to sleep and wake at certain times. Most of the time it sleeps fine, wakes up fine and still sits at Gigabit. Theres no explanation on how many times it takes before it decides to go into some stuck state of only negoiating at 10Mbps. Even going into Device Manager and setting it to 100Mbps, or 1000Mbps, Half or Full duplex does nothing. It disconnects the Link and Reconnects but only sits at 10Mbps. Im normally connected via the IntelAMT via RealVNC.
Ive updated from the 0054 bios to 0055 last week so Im also on the latest Bios revision.
What causes this to get in such a stuck state that only killing power to the board fixes this?
Dixit
upgraded my previous build of Win 10 Pro (64bit) to the new November 10 Update .
now after the update i have new problem When I start my computer (nearly everyday now, but not in the beginning) I can't connect to the internet. I get the message that my network driver adapter is missing (intel 82579LM Gigabit Network Connection adapter is experiencing driver-or-hardware - related problem). It does not show so i reboot sometimes it comes sometime so for solution i go to device manager locate ethernet intel adapter then disable it and enable it then it works. So for this reason I had lost my internet connectivity. Already updated driver to latest version (Manually). Kindly help it is very frustrating to do this silly things again and again thanks in advance
The Fodora 20 system was installed with quad-port XL710 NIC. By default, the NIC driver creates 4 queues per port and both IPv4+UDP/TCP(udp4/tcp4) and IPv6+UDP/TCP(udp6/tcp6) for RSS are enabled. It loads IPv4+UDP/TCP traffic with different IPs to different queues(cores).
But All IPv6+UDP/TCP traffic with different IPs was directed to only one queue(one core). Reconfiguration of rx-flow-hash for udp6 or tcp6 by ethtool did not solve the issue.
The other problem is all IPv4 or IPv6 traffic with different IPs was also directed to only one queue when only IPv4 or IPv6 RSS enabled.
System: Fedora 20
Kernel: 3.19.8-100.fc20.x86_64
NIC: quad-port XL710
Driver: i40e
Version: 1.2.2-k
Firmware-version: f4.1 a1.1 n04.10 e80001109
We successfully got 8086-1583 working with i40e 1.3.38 and 4.42 nvm.
Later we managed to upgrade from to i40e 1.3.39.1 and 4.53 nvm.
During nvm upgrade we've got following exception with the success message at the end.
Now we are not able to bring link up with old drivers and nvmneither new ones.
If nvm downgrade passes silently upgrade throws this exception every time.
Upgrade under Windows fails too with BSOD and 0x80 NMI_HARDWARE_FAILUR
# ./nvmupdate64e Intel(R) Ethernet NVM Update Tool NVMUpdate version 1.25.20.03 Copyright (C) 2013 - 2015 Intel Corporation. WARNING: TO AVOID DAMAGE TO YOUR DEVICE, DO NOT EXIT OR REBOOT OR POWER OFF THE SYSTEM DURING THIS UPDATE Inventory in progress. Please wait [******+...] Num Description Device-Id B:D Adapter Status === ====================================== ========= ===== ==================== 01) HP Ethernet 1Gb 2-port 361i Adapter 8086-1521 02:00 Update not available 02) Intel(R) Ethernet Converged Network Ad 8086-1583 06:00 Update available Select adapter(s) to be updated (only 'Update available' adapters may be selected [(comma-separated adapter numbers) | All | eXit]: 2 Do you want to save a backup copy of current NIC images? [Yes | No]: y Update process in progress. Please wait [****......] Message from syslogd@carbon at Sep 15 14:51:09 ... kernel:[ 332.581535] NMI: IOCK error (debug interrupt?) for reason 61 on CPU 0. Message from syslogd@carbon at Sep 15 14:51:09 ... kernel:[ 332.581688] Stack: Message from syslogd@carbon at Sep 15 14:51:09 ... kernel:[ 332.581753] Call Trace: Message from syslogd@carbon at Sep 15 14:51:09 ... kernel:[ 332.581838] Code: 28 e0 ff ff 80 e2 08 75 22 31 d2 48 83 c0 10 48 89 d1 0f 01 c8 0f ae f0 48 8b 86 38 e0 ff ff a8 08 75 08 b1 01 4c 89 e8 0f 01 c9 ed 6d e7 ff 4c 29 f0 48 89 c7 e8 f5 b7 e5 ff 4c 69 e8 40 42 ...+****** Reboot is required to complete the update process. Tool execution completed with the following status: All operations completed successfully Press any key to exit.