Quantcast
Channel: Intel Communities : Discussion List - Wired Ethernet
Viewing all 4405 articles
Browse latest View live

I219-LM & Certified drivers for Windows 10?

$
0
0

Purchased in december the newly released asus workstation motherboard Z170-WS that included one I210 adapter and one I219-LM.

I was expecting to use ANS Teaming and VLAN features (still waiting on update drivers to fix these features generally on Win10)
But i don't see the I219-LM listed as supported for the Network Adapter Driver for Windows® 10, and searching on I219-LM it only list with drivers with OS Independent.

 

Will we that have purchased newly workstation motherboards with dual internet adapters in this case I210 and I219 not being able to use ANS features and VLAN on both connections?
Or is only missing due to being a new model?


Driver Winpe 5 x86 for HP 840 G3 (Intel I219-V) for landesk

$
0
0

Hello,

 

I need driver Winpe 5 x86 for hp elitebook 840 g3.


I have test with E1D6332.inf it's don't work.


Where can i find the good driver?

 

Thanks,

I350-T4 - Driver Features Missing - pci\ven_8086&dev_1521&subsys_00a18086

$
0
0

Hello,

 

I have an issue with I350 Quad port NIC with driver version 20.7. The following features are missing on port 1,2 and 3:

  • *WakeOnPattern
  • *WakeOnMagicPacket
  • ReduceSpeedOnPowerDown
  • *PMNSOffload
  • *PMARPOffload

 

On port 0 are the missing features are available.

Do somebody knows something about that issue.

 

Kind regards

Matthias

I217 support removed from the UEFI Ethernet Driver

$
0
0

I tried using the 20.7 UEFI Ethernet Driver E7006X3.EFI, but I see that I217 support has been removed.  Why? 

 

I need I217-LM support in this driver.

 

Going back I see the last time it was in the Driver was version 20.0, E6604X3.EFI.

 

Can I217 support please be added back into future builds?

 

Thank You

40 sec negotiation with X540-T1 with Cisco Nexus 3172TQ

$
0
0

Hi,

Have a client experiencing the following issue - when they boot or reboot a workstation, the LAN adapter takes 40+ seconds to negotiate with the LAN switch before it connects.

 

Details:

Workstations are Windows 7 Pro with Intel Ethernet Converged Network Adapter X540-T1 running SSD drives. So they boot within seconds, and when the users go to sign on, system connects before network is available, thus network maps are not completed, etc. Once the system negotiates the link and is online, a log off / log on cycle works properly. (And the users tend to forget between system reboots that they need to be patient. Thus wasted support calls troubleshooting.)

 

 

Switch is Cisco Nexus 3172TQ (48 port 10GBase-T)

Cisco firmware has been patched recently.

 

Any suggestions on what to focus on / investigate in depth? Opening a case with Cisco as well. Will also look for Cisco commands etc.

 

Thanks

Link state flap with traffic does not recover for SR-IOV VFs

$
0
0

Using DPDK 2.3 and ixgbe driver 4.13.15.  When there is no traffic on the link and it is flapped, the VFs recover the link state properly.  When there is too much traffic though, the link state can't be recovered for VFs.  It seems to be caused by the PF driver putting the VF in a not clear to send state.  Since the VF is not clear to send, it can't retrieve the link state via the mailbox.  It looks like this can be fixed by restoring the clear to send state in the PF after the cleanup on state down:

 

*** ixgbe_main.c        2016-05-09 11:07:44.365431345 -0400

--- ixgbe_main.c.bak    2016-05-09 11:07:22.309430641 -0400

***************

*** 6128,6140 ****

 

        ixgbe_clean_all_tx_rings(adapter);

        ixgbe_clean_all_rx_rings(adapter);

-

