Hi,

I have read somewhere that Intel is NOT (directly) responsible for whatever Intel driver Microsoft is pushing through Windows update.

However I would like to ask a question, after a bit of context.

I have business laptop configured Windows 7 Enterprise, x64, SP 1:

     Microsoft Windows [Version 6.1.7601]

absolutely up to date.

The wired network is built with

     "Intel® Ethernet Connection (2) I219-LM"

so I have installed latest version of

     "Intel® Network Adapter Driver for Windows 7 / ProWin64.exe"

which is Version:21.1 (Latest)Date:10/11/2016

the specific version on the file driver as shown in Device Manager being:  12.15.23.7 dated 07/26/2016

So far so good.

Then why Microsoft Windows Update for Windows 7 keeps pushing a obsolete driver dated November 2015 update with the following description:

     Intel - LAN, LAN (Server) - Intel(R) Ethernet Connection (2) I219-LM

     Download size: 731 KB

     You may need to restart your computer for this update to take effect.

     Update type: Optional

     Intel LAN, LAN (Server) software update released in November, 2015

I mean even if it is optional, what is the point ? because it is definitely confusing.

What do you think ?

Please advise.

Hassan

PB for upgrading Driver for this card

during upgradind msg "impossible to upgrade driver installed, remove before upgrading"

i have desintalled the old driver et reboot

But i always read the same msg inquiring to remove old driver ??????

have a special program to ensure remove for the old driver ???

old driver is dated : 10/08/2012 and version number is : 12.2.45.0

best reagards

Patrick Larquey

#first server

root@sdb-1 ~]# fcoeadm -i p6p2.1002-fcoe

    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection

    Revision:         01

    Manufacturer:     Intel Corporation

    Serial Number:    90E2BA26EE3E

    Driver:           ixgbe 3.21.2

    Number of Ports:  1

        Symbolic Name:     fcoe v0.1 over p6p2.1002-fcoe

        OS Device Name:    host11

        Node Name:         0x1000001B2194DC83

        Port Name:         0x2000001B2194DC83

        FabricName:        0x100050EB1AF120AC

        Speed:             10 Gbit

        Supported Speed:   1 Gbit, 10 Gbit

        MaxFrameSize:      2048

        FC-ID (Port ID):   0x050000

        State:             Online

#second server

[root@dct1 ~]# fcoeadm -i p6p2.1002-fcoe

    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection

    Revision:         01

    Manufacturer:     Intel Corporation

    Serial Number:    90E2BA0DE616

    Driver:           ixgbe 3.21.2

    Number of Ports:  1

        Symbolic Name:     fcoe v0.1 over p6p2.1002-fcoe

        OS Device Name:    host11

        Node Name:         0x1000001B2194DC83

        Port Name:         0x2000001B2194DC83

        FabricName:        0x0000000000000000

        Speed:             10 Gbit

        Supported Speed:   1 Gbit, 10 Gbit

        MaxFrameSize:      2048

        FC-ID (Port ID):   0x000000

        State:             Linkdown

Dear Intel Community

In our device we have two WGI210IT ethernet controllers and we are facing an issue with them: Very rarley, let's say less than once per 100 boot ups, we see that the device ID is 1531 instead of 1533. At the moment we cannot reproduce it, it just appears sometimes on our devices.

lspci under linux shows it like this:

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

02:00.0 Ethernet controller: Intel Corporation Device 1531 (rev 03)

After a reboot the Ethernet controller has ID 1533 again:

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

Early at bootup of Linux the following message apears:

kernel: pci 0000:02:00.0: [8086:1531] type 00 class 0x020000

So it we doubt that any operating system related action causes the wrong ID.

The configuration is as follows:

- Ethernet controller firmware: Dev_Start_I210_Copper_SMB_8Mb_A2_3.25_0.03.bin

- Changes in Flash (On some devices done with Lanconf.exe under DOS and in others with eeupdate64e under Linux):

--> Word 0x20: Set bit 4 to '1' (disables Gbit Ethernet)

--> Changed MAC Address

