Hi Everybody

I am facing a scalability issue when using SR-IOV with multiple 82599ES NICs. I have 2 x520 Network adapters containing a total of 4 82599ES controllers. SR-IOV is enabled on each of them with "modprobe ixgbe max_vfs=8" option. The server used is Dell PowerEdge M620 with 4 KVM hosted VMs. Each VM has a VF added from a separate 82599 NIC.

The problem is that the combined RX+TX rate for 64 Bytes UDP packets doesn't extend beyond ~23MPPS.

So if only 1 VM is started, it can RX+TX at ~23 MPPS (almost ~11.5 MPPS each). However when second VM is booted, the rate for each VM becomes 5.5 MPPS for RX and 5.5 MPPS for TX (still a 23 MPPS combined RX+TX for both VMs). Kindly see the table below:

No. of VMs:                                1          2          4

Each VM's RX rate (MPPS):       11.5       5.5       2.8

Each VM's TX rate (MPPS):       11.5        5.5       2.8

So a total of ~23MPPS in each case. Any idea where the bottleneck can be?

I have tried these optimizations/settings but no improvement is seen:

1) Guest Memory is backed by (mapped on) hugepages on Host. Memory is from same socket on which VM is running. Also sibling cores are used.

2) vCPUs have been pinned down to physical CPUs.

3) The MSI-X interrupts of the VF used are mapped on the respective VM cores.

4) SR-IOV global, Intel VT-d and IOAT is enabled in BIOS.

5) Updating the IXGBE driver on host to latest (3.22.3) version didn't improve this.

Testbed details:

My system is Dell PowerEdge M620.

Host OS: RHEL 6.5

Guest OS: Ubuntu 13.10

IXGBE driver version: 3.15.1-k

I am running DPDK 1.6.0 on KVM hosted Guests.

Any help will be greatly appreciated.

Thank you

Umar

Hi all.  I am currently having an issue with Windows 8.1 and my wired Ethernet connection.  Whenever I am using web based browser games or downloading a large amount of content, my Ethernet connection will drop to limited.  My wireless connection has never had this problem, but it is much slower.  It is very frustrating because the only way to fix it is to either restart the computer or constantly run a fix connection.  I am wondering if this problem has any thing to do with my Ethernet driver? I am currently using Broadcom Netlink (TM) Gigabit Ethernet driver version 15.6.1.2.....It is currently the most up to date version of the driver.  I have read on some other support forums that this particular driver does not work well with windows 8.1 and to use a windows 7 driver.  If this is the case, what driver would I use and where do I find it?  If this isn't the case, do any of you have any ideas for what could be causing the issue, and if so, how do I fix it?

I have 3 HP Z800 workstations I am installing X540-T2 card into which are teamed to 802.3ad.

The first PC has installed fine and running smooth.

PC 2 and 3 the cards installed fine and work for about 5 minutes and then shut off due to overheating. The syncs are noticeably hot to touch.

The only difference spec wise is PC 1 has a mid range card where PC 2 and PC 3 have Nvidia GTX 980 cards and sata cards installed in each.

I have taken the cards out and put them into another Z800 box that is similar to PC 1 and have not had any issues overheating. Though I was only able to test over a 1gb connection.

I am fairly certain the cards were seated correctly in all instances.

I have the most current drivers/firmware for the X540-T2 cards installed.

Cards are installed into the last slot, closet to the bottom of the case. I believe this is slot 8.

Looking for any help or guidance as to where/how to check temperatures and power to the cards. Or any other information that might help me control this overheating issue.

Thank you in advance!

Hi,

i want to know the power consumption of the I210-T1 and I350-T2 adapters cause I'm not sure

if it's right was the datasheed says.

Intel writes 0.81 Watt for the "Intel Ethernet Server Adapter I210-T1" but the "Intel Ethernet Server Adapter I350-T2" needs 4.40 Watt?

And then there is from HP the "E0X95AA Intel Ethernet I210-T1 GbE" where HP writes 3.00 Watt.

I believe the Intel and HP cards are nearly the same, so why that big difference.

Also i can use 5 "Intel Ethernet Server Adapter I210-T1" and still have lower power consumption then with 1 I350-T2?

