While using iperf to testing TCP performance, we found win7 machines with 82579LM NIC has inconsistent TCP performance result(some time 400mb/s some time 900mb/s, no other results).
On some machines, we fixed this problem by disable "interrupt moderation" to "high", problem fixed-> consistent TCP perf test result.
On some machines, non of our efforts have any effects: disable tcp offload etc.
Both OS and NIC driver are update to the latest.
Anyone saw this issue?
Details:
Windows 7 64 bit
Gigabyte GA-Z77x-up5 th motherboard (F4 bios)
Recently installed 7260 ac HMWG wireless card. 17.1 driver Working fine. 15 MBS
Problem: The network interface (wired) was only running about 20MBS and the 82579V adapter Advanced properties tab was blank, so
I decided to uninstall the driver and do a reinstall. First the 19.5 driver, then the 17.2 from Gigabyte, then the 11.13 driver from the
install CD from Gigabyte. All report back: "Cannot install drivers. No Intel adapters are present in this computer."
Hi,
I've recently installed a CT-2 network card (pic-e) on my XP pc. After startup the card reports 'no cable connected'. When I deactivate the network connection in windows and afterwards enable it again, then everything works fine.
Any suggestions / hints?
Tomy
We are trying to upgrade the NIC ixgbe driver to 3.21.2. I noticed that setting of unicast filtering table (ixgbe_set_uta) to all 1s has been removed. This breaks one of the features on the product. We have a VF that needs to be setup in L2 mode to do L2 switching in software and needs to be in promiscuous mode. It is setup / enabled with AUPE and ROPE bits in VMOLR. I would like to know the implications if this is conditionally brought back that is set UTA table to 1s when the VF is configured in promiscuous mode (L2 mode) and clear it when VF is disable. Also would like to understand reasoning behind removal of the setting of uta to all 1s.
Thanks in advance.
How can I make a wireless PC to TV connection?
Hi everybody,
I am unable to find Network drivers for Intel® I217LM Gigabit Network adapter for Windows Server 2008 Standard (32-bit). I have found the drivers for Windows Server 2008 R2 but that being 64-bit do not work.Kindly help me in sorting out this problem as I am stuck need to install the drivers.
Thanks in advance.
SHOAIB
A question about Ethernet Controller XL710 ,witch not expressed clearly in Datasheet：where is the L2tags removed from packet? Before Internal Switch，or after Internal Switch and before Receive Filters，or after Receive Filters? If the L2tags not removed, can the hash filter get input set correctly as no tag packet? For example, accoding to a packet with no L2tags, the hash filter can get the IP header follow the ethernet header. if a packet with L2tags between IP headert and ethernet header, can the hash filter correctly get the IP header ?
Hi,
I started working on Intel 82599 and as a initial step trying to test VLAN configuration on VFs.
I see it only allowing to configure one VLAN per VF. I used following command to configure VLAN 25 for VF0 of port1 (eth2) on my 82599 device.
# ip link set eth2 vf 0 vlan 25
When I try to add one more VLAN 28 using "ip link set rename19 vf 0 vlan 28", I observed it overridden previous VLAN configuration and now the VF is part of VLAN 28 only.
Could you please suggest if we can configure multiple VLANs on a VF; if so, please suggest the necessary configuration.
Thanks in advance.
Note: As it is just experiment, I am trying to use VFs on host itself. I am not assigning these VFs to VMs.
Regards,
VSR
I've got six Dell worstation class computers (Precision T5500 and Precision 670) that I am trying to use I210-T1 network adapters in. The computers are running Windows 7. When I boot the computers after the NIC's are installed, the computers fails to make it to post. All I get is a black screen with a blinking cursor in the top left corner. I have tried them in various slots, but I get the same result every time. I cannot get into the BIOS during this failure mode.
I had previously ordered and installed roughly 30 of these cards in the same model computers with no problem around 6 months ago. Because of this, I started checking to see if there were any differences between that batch of cards and the latest ones that I bought. The older cards have a manufacture date of 03/2014. The newer ones have a manufacture date of 08/2014. The newer ones, according to the Intel documentation, have 2 resistors added to them and a newer firmware.
I decided to try the older cards in the computers with the issues. The computers booted up and ran fine with the older cards.
Anyone have any ideas as to what the problem with the newer cards could be and what can be done to resolve or work around this issue?
Trying to get all my drives / firmware up to latest and greatest to root cause a Wireless performance issue. I moved to 50Mb Internet service and wired I get 50Mb.. wireless I get 6Mb.
I have a thread on Linksys site on the topic Re: Linksys TP-Link Wireless Router Performance I... - Linksys Community but the next piece of the puzzle is to validate that the drivers and firmware are fully updated such that I can start to analize the performance issue.
Issue: Intel driver Update Utility version 2.0.0.29 detects that my Dell Latitude E7440 running driver 17.0.6.1 the driver downloads but crashes during the "setup" run. Download 17.1.0.19 which is download of "Wireless_17.1.0_s64.exe"
I am not a programmer... but tried to let it run debugger and save some basic output of what it dumped.
Question:
1) Can someone direct me to what the issue is with the driver installation?
2) Can I just unpack the file and point to driver files directly? (I unzip it and it is not something that unpacked with any files I could use to let windows point to)
Thanks
A question about Ethernet Controller XL710 ,witch not expressed clearly in Datasheet：where is the L2tags removed from packet? Before Internal Switch，or after Internal Switch and before Receive Filters，or after Receive Filters? If the L2tags not removed, can the hash filter get input set correctly as no tag packet? For example, accoding to a packet with no L2tags, the hash filter can get the IP header follow the ethernet header. if a packet with L2tags between IP headert and ethernet header, can the hash filter correctly get the IP header ?
Hi all,
Having a bit of a problem currently with a Windows Server 2012 R2 system which is blue screening on a bi-daily, sometimes daily basis. The BSODs appear to be occurring when there is heavy network I/O and from reviewing the Small Kernel Dump (Minidump) files, there is a regular pattern of NdisImPlatform.sys and Ndis.sys being reported as the faulting module.
The server has a Supermicro X8DTH-6F motherboard with dual 82576 gigabit adapters on-board. Currently the server is running with the network driver which was downloaded via Windows Update, a WHQL signed Microsoft driver version 12.6.47.1 and viewing the Driver Files section in Device Manager, it is using an underlying driver file from Intel, e1i63x64.sys with a file version of 12.6.47.0.
I know that the version 12.x family of driver is pretty old so I have visited the Intel Download Center to download a later driver and the latest version available from the Download Center is 19.5. From the Supermicro website on the motherboard downloads page, they are advertising 19.4 for download.
Having tried both of these 19.5 and 19.4 driver bundles, if I use the Setup.exe to try and complete the installation naturally, they both report no Intel(R) Adapters present in the system. If I try to update the driver manually using Device Manager, in both instances it reports that the Windows Update driver is the best available driver.
I have explored the unzipped structure of the download bundle and I can see that there is no driver which references the 82576 in the NDIS64 Windows Server 2012 R2 directory, but there is a driver in the NDIS63 Windows Server 2012 folder which references the 82576.
Should I update the driver via Device Manager using the Have Disk option and forcibly select the 19.5 NDIS63 driver or is there a different bundle which will contain a Windows Server 2012 R2 NDIS64 driver for this chipset? I cannot personally see that there is going to be much, if any difference between the NDIS63 and the NDIS64 driver and given that the R2 release of Windows Server is just that, an R2 release and not a completely new operating system version, the differences in the OS should not be great enough to prevent the installation?
The Intel® Advanced Network Services (Intel® ANS) provides teaming and VLAN functionality to Intel® Ethernet network products running under various Microsoft Windows* operating systems. The same role is done by channel bonding in Linux*. Unlike Linux, there is no common teaming architecture provided by the O/S. That might change for the next Windows edition; we will have to wait and see. Until then it’s an each vendor have at it free-for-all. But Intel ANS does provide some wiggle room for our partners that have Intel add-in cards and 3rd party LAN on Motherboard (LOM) implementations. We call it Multi-Vendor Teaming (MVT) mode of ANS.
While MVT might sound like a great thing, you need to know upfront that MVT is not as good as an all Intel team. This is a natural outcome of the unique way each vendor implements and defines their products. Because of this unevenness in the implementations, we have to enforce lowest common denominator (LCD) rules for the MVT. Jumbo frames are out, as is anything else that isn’t a Microsoft standard with a standard OID. Why are jumbo’s out? Does the size listed as supported include the CRC or not? The difference means the packet will be rejected by the infrastructure for being bigger than the MTU. Things like RSS and checksum offloads are typical things that end up being turned off for LCD reasons.
We do less testing with MVT than with our own native teams mostly because we are unable to address defects in the third party products. One day maybe it will move up into the O/S provided realm, like in Linux, but until then, you should know if you add Intel adapters to your non-Intel LOM you can still make a team using Intel ANS.
Let me know if you have any MVT questions and thanks for using Intel® Ethernet!
I had a virus.
I restored a backup computer D845PESV Windows XP Pro SP3.
My old backup was not my new PCI Ethernet card Intel PRO / 1000Mbps PCI ACPI, Wake on LAN, PXE.
She has been recognized and works very well.
I am still a problem at every boot I have ever had before, a DOS window that says:
Initialyze and etablishing link
Intel Boot Agent GE v1.2.22 DHCP
PXE-E53 No boot file
PXE-MOF Exiting boot
How to remove this procedure?
Thank you for your cooperation
Hello all,
does anyone know how, or if it is even possible to downgrade the firmware on a pro 1000 vt quad port server adaptor as the one I have seems to be too recent for ESXI 5.5 udt 2.
Thanks
Glenn...
Dear SR-IOV and 82599 experts,
I’m testing KVM device(pci) pass-through with new 3.x kernel (RHEL 7.0)
It seems new device pass-through framework, VFIO, has been merged since kernel 3.6.
Before VFIO (prior pci-stub) we could simply assign each PF or VF to different guest VM freely but with VFIO, kernel strictly prohibit assigning devices to different guest (or host) in case they are in same iommu_group. I know it is required because security and PCIe ACS(Access Control Services) can avoid this limitation.
Attachment is about test environment and in this file you can see the test machine definitely support PCIe ACS. So I expected both of VFs and PFs are splitted to different iommu_group so that they can be assigned to different guest VM each.
Against expectation, the two PF on a single X520-SR2 are grouped in same iommu_group while VFs are splitted as I expected. It means I cannot assign dual port NIC to two guest VM each. Is this correct?
It is not easy to understand why PFs are tied in the same iommu_group while VFs are not.
Please someone help me to understand why this limitation still remains and let me know if there is any way I can avoid this.
For performance reason, I need PF pass-through I don't consider VF.
Thank you.
Minho Ban
Hi ...
I am trying to remove "Intel Advanced Network Services Virtual Adapter" that appears in the device manager in windows 7.Tried few solutions but none of the work like this one:
http://www.intel.com/support/network/sb/cs-029916.htm
anyone knows a working solution.
Thanks
Hello,
Upon reboot my network card fails to start with error code 10. I have tried disabling and re-enabling, re installing with current drivers and of course reboots all did nothing. Now im trying to download the NVM update utility for 82579LM from Intels site but it says "page not found", this is happening to me for almost all pages on intels site.... I have tried using 3 different browsers but still cannot get to the page. Does anybody by chance have the direct download link for the NVM update tool?
A question about Ethernet Controller XL710 ,witch not expressed clearly in Datasheet：where is the L2tags removed from packet? Before Internal Switch，or after Internal Switch and before Receive Filters，or after Receive Filters? If the L2tags not removed, can the hash filter get input set correctly as no tag packet? For example, accoding to a packet with no L2tags, the hash filter can get the IP header follow the ethernet header. if a packet with L2tags between IP headert and ethernet header, can the hash filter correctly get the IP header ?
Hi,
After weeks of troubleshooting DPC latency problems on my Lenovo Thinkpad T420 laptop which were causing audio dropouts and mouse freezes every few mins I have finally tracked down the source of the issue. It appears that the Intel 82579LM based Network Controller driver may not be correctly optimised for Windows 8. I'm running Windows 8 Pro 64-bit and am using the latest Intel driver for the controller (12.6.45.0). In troubleshooting the issue I tried everything I could think of such as:
Update BIOS and all drivers to latest versions
Disable CPU and PCI Power Management in BIOS
Disabled onboard Sound (I use a separate professional audio sound card), Wifi, Bluetooth
Change power management settings to High Performance and Disabled USB selective suspend
Turn on all offloading settings on Ethernet NIC
Ran bcdedit /set disabledynamictick yes
Disabling Network Location Awareness in Windows
Nothing made any noticable difference at all. I had also been noticing that my network performance had been pretty poor intermittently on this machine for a while, occasionally experiencing dropouts and low download speeds (yes I know that can be caused by many other factors but please hear me out). Every few mins on the PC I would experience a DPC latency spike of around 95000us to 100000us which would occur right when the audio dropouts, mouse freezes, and probably network pauses would occur. I use the PC for audio production amongst other things so this causes me big issues.
I was totally baffled by the problem until I ran an xperf trace in the Windows Performance Toolkit and saw that the spike was being generated from ndis.sys and tcpip.sys. That got me thinking down the lines of a network related problem so I disabled the onboard Intel(R) 82579LM based Network Controller in Device Manager in Windows 8 and what do you know the problem disappeared competely!! No more DPC latency spikes ever (tested for hours and many times). I can do pretty much whatever I like on the PC and the problem does not reoccur. Not one single audio dropout in my Audio DAW either. The onboard Wifi is still running (Intel Centrino Advanced-N 6205 - v15.8.0.5) providing me with network access and download speeds through the wireless nic are both much faster and more stable surprisingly (should be the other way around if anything). As soon as I re-enable the 82579LM NIC the problem is immediately back within a few mins.
I am desperate to get this fixed as I cannot use wireless all of the time. Intel can you please fix the 82579LM driver to make it fully compatible with Windows 8 Pro 64-bit. I'm sure many other people out there are having the same issue and just don't know the cause, or put up with it it as real time applications such as audio are less important to them. I have read about other people having these issues and it only appears to be with Windows 8. I think the drivers are fine for Windows 7, although I haven't confirmed this for sure.
Intel please consider patching the 82579LM NIC driver ASAP for full Windows 8 support. I can assist in providing you information if you require as I'm very keen to get this sorted.
Thanks,
Brad