- Gigabit Ethernet is not supported on HW side. MDI_PLUS_2 / MDI_MINUS_2 / MDI_PLUS_3 / MDI_MINUS_3 are pull-up to 1.5V via 49.9R resistors

- Flash: MX25L1606EZNI-12G

- 33R resistors in SPI lines (NVM_SI, NVM_SO, SVM_SK, NVM_CS#)

- Pin 12 is pulled-down with 10k (strap pin --> non secure mode)

Hardware checks:

- The I210 and the flash are powered from the same 3.3V source. First flash access happens after 25ms after 3.3V is reached. The flash itself requires 200us to be ready after Vmin is reached. So the flash is ready at first access.

- The signal levels of all SPI lines are fine.

- The solder points are checked and nothing wrong was seen.

We checked a few register values while the problem was seen:

Read at 0x90012010 | 0x40 0x2A 0x48 0x00 (Base address is 0x90000000)

The 1533 controller shows:

Read at 0x91312010 | 0x40 0x2B 0x08 0x06 (Base address is 0x91300000)

Differences:

EEPROM-Mode Control Register - EEC (0x12010) bit 8 is '0'. --> EE_PRES: No Flash with correct signature or empty iNVM

EEPROM-Mode Control Register - EEC (0x12010) bit 22 is '0'. --> Reserved: No info from datasheet

EEPROM-Mode Control Register - EEC (0x12010) bit 25 is '0'. --> SEC1VAL: Sector 1 not valid (but not meaning full due to bit 8 is '0')

EEPROM-Mode Control Register - EEC (0x12010) bit 26 is '0'. --> FLUDONE: No flash update done

Have you got any idea what could cause this problem?

Thank you in advance and best regards

Stefan

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,

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

Hello!

I have a problem with running X710-DA2 on my servers. When I try to load the i40e driver it crashes. It happened on a stock fw, drivers, etc. and on the upgraded versions too.

Platform: Supermicro X9DRW with dual Intel(R) Xeon(R) CPU E5-2620, latest BIOS

OS: Ubuntu 16.04.1 LTS, linux 4.4.0-57

NIC firmware: fw 5.0.40043 api 1.5 nvm 5.04 0x800024c6 0.0.0 (latest)

i40e driver: 1.5.25 (latest, downloaded and compiled)

Modules installed: GBC Photonics SP-MM85030D-GP -SFP+

dmesg:

Jan  3 18:01:58 ceph6 kernel: [  739.510036] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 1.5.25

Jan  3 18:01:58 ceph6 kernel: [  739.510041] i40e: Copyright(c) 2013 - 2016 Intel Corporation.

Jan  3 18:01:58 ceph6 kernel: [  739.527324] i40e 0000:04:00.0: fw 5.0.40043 api 1.5 nvm 5.04 0x800024c6 0.0.0

Jan  3 18:01:58 ceph6 kernel: [  739.765165] i40e 0000:04:00.0: MAC address: 3c:fd:fe:a2:19:54

Jan  3 18:01:58 ceph6 kernel: [  739.789909] i40e 0000:04:00.0: AQ command Config VSI BW allocation per TC failed = 14

Jan  3 18:01:58 ceph6 kernel: [  739.789912] i40e 0000:04:00.0: Failed configuring TC map 255 for VSI 390

Jan  3 18:01:58 ceph6 kernel: [  739.789915] i40e 0000:04:00.0: failed to configure TCs for main VSI tc_map 0x000000ff, err I40E_ERR_INVALID_QP_ID aq_err I40E_AQ_RC_EINVAL

Jan  3 18:01:59 ceph6 kernel: [  739.833189] divide error: 0000 [#1] SMP

Jan  3 18:01:59 ceph6 kernel: [  739.833324] Modules linked in: i40e(OE+) vxlan ip6_udp_tunnel udp_tunnel intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel ipmi_ssif kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni

_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper input_leds joydev sb_edac cryptd serio_raw edac_core ipmi_si mei_me 8250_fintek mei ipmi_msghandler shpchp ioatdma lpc_ich mac_hid autofs4 hid_generic usbhid hid psmouse isci

igb ahci libsas libahci dca ptp scsi_transport_sas megaraid_sas pps_core i2c_algo_bit wmi fjes

Jan  3 18:01:59 ceph6 kernel: [  739.835034] CPU: 0 PID: 2386 Comm: insmod Tainted: G           OE   4.4.0-57-generic #78-Ubuntu

Jan  3 18:01:59 ceph6 kernel: [  739.835306] Hardware name: Supermicro X9DRW/X9DRW, BIOS 3.0c 03/24/2014

Jan  3 18:01:59 ceph6 kernel: [  739.835518] task: ffff880868b9f000 ti: ffff88046c1c0000 task.ti: ffff88046c1c0000

Jan  3 18:01:59 ceph6 kernel: [  739.835754] RIP: 0010:[<ffffffffc03a4faf>]  [<ffffffffc03a4faf>] i40e_pf_config_rss+0x1ef/0x230 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.836059] RSP: 0018:ffff88046c1c37a0  EFLAGS: 00010246

Jan  3 18:01:59 ceph6 kernel: [  739.836227] RAX: 0000000000000000 RBX: ffff88086bd33c00 RCX: 0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.836452] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000200