Hello,

We are currently testing the implementation of 802.1x authentication using a computer certificate on our network.

The laptops used are Dell Latitude 6220 and Dell Latitude 7240 (I218-LM and 82579LM cards) and a Targus Universal USB Docking Station. (OS: Windows 7 Enterprise SP1)

When testing the configuration, the laptops are not able to authenticate when I use the Intel NIC giving this error:

Wired 802.1X Authentication failed.

Network Adapter: Intel(R) Ethernet Connection I218-LM
Interface GUID: {fce65701-1056-495e-8d36-f2c7b29dd4a2}
Peer Address: CCEF48D73A6B
Local Address: ECF4BB1443D7
Connection ID: 0x9
Identity: -
User: -
Domain: -
Reason: 0x50006
Reason Text: The authenticator is no longer present
Error Code: 0x0

Sometimes, I receive a strange "succeeded" message telling that the network does not support authentication then restart the authentication process :

Wired 802.1X Authentication succeeded.

Network Adapter: Intel(R) Ethernet Connection I218-LM
Interface GUID: {fce65701-1056-495e-8d36-f2c7b29dd4a2}
Peer Address: CCEF48D73A6B
Local Address: ECF4BB1443D7
Connection ID: 0xa
Identity: -
User: -
Domain: -
Reason: 0x70003
Reason Text: The network does not support authentication
Error Code: 0x0

When switching to the Embedded adapter in the Targus Docking station, I'm authenticated in less than 10 seconds:

Wired 802.1X Authentication succeeded.

Network Adapter: Targus Giga Ethernet
Interface GUID: {2cdbb8b0-0eec-42c3-a57b-7b8bc22ab354}
Peer Address: CCEF48D73A6B
Local Address: 0050B668D39D
Connection ID: 0x1
Identity: host/PC0022110.NBB.LOCAL
User: -
Domain: -
Reason: 0x0
Reason Text: The operation was successful
Error Code: 0x0

I've updated the laptops to the latest BIOS available, updated the Intel drivers to the latest available without success.

Any idea of what is causing this problem?

Gerald

Hello, first sorry for my bad english, i am from german.

I bought me the gamer PC acer aspire G5910 with Intel(R) 82579V lan adapter.

I loose the connection if i hear musik in spotify (i have windows 8.1 64bit)

or i loose the connection if open steam to play a game..every time.

i installed this driver: https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22026&ProdId=3299&lang=deu&OSVersion=Windows%208*&DownloadType=Utilities%2C%20Tools%20und%20Beispiele

i download it,unrar it,and then i open CMD with admin rights and i typed in: cd\users\myname\downloads and then i press enter,then i was in the folder downloads and then i type 82579VSKUW64e.exe

and i loose after the last command the lan connection,then i was connectet again with the internet.My internet is better now, but sometimes i loose the connection, or if i start steam/spotify.

Have anyone ideas or tipps for me?

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?

RESPECTED SIR, ITS BEEN 10 YEARS I HAVE BEEN USING  LAPTOP WITH INTEL INSIDE AND I AM VERY HAPPY FOR IT. RECENTLY I PURCHASED A NEW LAPTOP (HP PAVILION 15 P077TX) IN WHICH I AM UNABLE TO UPDATE MY GRAPHICS DRIVER.

I KNOW I AM INSTALLING THE RIGHT ONE BUT THE MESSAGE POPS UP WHEN TRYING TO INSTALL IS THAT the version is not compaitable I DONT UNDERSTAND IT. I AM NOT A FOOL. CPU - 4210U CORE i5 INTEL - 4400 WINDOWS - 8.1 64BIT PLEASE HELP ME TO GET MY GRAPHICS DRIVER 4400HD  AN UPDATE OR PLEASE GIVE ME THE LINK OF APPROPRIATE DRIVER TO INSTALL.

MY CURRENT VERSION OF INTEL DRIVER AS PER DEVICE MANAGER IS 10.18.10.3574 LAPTOP SERIAL NO - 5CD4245B77 BIOS (Configuration):F.07-06/23/2014 (0976100000405F10000610180) Product number:J6M42PA#ACJ THE VERSION THAT I AM TRYING TO INSTALL IS - https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24329