-         if (adapter->num_vfs) {

-

-                 /* Mark all the VFs as clear to send again */

-                 for (i = 0 ; i < adapter->num_vfs; i++)

-                         adapter->vfinfo[i].clear_to_send = 1;

-         }

  }

 

  /**

--- 6128,6133 ----

 

Thoughts?  Not sure why it works without above fix when traffic is light.  The DPDK does resets here and there for the VF so perhaps timing makes a difference at restoring the clear to send state.

 

Thanks.

Queue issue about XL710

$
0
0

Hi,

 

I met some issues with XL710 NIC on FreeBSD10.1.

The NIC is a dual-port 40G card with the latest NVM image. CPU is 2690 V2 with hyperthreading to 40 logical cores.

Part number as XL710-QDA2 932587.

Firmware info:  f5.0 a1.5 n05.02 e80002285

Driver info: 1.4.8.

 

Issue1:

Within 20 queues only 16 of them are receiving packets (que0 - que15),

Que16-que19 are generating interrupt but no packet available, status/error register value are all 0.

 

AN# sysctl dev.ixl.2 | grep rx_packet

dev.ixl.2.pf.que0.rx_packets: 8805610

dev.ixl.2.pf.que1.rx_packets: 9348787

dev.ixl.2.pf.que2.rx_packets: 8505388

dev.ixl.2.pf.que3.rx_packets: 9928934

dev.ixl.2.pf.que4.rx_packets: 3879181

dev.ixl.2.pf.que5.rx_packets: 5579101

dev.ixl.2.pf.que6.rx_packets: 4322241

dev.ixl.2.pf.que7.rx_packets: 5788389

dev.ixl.2.pf.que8.rx_packets: 5575891

dev.ixl.2.pf.que9.rx_packets: 3743182

dev.ixl.2.pf.que10.rx_packets: 4127868

dev.ixl.2.pf.que11.rx_packets: 3878214

dev.ixl.2.pf.que12.rx_packets: 4013070

dev.ixl.2.pf.que13.rx_packets: 5146686

dev.ixl.2.pf.que14.rx_packets: 4024729

dev.ixl.2.pf.que15.rx_packets: 4736103

dev.ixl.2.pf.que16.rx_packets: 0

dev.ixl.2.pf.que17.rx_packets: 0

dev.ixl.2.pf.que18.rx_packets: 0

dev.ixl.2.pf.que19.rx_packets: 0


Issue2:

The NIC may hang under heavy stress, like putting 60Gbps traffic into it.

It may stop generating interrupt in such case.

 

Could you please help check the above issues?

Great thanks.

 

Regards,

Jingxun

Cannot control XL710 VF interrupte rate

$
0
0


Hi,

 

I'm doing the tuning job for XL710 VF on a FreeBSD10 VM (driver is ixlv-1.2.11) hosted on a kvm-hypervisor server (pf driver is i40e-1.4.25).

I found for each queue of the vf the interrupte rate is very high (>10000/sec).

As said in the datasheet, I tried to set I40E_VF_ITRN by the VF driver and set I40E_VPINT_RATEN by the PF driver. But this didn't work.

I have upgraded the NVM to 5.02 the latest version.

 

Could anybody help me resolve the issue?


X540-T2 3.15.3 ixgbe bypass driver update

$
0
0

Hi,

 

I'm a new AE and I'm looking for some information concerning 3.15.3 Intel 10 Gigabyte Ethernet bypass driver.
I would like to know where can I find it as I can't see anything on download center. I need to find whether there is some update for this version.

Will appreciate any kind of help

I211/I217-V Windows 10 LACP teaming fails

$
0
0

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

I219-LM & I210-T1 Teaming

$
0
0

Hi.

 

I have 2 NIC in my HP Z240 workstation, Intel I219-LM & I210-T1 models and i want to work with Team between them.

 

Is possible? i read about error in teaming with this card in windows 10.

 

You have some solution to this problem?

I218-LM nic windows 10 drivers for advanced use

$
0
0

Hey,

 

On my Dell latitude E7450 ultrabook, the nic card is a I218-LM.

Is the developpement for windows 10 advanced software for this card is in progress ?

 

Vlans management is important and this fonction is not enable.

 

Thank you

Please help with receive setup of a 82574 based NIC

$
0
0

I am developing a Miniport device driver for an 82574l based NIC on Windows CE 5.0, using NDIS 5.1. Transmission setup works OK and the NIC transmits OK. I setup receive as the documentation dictates:

  1. Allocated a region of memory for legacy receive descriptor list using NdisMAllocateSharedMemory and setup a descriptor ring.
  2. Setup receive buffers of appropriate size and allocated and pointers to these buffers and stored these in each descriptor in the descriptor ring.
  3. Programed the descriptor base address with the address of the descriptor ring.
  4. Set the length register to the size of the descriptor ring.

However the when I process receive related interrupts the memory buffers pointed to by the memory allocations I got from NDIS point to regions filled with 0s. Using the diagnostic registers it shows that data was received and the Receive Data FIFO Packet Count register indicates how many packets were received and analyzing the RX FIFO PBM region seems good. So I must be doing something really bad when setting up my RX registers to not be able to handle RX packets. I will gladly provide my code to anybody who can help me.

X520-DA2 + FTLX8571D3BCV-IT | Will these two will work together?

$
0
0

Hi!

 

I have question about compatibility of NIC with Intel's transcievers?

 

I have two transcievers made by Intel FTLX8571D3BCV-IT (E65689-001) and want to plug them into X520-DA2 (E10G42BTDA) for iSCSI booting?

 

I searched Internet but found nothing specyfic about about my question.

 

Thanks in advance.

Sylwek.

X540-T2

$
0
0

Bonjour,

j'ai un dell precision t3420 avec un pcie x16 dispo. j'aimerai savoir si je peux mettre la carte x540-t2 qui est en x8 sur cet emplacement?

merci


Problem with Flow Director filter and statistic registers

$
0
0

Hi!

 

I'm a student at Umeå University and I am currently using an Intel® 82599EB 10 Gigabit Ethernet Controller to send and receive network packets. I'm using the Flow Director filter to direct the packets into different rx queues, and I want to use the queue statistic registers (QPRC and QPRDC) to count the number of received packets at each queue.

 

However, the numbers are not correct! The GPRC register gives one number for the total amount of received packets (which is correct, it's the same as the amount of sent packets), while summing the queue statistics gives another number, lower than the GPRC. Shouldn't these be the same? It works at low speeds, <5 Gbit/s, but not for speeds higher than that. All packets should be matching the filters. Where/why are packets lost after being received and counted at the GPRC register, but before being placed in a queue and counted at the queue statistics?

 

 

Any other suggestions for ways to count packets divided into different groups/queues are also very appreciated if the solution with the Flow Director filter and queue statistics is not working!

 

 

Thanks!

Johan Nilsson

[e1000e/82579LM] Speed up network reachability on resume

$
0
0

Hello all,

 

For research purposes I am trying to improve the resume latency of a Linux machine, and specifically I need to speed up its network responsiveness when it wakes up from suspend-to-RAM. I have managed to get a latency of about 3s for now and I am looking for clues to further shorten this delay.

 

My setup includes an Intel 82579LM Gigabit NIC, which is controlled by the e1000e driver in the Linux kernel (the computer runs ArchLinux). For now it is only linked to my laptop so I have full control over the network characteristics.

 

On this setup, DHCP is disabled, as well as auto-negotiation; link speed and duplex mode are forced to 100Mbps full duplex. These (somewhat unrecommended) settings allow for a response time of about 3s on resume. This time is obtained by querying a very light HTML page via an Apache server running on the target machine.

 

So now I need to find other ways to shorten the delay. According to dmesg, the driver itself only takes about 50ms to wake up, and it is the restoration of the link that takes up a lot of time. Essentially, I need some ideas to quicken the process to restore the Ethernet link.

 

What is important here is that the NIC is waking up from suspend-to-RAM (and WoL enabled of course) so it might be interesting to avoid some steps when setting it up again because it is safe to assume the network hasn't changed during the sleep period. In the ideal case I would like a way to either keep the link up when the NIC goes to sleep (it stays almost awake because of the wake-on-LAN after all) or to have the link immediately available on resume.

 

So here I am asking for your help. If you have any hints about how these suggestions could be achieved, or any other idea about this, please answer And thank you!

Intel 10Gbit Card X540-T1 changes its Hardware ID?

$
0
0

Hi,

 

we have bought 3 of these expensive cards and for the second time now the following has happened:

 

these cards came as

 

PCI\VEN_8086\DEV_1528\&SUBSYS_00028086

 

and the installation of the the newest Win7 64bit drivers 20.3 went just fine and the network card worked

perfectly. The problem now is, once the PC shut down/cold booted the network disappeared and instead

an unknown ethernet controller is found by the device manager listed as follows:


PCI\VEN_8086\DEV_1512\&SUBSYS_00008086


It is then of course not possible anymore to install any driver for it, not even manually

inserting DEV_1512 into the .inf file works (device cannot be started code 10). Also

the Ctrl-S dialog to get into the card doesn't come up anymore after the Bios screen.

It looks as if the card is brain dead or several bits flipped or whatever.


This is now the second time under Win7 64bit with an HP 8100 Workstation. Under

Win81 64bit on a 2 Dell workstations the cards work very well even after several

complete shutdowns.


What can we do? Why and how does this happen? I have already RMA'd one card

and got a replacement but now the same is happening again and we can not believe

what we see. Hardware ID's are changing, how's that possible, what's going on??


What should we do with this, does anyone have any idea how this can be fixed???

Any help please? Thank you!


 





the Teaming Feature, need to be supported in PHY or not?

$
0
0

for the teaming feature, does it should be supported in PHY?

if yes, which kind of PHY can support the feature.

the requirements of PHY as below:

1. PCIe interface

2. 10M/100M/1000M

3. Teaming Feature

I211/I217-V Windows 10 LACP teaming fails

$
0
0

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

Viewing all 4405 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>