Jan  3 18:01:59 ceph6 kernel: [  739.836679] RBP: ffff88046c1c3808 R08: ffff88046fc1a120 R09: ffff88046f8032c0

Jan  3 18:01:59 ceph6 kernel: [  739.836904] R10: ffff88086bd33c00 R11: 0000000000000000 R12: 0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.837130] R13: ffff88046da74008 R14: ffff88046c099000 R15: ffff88046da74000

Jan  3 18:01:59 ceph6 kernel: [  739.837359] FS:  00007f5815768700(0000) GS:ffff88046fc00000(0000) knlGS:0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.837615] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033

Jan  3 18:01:59 ceph6 kernel: [  739.837796] CR2: 00007fe8a4fcc13c CR3: 000000046a7f2000 CR4: 00000000000406f0

Jan  3 18:01:59 ceph6 kernel: [  739.838022] Stack:

Jan  3 18:01:59 ceph6 kernel: [  739.838085]  0000000000000005 00000000001c0ac0 00000000000e0000 ffff88046c1c37e8

Jan  3 18:01:59 ceph6 kernel: [  739.838335]  ffffffffc03b9e39 ffff88046da74f28 ffff88046da74008 00000000ffd84a52

Jan  3 18:01:59 ceph6 kernel: [  739.847061]  ffff88046da74000 0000000000000000 ffff88046da74008 0000000000000000

Jan  3 18:01:59 ceph6 kernel: [  739.855800] Call Trace:

Jan  3 18:01:59 ceph6 kernel: [  739.864529]  [<ffffffffc03b9e39>] ? i40e_write_rx_ctl+0x39/0x90 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.873487]  [<ffffffffc03a7ba8>] i40e_setup_pf_switch+0x308/0x590 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.882566]  [<ffffffffc03ab5c0>] i40e_probe.part.58+0xd50/0x1be0 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  739.891572]  [<ffffffff813fcbdd>] ? radix_tree_lookup+0xd/0x10

Jan  3 18:01:59 ceph6 kernel: [  739.900540]  [<ffffffff810da827>] ? irq_to_desc+0x17/0x20

Jan  3 18:01:59 ceph6 kernel: [  739.909424]  [<ffffffff810de48e>] ? irq_get_irq_data+0xe/0x20

Jan  3 18:01:59 ceph6 kernel: [  739.918278]  [<ffffffff81057695>] ? mp_map_pin_to_irq+0xb5/0x300

Jan  3 18:01:59 ceph6 kernel: [  739.927153]  [<ffffffff814b55cc>] ? acpi_ut_remove_reference+0x2e/0x31

Jan  3 18:01:59 ceph6 kernel: [  739.936072]  [<ffffffff811ed69b>] ? __slab_free+0xcb/0x2c0

Jan  3 18:01:59 ceph6 kernel: [  739.944972]  [<ffffffff81057e98>] ? mp_map_gsi_to_irq+0x98/0xc0