PLEASE REPLY ME WITH A SOLUTION SIR. I NEED AN UPDATE. I HAVE BEEN USING YOUR PRODUCT SINCE COUPLE OF YEARS AND I AM LOVING IT. NOTE - I HAVE CONTACTED HP COUPLE OF TIMES BUT NO SOUTION YET

Would anyone help to check what's wrong?

OS: Windows server 2012 R2

Driver: 12.11.97.1

Other configuration:  router and remove access enabled

Probably caused by : e1r64x64.sys ( e1r64x64+21494 )

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high.  This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: ffffe801de4ce009, memory referenced

Arg2: 0000000000000002, IRQL

Arg3: 0000000000000000, value 0 = read operation, 1 = write operation

Arg4: fffff80026f1e494, address which referenced memory

ADDITIONAL_DEBUG_TEXT: 

You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

FAULTING_MODULE: fffff803d7c11000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  53e3c3c0

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPagedPoolEnd

unable to get nt!MmNonPagedPoolStart

unable to get nt!MmSizeOfNonPagedPoolInBytes

ffffe801de4ce009

CURRENT_IRQL:  0

FAULTING_IP:

e1r64x64+21494

fffff800`26f1e494 0fb644300c      movzx   eax,byte ptr [rax+rsi+0Ch]

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  AV

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff803d7d707e9 to fffff803d7d64ca0

STACK_TEXT: 

ffffd000`8c3dd0a8 fffff803`d7d707e9 : 00000000`0000000a ffffe801`de4ce009 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx

ffffd000`8c3dd0b0 fffff803`d7d6f03a : 00000000`00000000 ffffe801`ddc84160 00000000`00000000 ffffd000`8c3dd1f0 : nt!setjmpex+0x37e9

ffffd000`8c3dd1f0 fffff800`26f1e494 : ffffe801`e06d8f00 00000000`00000000 00000000`00000000 00000000`00000002 : nt!setjmpex+0x203a

ffffd000`8c3dd380 fffff800`26f1f497 : 00000000`430005ac ffffe801`e06d1000 00000000`00000030 00000000`00000000 : e1r64x64+0x21494

ffffd000`8c3dd3d0 fffff800`26f205c2 : 00000000`430005ac ffffd000`8c3dd499 ffffe801`e06d1000 ffffe801`e06d1000 : e1r64x64+0x22497

ffffd000`8c3dd400 fffff800`26f1f771 : ffffe801`de238b00 ffffe801`e06d1000 00000000`00000000 ffffe801`ddc84198 : e1r64x64+0x235c2

ffffd000`8c3dd500 fffff800`26f1d149 : ffffe801`ddc84198 00000000`00000030 00000000`00000000 00000000`00000000 : e1r64x64+0x22771

ffffd000`8c3dd530 fffff803`d83a0a37 : ffffe000`d2dbf578 ffffe000`d2000050 ffffe000`d2dbf540 ffffe000`d2dbf540 : e1r64x64+0x20149

ffffd000`8c3dd570 fffff800`25a3520c : ffffe000`d2dbf540 ffffe000`d2000050 ffffe000`d2dbf540 ffffe000`d2dbf578 : hal!HalSendSoftwareInterrupt+0x567

ffffd000`8c3dd610 fffff800`26f2009b : ffffe000`d2ae4a30 ffffe000`d17aad00 ffffe000`d0cc6bb0 00000000`00000000 : NDIS!NdisMAllocateNetBufferSGList+0x20c

ffffd000`8c3dd6d0 fffff800`26f20437 : 00000000`00000001 00000000`00000000 00000000`0000000b 00000000`00000000 : e1r64x64+0x2309b

ffffd000`8c3dd740 fffff800`26f1d17e : 00000000`00000000 ffffd000`8c3dd8e0 00000000`00000000 ffffe000`cf6d0af0 : e1r64x64+0x23437

ffffd000`8c3dd7a0 fffff800`25a35a21 : 00002b83`0000001b 00000000`00000000 ffffd000`0000001c 00000000`0000000c : e1r64x64+0x2017e

ffffd000`8c3dd7e0 fffff800`2632d97b : ffffe801`e02a8c10 ffffe000`d0cc6a50 00000000`00000000 00000000`00000002 : NDIS!NdisSendNetBufferLists+0x551

ffffd000`8c3dd9d0 fffff800`26320862 : fffff800`26498180 00000000`00000000 00000000`e0000000 ffffe000`cd840800 : tcpip+0x5b97b

ffffd000`8c3ddb10 fffff800`2643a498 : ffffe000`cf6e1890 00000000`00000000 00000000`00000001 ffffd000`88a37900 : tcpip+0x4e862

ffffd000`8c3dde90 fffff800`26548f05 : 00000000`00000002 ffffd000`8c3ddfd0 ffffd000`88a379a1 ffffd000`88a4cbc0 : tcpip+0x168498

ffffd000`8c3ddef0 fffff803`d7d685f7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : fwpkclnt!FwpsVirtualIfTunnelInfoGet0+0x141

ffffd000`8c3ddf80 fffff803`d7d685bd : ffffe000`c43ad01a 00000000`00000000 00000000`00000000 fffff803`d7cddad8 : nt!KeSynchronizeExecution+0x2d07

ffffd000`88a377b0 fffff803`d7cddad8 : ffffe000`c43af1e8 fffff800`00000019 00000000`00000000 fffff800`00000001 : nt!KeSynchronizeExecution+0x2ccd

ffffd000`88a377d0 fffff800`2655a4a8 : fffff800`26548e20 ffffd000`88a37930 00000000`00000010 00000000`00000001 : nt!KeExpandKernelStackAndCalloutEx+0x238

ffffd000`88a378c0 fffff800`27678a8a : ffffe000`d0cc6a50 ffffe000`cad0c808 ffffe000`cad0c800 00000000`00000003 : fwpkclnt!FwpsInjectNetworkReceiveAsync0+0x22c

ffffd000`88a379e0 fffff800`25b53d05 : ffffe000`c45d6820 ffffe000`cad0c830 00000000`00000000 00000000`00000000 : ipnat+0x17a8a

ffffd000`88a37a70 fffff800`25b490c5 : ffffe000`cf3a0008 ffffd000`88a380a0 00000000`00000000 ffffe000`d28fe030 : NETIO!KfdDiagnoseEvent+0x395

ffffd000`88a37b90 fffff800`263765c6 : ffffd000`88a381d0 ffffe000`cad0c830 ffffe801`e0671000 ffffe000`cad0c600 : NETIO!KfdClassify+0x205

ffffd000`88a38010 fffff800`263760bf : 00000000`00000000 00000000`00000000 ffffd000`88a38250 ffffe801`ddd26140 : tcpip+0xa45c6

ffffd000`88a38150 fffff800`263209b3 : fffff800`26498180 ffffe000`cf6d0ae0 00000000`e0000001 00000000`00000000 : tcpip+0xa40bf

ffffd000`88a38290 fffff800`26316ded : ffffe000`cf6e1890 00000000`00000000 ffffd000`88a38601 fffff800`26c8a700 : tcpip+0x4e9b3

ffffd000`88a38610 fffff800`26316995 : ffffe000`cf6d0002 00000000`00000000 fffff800`26316750 00000000`00000001 : tcpip+0x44ded

ffffd000`88a38700 fffff803`d7cdd9a6 : ffffe000`cf6890b8 00000000`00000000 ffffe000`cd929610 ffffd000`88a34000 : tcpip+0x44995

ffffd000`88a38830 fffff800`26316a96 : fffff800`26316840 ffffd000`88a38950 ffffe000`00000010 00000003`00000597 : nt!KeExpandKernelStackAndCalloutEx+0x106

ffffd000`88a38920 fffff800`25a2f903 : 00000000`00000000 ffffd000`88a38a01 ffffd000`00000002 ffffd000`88a38a30 : tcpip+0x44a96

ffffd000`88a389a0 fffff800`25a3008a : 00000000`00000001 ffffd000`87400008 00000000`00000000 00000000`00000002 : NDIS!NdisAcquireRWLockWrite+0x593

ffffd000`88a38a60 fffff800`26c89b70 : ffffe000`d2845030 00000000`c0000001 ffffe000`d0ef0b60 ffffe000`d2465000 : NDIS!NdisMIndicateReceiveNetBufferLists+0x32a

ffffd000`88a38c40 fffff800`26c9ecb5 : ffffe000`00000000 ffffd000`88a30000 ffffd000`88a38d50 00000000`00000000 : vmswitch+0x4b70

ffffd000`88a38cf0 fffff800`26c9bd8a : ffffe000`d2460000 ffffe000`d2465000 ffffe000`d0ef0b01 fffff800`26c87701 : vmswitch+0x19cb5

ffffd000`88a38dd0 fffff800`25a2f903 : 00000000`00000000 00000000`00000000 ffffd000`88a38e91 00000000`0000c001 : vmswitch+0x16d8a

ffffd000`88a38e30 fffff800`25a3f29b : ffffd000`8801ff98 fffff800`26c88247 ffffe000`00000000 ffffe801`00000001 : NDIS!NdisAcquireRWLockWrite+0x593

ffffd000`88a38ef0 fffff800`25a308f6 : ffffe000`ceb8f1a0 00000000`00000001 00000000`00000000 00000000`00000000 : NDIS!NdisFIndicateReceiveNetBufferLists+0x36b

ffffd000`88a38f80 fffff800`26c889c9 : ffffe000`d2465000 ffffe801`de77e000 ffffe000`d0ef0b60 ffffe000`d0ef0b60 : NDIS!NdisMIndicateReceiveNetBufferLists+0xb96

ffffd000`88a39160 fffff800`25a35a21 : ffffe000`ceb4e000 ffffd000`88a39301 00000000`00000000 00000000`00000021 : vmswitch+0x39c9

ffffd000`88a392f0 fffff800`26c8e347 : ffffe000`cf687c10 ffffe000`d0ef0b60 ffffe000`00000000 00000000`00000000 : NDIS!NdisSendNetBufferLists+0x551

ffffd000`88a394e0 fffff800`26c8d3f7 : ffffe000`d0ef0b00 ffffe000`d0ef0b60 ffffe000`d2465000 ffffe000`d2465000 : vmswitch+0x9347

ffffd000`88a395b0 fffff800`26c8d128 : ffffe000`d08c0b00 ffffd000`88a39760 00000000`00000000 00000000`0000ff02 : vmswitch+0x83f7

ffffd000`88a39660 fffff800`261c41e0 : 00000000`00000003 ffffe000`cf526a02 00000000`00000034 00000000`000005ea : vmswitch+0x8128

ffffd000`88a39790 fffff800`26189e3d : 00000000`00000001 ffffe000`d226e010 000090d0`eb3d26c2 00000000`00000000 : vmbkmclr+0x21e0

ffffd000`88a39810 fffff803`d7c54130 : ffffd000`88a39960 ffffe000`cd9cc140 ffffd000`88a40180 fffff803`d7c76ae0 : vmbusr+0x3e3d

ffffd000`88a39860 fffff803`d7c5334b : ffffd000`88a40180 ffffe000`ce19a430 ffffe000`cd808260 ffffd000`88a40180 : nt!KeRemoveQueueEx+0x4550

ffffd000`88a399b0 fffff803`d7d687ea : ffffd000`88a40180 ffffd000`88a40180 ffffd000`88a4cbc0 ffffe000`d0cb1080 : nt!KeRemoveQueueEx+0x376b

ffffd000`88a39c60 00000000`00000000 : ffffd000`88a3a000 ffffd000`88a34000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x2efa

STACK_COMMAND:  kb

FOLLOWUP_IP:

e1r64x64+21494

fffff800`26f1e494 0fb644300c      movzx   eax,byte ptr [rax+rsi+0Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e1r64x64+21494

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e1r64x64

IMAGE_NAME:  e1r64x64.sys

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner

---------

I've been running a new machine with an i350-T2 NIC in it for several months without a hitch until today, when I booted the machine (prior shutdown had been clean) and noticed that there was no network connection. I checked in Windows Network Connections, and both i350 interfaces were absent. I then looked in Device Manager, and the NIC was not listed there either. I immediately rebooted into a Windows PE 3.1 environment (from a flash drive), and it showed the i350 working perfectly. Then I rebooted again back to my normal install of Windows, and the i350 was back to working like nothing had ever happened. There were no errors in Event Viewer.

What am I to make of this? Is this a once-off freak event that can be safely ignored?

i need help with my

Intel Network 7260.HMWG WiFi Wireless-AC 7260 H/T Dual Band 2x2 AC+Bluetoooth

i cannot see the adapter in my device manager. i update my bios to the latest version. i am running windows 7pro. can anyone help please

Hello! I have anintel i210 and EEPROM Winbond 25Q16. I want toconfigurethecontrollerto workwith theoptical moduleOptocore OTB1250-3520. I configuredEEPROM in Fiber mode,writing 0x1536 to a memory location. My optical module is not working. I setSFP module. He is working! Prompt how tomake it workOptocoreoptical module? I am sorry formy bad English. Attachesdatashitsandwaveform!

Also, I have a workingmoduleOptokoreand itswaveform.

Thank you!

Hi,

I'm trying to install Intel PROSet with MDT. So the install folder is a remote share (\\MDT\DeploymentShare$\Applications\Intel).

With the previous version, I used the msi (PROSETDX.msi) but with the new version it's impossible because there is a check to force the use of DxSetup.exe.

But DxSetup crash at the end of the installation.

How I can install this tool with MDT ?

Stephane.

Hello,

We have a need to be able to capture:

* The FCS field of Ethernet frames (RX_FCS in ethtool parlance)

* Bad packets, even if FCS/CRC is incorrect (RX_ALL in ethtool parlance)

* The union of both (i.e the incorrect FCS for 'bad' packets)

at 10G on Windows.

Having both of these enabled allows us to capture what we need. (I.e. An Arista switch timestamping in replace-fcs mode)

Under Linux, RX_ALL is already supported we are able to extend ixgbe to support RX_FCS (by toggling clearing CRCSTRP bits in HLREG0 and RDRXCTRL). This works perfectly (we understand this is mutually exclusive with IPSec or LinkSec)

Under Windows (Server 2008 r2) we have experimented with banging the registers directly in PCI IO space, and despite being a nasty hack, seems to work - we can capture the FCS fields under windows, as necessary with wireshark.

So my question is - how would we best go about formally requesting these as official windows/linux driver features for ixgbe? The procedure we're experimenting with is likely not suitable for production as it stands now.

Thanks,

David M

Hi,

For Study and home use I build a small computer with the following components:

Mobo : Asus Intel 1150 H97M-Plus

CPU : Intel Core i3-4150

Ram : 2x Kingston HyperX 4GB DDR3 1600 (9-9-9) Blu 2K

PSU : Seasonic S12II-430

HDD : 2x 2TB WD Green (RAID 1)

HDD : 2x 500GB (leftovers from another computer )

HDD : 1x 1TB (leftover from another computer )

As host I installed Hyper-V 2012 R2 but as soon the sconfig.cm started my screen shows an error....No active networkcontroller detected

The light (ornage and green) on the back are working so It should be an driver error. What ever I found on the internet, it ain't working. I even switched to Server GUI version via a brand new installation to accualy be able to see what is going on and today I noticed something strange.

I downloaded the Driver cd from the Intel side here and followed instructions. On some installation point I see the driver for the I218-V nic is being installed but after a few secs the error message appears with

Cannot Install the drivers. No Intel Adapters are present in this computer.

So I tried it another way. via update driver in the Device management console. That resulted in this error:

Windows found driver software for your device but encountered an error while attempting to install it.

Intel(R)Ethernet Connection(2)I218-V

The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.

These are untempered fresh unzipped drivers directly for the Intel site!!

I realy don't know what I can do more and I realy hope someone out here is and can point me into the correct directions

The final solution must be that I can install the drivers under Hyper-V 2012 R2.

Ill attach some screenies and the readme file from the NDIS64 folder which clearly states that those drivers in that folder are also for W2K12 R2.

We have two Cisco C240 servers running Windows Server 2008 R2 Datacenter with X540 cards directly connected with cat 6A cord and they only run 0.1 Gbps (1%) with iperf. What am I doing wrong?

Intel site lists driver as PROWinx64.exe version: 18.4 (Latest) Date: 07/19/2013, but Cisco installed Intel driver 3.9.58.9101 7/11/2014 and it seems to work other than the performance.

hello

iam developing board with 82579 chip.

datasheet says that this chip should be connected to the Intel 6 Series Express Chipsets.

can i connect 82579 via PCIe to CPU with integrated chipset? (Intel Atom E3826 for example)

thank you.

I'm posting here in the hope that someone has seen symptoms like this and can

offer some insight as to what's going on.

Executive summary: We have a newly-installed E1G44ET2BLK 4-port server adapter;

following a server reboot, we found that the ethernet jacks on that card had

been reordered! How did that happen, and how do we prevent it?

Here's how ifconfig saw this card after it was installed, with an ethernet

cable plugged into the bottom jack:

igb0: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 13

        inet 0.0.0.0 netmask 0

igb1: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 14

        inet 0.0.0.0 netmask 0

igb2: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 12

        inet 0.0.0.0 netmask 0

igb3: flags=1001000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,FIXEDMTU> mtu 1500 index 5

        inet 171.64.175.54 netmask fffff800 broadcast 171.64.175.255

We checked every port on the card one at a time by plugging in an ethernet

cable and running ifconfig to see which network interface showed valid link

status (the RUNNING bit). We labeled the jacks b0 through b3 on the back panel; no

surprise, they were ordered top-to-bottom, b0 to b3.

After a server reboot, ifconfig showed the following:

igb0: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 13

        inet 0.0.0.0 netmask 0

igb1: flags=1000802<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 14

        inet 0.0.0.0 netmask 0

igb2: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 12

        inet 0.0.0.0 netmask 0

igb3: flags=1001000843<UP,BROADCAST,MULTICAST,IPv4,FIXEDMTU> mtu 1500 index 5

        inet 171.64.175.54 netmask fffff800 broadcast 171.64.175.255

Notice that igb3 is no longer RUNNING; igb1 shows as RUNNING, instead. Yet the

cable had not been moved! It's still plugged in to the bottom jack. What's

changed is the mapping from network device name to physical port: the bottom

jack, which used to be igb3, is now igb1. And igb1, which used to be the 2nd

jack down from the top, is now the bottom jack. Our carefully-applied labels

are now wrong!

To restore network connectivity, I had to move the cable from the bottom jack

to the 2nd jack down. This restored RUNNING status to igb3.

We can't live with network jacks that move around on our server every time

we reboot. How is this remapping happening? Is this a feature of the E1G44ET2

card? An issue with the card's firmware? A device driver or OS problem?

The OS is NexentaStor v3.1.3 Enterprise (SunOS Release 5.11, OpenSolaris

Build 134). Server node is based on the Xyratex OneStorHS 1235T chassis.

Driver version is apparently 1.1.18:

# modinfo | grep igb

179 fffffffff8084000  1e178 284   1  igb (Intel 1Gb Ethernet)

# strings /kernel/drv/amd64/igb | grep igb

igb 1.1.18

-- Kai Lanz            Stanford University        School of Earth Sciences

Hi,

I need receive packets from NIC on 10G speed with zero use CPU.

In linux there is PF_ring, but i have not found such decision in Windows

it's really to receive packets from X540 NIC direct to userland in Windows?

Need to write a driver or Intel PRO driver able this function and enough CreateFile/DeviceIOControl in our app?

I have a new Dell E5540 laptop with intel i218-lm network adapter which I normally leave connected to the network.  Whenever the laptop goes idle for a long time, I cannot access the network (IE cannot connect to any websites including intranet sites, Outlook cannot connect to O365 etc.).  Same issue for both wired and wireless.  I've updated the nic drivers and make every possible changes to prevent the laptop from hibernating/sleep.  To get this machine going again, I have to log off my profile and log on again.  Very annoying!!  I'm not sure why this action wakes up the network but it does.  Any ideas how I can fix this once and for all aside from dumping it in the garbage?