Jan  3 18:01:59 ceph6 kernel: [  739.953757]  [<ffffffff8104f72e>] ? acpi_register_gsi_ioapic+0xbe/0x180

Jan  3 18:01:59 ceph6 kernel: [  739.962466]  [<ffffffff81495726>] ? acpi_pci_irq_enable+0x1bf/0x1e4

Jan  3 18:01:59 ceph6 kernel: [  739.971114]  [<ffffffff817058c8>] ? pci_conf1_read+0xb8/0xf0

Jan  3 18:01:59 ceph6 kernel: [  739.979739]  [<ffffffff817093e3>] ? raw_pci_read+0x23/0x40

Jan  3 18:01:59 ceph6 kernel: [  739.988340]  [<ffffffff8143bc3c>] ? pci_bus_read_config_word+0x9c/0xb0

Jan  3 18:01:59 ceph6 kernel: [  739.996976]  [<ffffffff81444ced>] ? do_pci_enable_device+0xdd/0x110

Jan  3 18:01:59 ceph6 kernel: [  740.005459]  [<ffffffff81446104>] ? pci_enable_device_flags+0xe4/0x130

Jan  3 18:01:59 ceph6 kernel: [  740.013867]  [<ffffffffc03ac46e>] i40e_probe+0x1e/0x30 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  740.022228]  [<ffffffff81447585>] local_pci_probe+0x45/0xa0

Jan  3 18:01:59 ceph6 kernel: [  740.030571]  [<ffffffff814489c3>] pci_device_probe+0x103/0x150

Jan  3 18:01:59 ceph6 kernel: [  740.038806]  [<ffffffff8155a7a2>] driver_probe_device+0x222/0x4a0

Jan  3 18:01:59 ceph6 kernel: [  740.046946]  [<ffffffff8155aaa4>] __driver_attach+0x84/0x90

Jan  3 18:01:59 ceph6 kernel: [  740.055009]  [<ffffffff8155aa20>] ? driver_probe_device+0x4a0/0x4a0

Jan  3 18:01:59 ceph6 kernel: [  740.063118]  [<ffffffff815583cc>] bus_for_each_dev+0x6c/0xc0

Jan  3 18:01:59 ceph6 kernel: [  740.071205]  [<ffffffff81559f5e>] driver_attach+0x1e/0x20

Jan  3 18:01:59 ceph6 kernel: [  740.079029]  [<ffffffff81559a9b>] bus_add_driver+0x1eb/0x280

Jan  3 18:01:59 ceph6 kernel: [  740.086629]  [<ffffffffc01ea000>] ? 0xffffffffc01ea000

Jan  3 18:01:59 ceph6 kernel: [  740.093977]  [<ffffffff8155b3b0>] driver_register+0x60/0xe0

Jan  3 18:01:59 ceph6 kernel: [  740.101076]  [<ffffffff81446eac>] __pci_register_driver+0x4c/0x50

Jan  3 18:01:59 ceph6 kernel: [  740.107997]  [<ffffffffc01ea0a6>] i40e_init_module+0xa6/0x1000 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  740.114831]  [<ffffffff81002123>] do_one_initcall+0xb3/0x200

Jan  3 18:01:59 ceph6 kernel: [  740.121523]  [<ffffffff811ecbd3>] ? kmem_cache_alloc_trace+0x183/0x1f0

Jan  3 18:01:59 ceph6 kernel: [  740.128183]  [<ffffffff8118d9f3>] do_init_module+0x5f/0x1cf

Jan  3 18:01:59 ceph6 kernel: [  740.134706]  [<ffffffff8110a98f>] load_module+0x166f/0x1c10

Jan  3 18:01:59 ceph6 kernel: [  740.141064]  [<ffffffff81106f30>] ? __symbol_put+0x60/0x60

Jan  3 18:01:59 ceph6 kernel: [  740.147352]  [<ffffffff81214760>] ? kernel_read+0x50/0x80

Jan  3 18:01:59 ceph6 kernel: [  740.153662]  [<ffffffff8110b174>] SYSC_finit_module+0xb4/0xe0

Jan  3 18:01:59 ceph6 kernel: [  740.159956]  [<ffffffff8110b1be>] SyS_finit_module+0xe/0x10

Jan  3 18:01:59 ceph6 kernel: [  740.166220]  [<ffffffff818374f2>] entry_SYSCALL_64_fastpath+0x16/0x71

Jan  3 18:01:59 ceph6 kernel: [  740.172496] Code: 40 5b 41 5c 41 5d 41 5e 41 5f 5d c3 41 0f b7 be a8 04 00 00 31 c9 41 0f b7 b6 aa 04 00 00 66 85 ff 0f 84 5a ff ff ff 89 c8 31 d2 <66> f7 f6 88 14 0b 48 83 c1 01 66 39 cf 77 ed e9 42 ff ff ff 4c

Jan  3 18:01:59 ceph6 kernel: [  740.185825] RIP  [<ffffffffc03a4faf>] i40e_pf_config_rss+0x1ef/0x230 [i40e]

Jan  3 18:01:59 ceph6 kernel: [  740.192377]  RSP <ffff88046c1c37a0>

Jan  3 18:01:59 ceph6 kernel: [  740.215988] ---[ end trace ab2ce900f55f1c7a ]---

After that one of the interfaces appears in the system, but it's unaccesible:

root@ceph6:~# ip link set up eth2

RTNETLINK answers: Invalid argument

Kind regards,

Dominik

I was installing the latest drivers for my motherboard, I211 + I219-V on a fresh W10 x64, the 21.1 package.

I219-V work fine

But the new Drivers for I211 (at least, maybe others too) inside ProSet 21.1 are signed ¿Wrong? by INTELNPG1, and Windows refuse them with the classical Error 52.

ProSet 21.0, in other hands, work fine, the sign are correct. issued not by INTELNPG1, but Intel(R) Intel Network Drivers.

Not a drama, but it would be nice to install a properly signed driver to use it.

More strange, Drivers for I219-V are signed by INTELNPG1 too, and work fine (same cert)

What is the specific functionality of a PF(Physical Function)  in SR-IOV ? Also what is the difference between virtual function and a physical function ? Does the VF communicate with a PF during the transfer of a packet from the VM ?@

After long shutdown and then power up ( eg. Power up in morning ) 82579v adapter shows Windows driver code 10 - with media disconnected status in ipconfig.

Shutdown and restart does not fix.  Hard power off while machine running, wait 60 seconds and power on usually fix.  Bio reset default also fix.

Problem re-occurs if machine is shutdown and powered off for a few hours.

It is not cabling or router since problem is resolved by one of the above power cycle steps.

Configuration:

  Motherboard: Asus P8Z77-V Pro

  Bios: Asus 2104 ( latest )

  OS: Windows 10-x64

  Network Driver: Intel 12.5.31.4  / ProSet 21.1.30.0

Applied NVRam update ( 82579VSKU ) adapter is now 82579V - no longer bounces to LM.

Tried:

  Older BIOS

  Microsoft Windows 10 Driver

Problem appears similar to:

https://communities.intel.com/message/264820

https://communities.intel.com/thread/110194

Hi,

For a study, I would like to know the differences between two Intel Network driver versions (example: delta changes/fixes/improvements from v18.6 and v21.1)

In the Intel websites, I don't get this information. can you please update from where can I get these information?

Appreciate your help!

Hi,

I have few clarifications on the Receive side scaling (RSS) setting in a Windows 7 OS. I want to disable the RSS because it gives some performance issues, so executed the command "netsh int tcp set global rss=disabled" and when I checked at the Network adapter properties, I still see the Recieve side scaling is enabled.

1. I would like to understand the difference between setting the RSS disabled using the command and disabling the same using the Network adapter properties. (How it works, which takes priority)

2. Is there any known issues if the RSS is disabled using the command line.

please share any info on this topic.

Appreciate your help!

Regards,

Prabu

We are bringing up a new board with an XL710.

Need eeupdate/lanconf or whatever is now being used to program these.

Is the NVMupdate all that is needed?

What about the image file?

We've done 82576 and i210s in the past, has the process changed?

Thanks

Hello.

Trying to split XL710QDA1 in FreeBSD 12 and get:

[root@host ~]# ./qcu64e /devices                                                                                                                                                                                             [18:42:30]

Intel(R) QSFP+ Configuration Utility

QCU version: v2.27.10.01

Copyright(C) 2016 by Intel Corporation.

Software released under Intel Proprietary License.

NIC Seg:Bus Ven-Dev   Mode    Adapter Name

=== ======= ========= ======= ==================================================

zsh: segmentation fault (core dumped)  ./qcu64e /devices

[root@host ~]# gdb core qcu64e.core                                                                                                                                                                                          [18:43:21]

GNU gdb 6.1.1 [FreeBSD]

Copyright 2004 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB.  Type "show warranty" for details.

This GDB was configured as "amd64-marcel-freebsd"...core: No such file or directory.

Core was generated by `./qcu64e /devices'.

Program terminated with signal 11, Segmentation fault.

#0  0x00000000005051b1 in ?? ()

(gdb)

I tryed fw versions 4.22.26225 and  5.0.40043 . Driver we use 1.6.6.

And I succesfully split it from UEFI.

• We have been using the X710 and designers have been investing time in this card and driver
• If we wanted to look at the XL710 would it be transparent,  same driver and all?  or not?

I have a performance dilemma with the Windows 10 software/driver for an onboard I210 series LAN chipset.  I have two ASUS motherboards, Rampage IV – 82579V and P10S WS – I210, connected to a network.  The P10S WS is the server and the other is used as desktop.  With just these two components connected, I get about 85-90MB/s performance from a normal boot.  But, if I go into the P10S WS and change anything in the advanced configuration of the adapter, which makes the adapter restart, then my performance is 111-113MB/s (which is really good). After booting the P10S WS, I have to change something (i.e. speed from Auto to 1GB full duplex, even though it is running 1GB anyway) to get it to restart and run full speed.  Any help would be appreciated.  Running Intel latest drivers.

Windows 8.1 Enterprise 64 bit edition

ASRock QC 5000 ITX Mainboard

Intel Desktop CT GBe PCIe adapter

Using Proset release 21

The OS will automatically detect and bring the card up. What I'm needing in addition is the ANS suite so I can team adapters in a LAG.

The OS installation is brand new as of 4 hours ago to a 240GB SSD.

I am planning on getting a Asrock Rack E3C236D2I server motherboard, and the two on-board gigabit NIC's it has are the Intel i210 and the intel i219.

Just want to check both the i210 and the i219 both support VLAN tagging. Planning on using Windows Server 2016 essentials.

Also what is the difference between the i210 and the i219 Chipsets?

Regards: Elliott.

Hello,

I am currently writing a driver for the i219 and tried to access the received data, but I am missing the Receive Descriptor Base Address (RDBAL/RDBAH)?

I couldn't find this information in the datasheet (http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/ethernet-connection-i219-datasheet.pdf).

Was also looking at the datasheet of the PCH (http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/100-series-chipset-datasheet-vol-2.pdf).

The datasheet of the i217 (http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/i217-ethernet-controller-datasheet.pdf ) contains the RDBAL/RDBAH but I am not entirely convinced that these addresses are also correct for the i219.

I really appreciate any help you can provide,

Akir

I was installing the latest drivers for my motherboard, I211 + I219-V on a fresh W10 x64, the 21.1 package.

I219-V work fine

But the new Drivers for I211 (at least, maybe others too) inside ProSet 21.1 are signed ¿Wrong? by INTELNPG1, and Windows refuse them with the classical Error 52.

ProSet 21.0, in other hands, work fine, the sign are correct. issued not by INTELNPG1, but Intel(R) Intel Network Drivers.

Not a drama, but it would be nice to install a properly signed driver to use it.

More strange, Drivers for I219-V are signed by INTELNPG1 too, and work fine (same cert)