I am looking to deploy a wake on lan solution to one of the sites that I manage.  I have found a VBscript that takes care of most adapters, but not Intel 82579lm adapters.

I followed some very helpful information from this thread: https://communities.intel.com/thread/19132 and changed the commands to reflect wake on magic packet.  Unfortunately I keep getting a failure message.  The thread that I was using for reference was for a different model Intel NIC, but I hopped that it would work.

Does anyone have any guidance in enabling wake on magic packet via command line and prosetcl.exe for Intel 82579lm adapters?

Any help would be much appreciated.

Hi Guys,

I am trying to deploy 20+ Compaq 6200 PRO's via Windows Deployment Services. Other desktops work just fine 6000 8000... but not this 6200.

When booting in PXE, the Wim file gets loaded and the WDS screen asks me to select deploy or image. When I select Deploy an error displays:

A connection to the deploymentshare could not be made. The following networking device did not have a driver installed:

PCI\VEN_8086&DEV_1502&SUBSYS_1497103C&REV_04

Meaning It cannot find a driver for the network card. I believe its the "Intel 82579LM Gigabit networ Connection".

I tried every driver pack for it and injected the drivers in to the WIM file to no avail.

I do find a lot of driver packs where the e1c62x64.inf file stated the PCI\VEN_8086&DEV_1502&SUBSYS_1497103C but not with the &REV_04 at the end.

Intel drivers do not even match that far, they get stuck at PCI\VEN_8086&DEV_1502 before being different

Softpaq SP54803.exe does have the best match (PCI\VEN_8086&DEV_1502&SUBSYS_1497103C)

Here's the first bit;

[Intel.NTamd64.6.1.1]
; DisplayName Section DeviceID
; ----------- ------- --------
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503
; HP
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1494103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1495103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1496103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1497103C

%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1632103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_3395103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1787103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1788103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1789103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_178A103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_178C103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_178D103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1790103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1791103C

[Intel.NTamd64.6.1]
; DisplayName Section DeviceID
; ----------- ------- --------
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502
; HP
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1494103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1495103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1496103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1497103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1632103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_3395103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1787103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1788103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1789103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_178A103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_178C103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_178D103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1790103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1791103C

_____________________________________________________________________________________

SO I tried something I never done before and made an extra entry for the &REV_04 like this:

[Intel.NTamd64.6.1.1]
; DisplayName Section DeviceID
; ----------- ------- --------
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503
; HP
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1494103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1495103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1496103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1497103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1497103C&REV_04
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1632103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_3395103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1787103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1788103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1789103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_178A103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_178C103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_178D103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1790103C
%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_1791103C

[Intel.NTamd64.6.1]
; DisplayName Section DeviceID
; ----------- ------- --------
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502
; HP
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1494103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1495103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1496103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1497103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1497103C&REV_04
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1632103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_3395103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1787103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1788103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1789103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_178A103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_178C103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_178D103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1790103C
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_1791103C

But you have guessed, that did not work either.

Does anyone know why this error is thrown? Am I looking in the wrong place? Is the REV_04 bit really the culprit?

Any thought appreciated.

Regards,

Jurgen

Dear.

I have recently bought the new sandy bridge core i5 machine and been trying to install Win SBS 2008, but during the process, it asked me for the driver for the ethernet adaptor. I cannot find any whatever online or the driver CD. Can anyone help me to locate a Intel(R) 82579V Gigabit Network driver for Win SBS 2008 please?

Thanks a lot

Larry

Hello

I have a Lenovo W520 with 82579LM installed with the latest driver (IntelPro 19, driver version 12.10.28.0).

I am trying to connect it with a 10gBaseT copper port on a router and it won't come up.

The link is flapping constantly and changing between enabled/uplugged.

I realize this is a 1gig NIC but should it auto-negotiate and come up with 1gig (it is set to autoneg on both sides) ?. It has no issue connected to a 1gig copper port.

However I have used other Intel 1gig NICs (82578DM and 82576LM) and they don't have any issue connecting to this 10gig copper port.

Is there anything that I can dump to check out why ?

Note: the i350 1gic seems to have the same behavior but it's intermittent..

Thanks in advance,

KJ

Hi,

I recently updated a 2012 HyperVisor Server from GB iSCSI NIC to a X540-T2 NIC for use with iSCSI.

The System has onboard I350 Nics which I use for the LAN.

Initially I just allowed windows to install best driver (And I presume use the already installed v18 Proset)  Things were fine for around 18 hours.

Then I got an event log from IXBGT event ID 56 stating that "Intel(R) Ethernet Converged Network Adapter X540-T2 The network driver has been stopped because the network adapter has been removed." - This brought down all the VM's and although device manager was seeing the NIC's and the NIC's had lights on, they were marked as disabled and could not be re enabled.

After a restart all was fine and then it happened again, around 18 hours later.

I updated the BIOS on the server and attempted to install the latest V19 driver package (changing virtual switch to internal beforehand)

Although the install stated it went ok, immediately it was noticed that performance was poor, and now I cannot see any advanced options within the NIC's - the pane states: "Your Device / OS combination does not support any VLAN advanced settings."  (It's not on any VLANs)

The driver on the NIC now shows 05/12/2013 version 3.8.35.0

I will have another out of hours maintenance window soon, what's going on and what should I do ?

Thanks for you advice!

zach

I have run  “ modprobe –r ixgbe && modprobe ixgbe allow_unsupported_sfp=1” to enable allow_unsupported_sfp after upgrading the ixgbe driver to v3.17.3. Unfortunately,  I still got “failed to load because an unsupported SFP+ module type was detected” issue. Do we need to reboot the server to apply modprobe?

Hi,

I have a gateway which runs on Windows Embedded Standard 7 which has Intel NIC Card 1000 MT/PRO .

I have connected this gateway and a switch in a network where switch has configured speed/duplex as 1000Mbps/Full.

When I set the Speed/Duplex on my gateway's NIC to Auto-Negotiate or 1000Mbps/Full, it negotiating/advertising the speed and duplex properly.

But when Speed/Duplex sets to 100Mbps/Full on gateway's NIC, in the Switch it shows that my gateway is advertising the Speed/Duplex as 100Mbps/Half Duplex.

I am checking these configured values through the registry entryComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00NN\*SpeedDuplex. It shows the configured value.

The doubt have here is that i have checked the enum values for this *SpeedDuplex entry, it shows in the following way:

0 - Autonegotiation

1- 10Mbps HalfDuplex

2 - 10Mbps FullDuplex

3 - 100Mbps HalfDuplex

4 - 100Mbps FullDuplex

6 - 1000Mbps

Why don't have here the value 5?

I have checked this registry in other Windows Operating systems, it shows correctly. Only in this Windows Embedded Standard 7 OS it shows this way. Will it create any issue? While performing the Speed/Duplex advertisement/Negotiation will it use these enum values? If so how can I resolve this issue?.

Thanks,

Challask

There's a discussion on Dell's forums about the i217-LM causing a flood of IPv6 multicast traffic during sleep state. Is Intel aware of this issue? Is it a driver issue which has been addressed?

Opti 9020s with Intel I217-LM nics causing network issues - Desktop General Hardware Forum - Desktop - Dell Community

I recently updated to Windows 8.1 and the original Windows 8 drivers for my Gigabit CT NIC have been replaced with the default Windows 8.1 drivers which are terrible and have done nothing but annoy me (stuttering audio in streams, high CPU usage in downloading etc). I notice updates for Windows 8 are still regularly provided but there's absolutely nothing for Windows 8.1. Is possible to reinstall the Windows 8 drivers by such methods as making changes to the .inf file of the accompanying driver?

Thanks in advance!

Hallo Leute,

ich verstehe die Treiberpolitik nicht.

In meinem Rechner werkeln zwei Intel Pro/1000 Dual PT PCIe Karte. Treiber für Win 8 wurden zur Verfügung gestellt. Das war auch der Grund, dass ich mich für die Karten entschieden habe.

Beim kleinen Update auf 8.1 wird die Karte plötzlich nicht mehr supportet....

Einen Versionssprung von 7.x auf 8.x oder von 8.x auf 9.x kann ich verstehen, aber innerhalb von Win 8.x ist schon bitter. Die Karten kann ich derzeit nur gegen unterstützte Karten austauschen. Bei einem Markenanbieter und Marktführer wie Intel habe ich das einfach nicht erwartet und bin enttäuscht.

Gibt es eventuell die Möglichkeit einer Petition für die Treiberunterstützung ? Bei meinen HP Micro Servern wurde auch ein Biosupdate für Win8.1 nachgeschoben. Wieso kann das HP und Intel nicht ?

Gruß Michael

Hi all,

Bought a AsRock motherboard (ASRock B85M Pro4) with Intel Ethernet, downloaded the driver from AsRock website then downloaded another one from Intel Website, still cannot install the driver on my Windows Server 2008 R2 (x64). What I'm doing wrong or what driver should I install?

Need to solve this issue asap.

Thank you.

I am imaging using SCCM 2012 R2.  It installs the driver correctly but I would like to remove the check from "Allow the computer to turn off this device to save power".  What is the best way to do this?  Can I run a command line or a script to change that setting?

I need to change it for both Windows 7 and Windows 8.1 in case I have to do it differently.

Any help would be much appreciated.

Thanks

Rick

Hi,

I got this logged in my kern.log:

warning kernel: swapper: page allocation failure. order:0, mode:0x20
...
warning kernel: Call Trace:
warning kernel: [<ffffffff810f9bdc>] ? fallback_alloc+0x16e/0x20b
warning kernel: <IRQ>  [<ffffffff810f9d2a>] ? ____cache_alloc_node+0xb1/0xf8
warning kernel: [<ffffffff810ca6c8>] ? __alloc_pages_nodemask+0x6f4/0x780
warning kernel: [<ffffffff810f9716>] ? kmem_cache_alloc_node+0xdd/0x178
warning kernel: [<ffffffff812ad4c3>] ? __alloc_skb+0x59/0x159
warning kernel: [<ffffffff810f94d8>] ? kmem_getpages+0x52/0x11a
warning kernel: [<ffffffff810f9bdc>] ? fallback_alloc+0x16e/0x20b
warning kernel: [<ffffffffa022677a>] ? ixgbevf_alloc_rx_buffers+0x5e/0x18e [ixgbevf]
warning kernel: [<ffffffff810f9d2a>] ? ____cache_alloc_node+0xb1/0xf8
warning kernel: [<ffffffffa0228dda>] ? ixgbevf_poll+0x4e8/0x601 [ixgbevf]
warning kernel: [<ffffffff810f9716>] ? kmem_cache_alloc_node+0xdd/0x178
warning kernel: [<ffffffff812b7dd7>] ? net_rx_action+0xd1/0x29a
warning kernel: [<ffffffff812ad4c3>] ? __alloc_skb+0x59/0x159
warning kernel: [<ffffffff8105d694>] ? lock_timer_base+0x26/0x4c
warning kernel: [<ffffffff8105686c>] ? __do_softirq+0xd9/0x1a6
warning kernel: [<ffffffffa022677a>] ? ixgbevf_alloc_rx_buffers+0x5e/0x18e [ixgbevf]
warning kernel: [<ffffffff8100ad6c>] ? call_softirq+0x1c/0x30
warning kernel: [<ffffffffa0228d7f>] ? ixgbevf_poll+0x48d/0x601 [ixgbevf]
warning kernel: [<ffffffff8100c635>] ? do_softirq+0x5f/0xbe
warning kernel: [<ffffffff812b7dd7>] ? net_rx_action+0xd1/0x29a
warning kernel: [<ffffffff8105686c>] ? __do_softirq+0xd9/0x1a6
warning kernel: [<ffffffff81056688>] ? irq_exit+0x36/0x78
warning kernel: [<ffffffff8100ad6c>] ? call_softirq+0x1c/0x30
warning kernel: [<ffffffff8100c635>] ? do_softirq+0x5f/0xbe
warning kernel: [<ffffffff81056688>] ? irq_exit+0x36/0x78
warning kernel: [<ffffffff8100bc83>] ? do_IRQ+0xa0/0xb6
warning kernel: [<ffffffff8100bc83>] ? do_IRQ+0xa0/0xb6
warning kernel: [<ffffffff8100a593>] ? ret_from_intr+0x0/0x11
...

After a while, the system crashed for out-of-memory (kernel panics). It only happened on some servers (low end Intel Xeon) but not on the others. So I got 3 questions for you guys:

- Is this exactly the VF known issue mentioned in the subject?

- If yes, what will trigger it?

- Why the memory was used up when this happened?

Windows 7 64-bit, Intel Gigabit CT with ProSet 19.1. When VLAN is added to this card "Intel ANS Virtual Adapter" is added to system, but then error is displayed "One or more vlan(s) could not be created. Please check the adapters status and try again".

At the same time an appcrash is logged to eventlog:

----

Faulting application name: NCS2Prov.exe, version: 18.8.134.0, time stamp: 0x5285684c

Faulting module name: NcsColib.dll, version: 18.8.134.0, time stamp: 0x5285679b

Exception code: 0xc0000005

Fault offset: 0x00000000000332bb

Faulting process id: 0x12ac

Faulting application start time: 0x01cf598ed0546b43

Faulting application path: C:\Program Files\Intel\NCS2\WMIProv\NCS2Prov.exe

Faulting module path: C:\Windows\system32\NcsColib.dll

Report Id: 15bd7eae-c582-11e3-bb42-005056c00008

----

I tried adding vlan with prosetcl but that fails also.

Those "ghost" virtual adapters can not be uninstalled from Network Connections or from Device Manager. Only way to remove them is manually from registry... more info here Network Connectivity &mdash; Unable to uninstall Intel� Network Connections, Intel� PROSet, or teams

I removed drivers and reinstalled them, same thing.

I tried the card in another machine, with same ProSet 19.1 and I had no problems creating VLANs.

All drivers should be the latest. I believe that is an access violation exception, but what was going on... verbose logs anywhere ?

I'm not sure if this is a problem with WinGate, my Intel ethernet devices the motherboard or Windows but I'll post it here anyway.

Every now and then (maybe twice a week) all LAN clients lose connectivity and the usual "limited connectivity" exclamation mark is displayed over the network icon in the notification area. The server can still connect to internet, and everything seems peachy with ipconfig.

If I reboot the Wingate server, everything is fine again. The wonky thing is if I try to disable and re-enable the local network adapter, it won't turn grey. If I try again a few times, it does turn grey, but then won't turn on again. If I now try to reboot the Wingate server it will be stuck at "Restarting ..." and I need to hit the reset button.

Specs and images:

WinGate 8.1.0 Build 4655

Pretty standard but with Proxy server removed, no firewall, no bandwidth control.

Services installed: DHCP, DNS, Remote control, SMTP delivery and schedulers

Performance counters installed but disabled/stopped.

DHCP mode: Fully automatic

ips 192.168.3.2 to 192.168.3.5 reserved for various lan clients

Windows 8.1 update 1 x64 Pro

DirectX 11.0

Intel Core i5-4570S

Asus H87I-Plus BIOS 0905

8GB RAM

Logitech HID-compliant G3/MX518 Optical Mouse

Intel Ethernet Connection I217-V (84.xxx.xxx.xxx) driver e1i63x64.sys 12.6.47.0

Intel Gigabit CT Desktop Adapter (192.168.3.1) driver e1q63x64.sys 12.7.27.0

Clients OS: Windows 8.1 update 1 x64 Pro

Forum thread at WinGate:

WinGate Forums &bull; View topic - LAN clients connection broken, ethernet device wonky

My DH87MC board with I217v Gigabit Ethernet Controller used a wire connection until I recently installed a Centrino-N 6205 desktop wireless adapter and started using wireless.

I just downloaded Intel Network Connections 19.1  to update the wired LAN . The update failed to run because "Cannot install drivers. No Intel adapters are present in this computer." I did not knowingly uninstall anything associated with the adapters.

Could the installation of the wireless connection caused this issue? I would appreciate any info on how to recover the adapters. Regards. Peter

I shall make the Intel ethernet adapter 82566DM mounted on the mainboard (FOXCONN LS-36) of a DELL desktop PC (Type DCSM) transmit test patterns for Ethernet (100BASE-TX) Conformance Tests.

In detail I shall make it permanently transmit

1th     a scrambled IDLE stream (4B/5B=11111) as a basic signal for Mask Test

          (ANSI X3.263-1995 (R2000) Annex J)

2nd     a scrambled HALT line state for Jitter Test

          (IEEE 803.2-2000, 25.4.5 & ANSI X3.263-1995 (R2000) 9.1.9)

3rd      a 01010101 NRZ bit sequence for Duty Cycle Distortion

          (ANSI X3.263-1995 (R2000) 9.1.8)

Who can help me or/and tell me how to manage that?

Hello,

I can't receive all packets ranging in size from 65 to 68 bytes at 10Gbps. I learned from my net card vendor Silicom that it maybe has to do with cache line. If so, why I can receive all packets of 64-byte, and why all the packets of 69-byte and above can be received?

If it is really a hardware problem, I also want to know how I can get a convincing reason. Maybe you can give me one, or teach me how I can find the critical point that affect the performance. Now I have known a bit how to use Linux tool perf, but I don't know how to use it to find the reason.

BTW, I need to clarify that the driver is customized by PF_RING-5.6.2. And I didn't match the result of netdriverinfo.sh with you provided product info, but the lspci reported its vender:device(8086:10fc).

NIC: Intel® 10 Gigabit XF SR Dual Port Server Adapter

Kernel: 3.5.0-23-generic

Distribution_Version: Ubuntu 12.04.2 LTS

Driver_Version: ixgbe-3.18.7

Thanks in advance.

'The problem that we are having with these 10Gb NICs is that they do not come online unless a 1Gb NIC in the same system comes online as well.  I'm seeing this behavior in Redhat 5.x, Redhat 6.x, and Windows Server 2012 on this new batch of NIcs that we purchased.  This does not happen on some older (1 year old) X520-DA2 NICs that we have, hence my request to downgrade the firmware.

The NICs in question are all being used in Dell Poweredge R610 servers, in PCIe x8 slots.  I've already tried switching PCI slots as well, to no avail.

I will try upgrading the driver in Redhat, but I don't think that's it because our existing 10Gb NICs (same exact model, just 1 year old) are using the same driver, same optics, etc. and they work great.  Besides, the issue persists across multiple operating systems so I'm inclined to

think it's definitely not a driver issue.

Again, it should be noted that the NICs work fine, once another NIC (in this case, an onboard 1Gb NIC) is activated.  We are seeing this across the different operating systems as well.

Please advise

Dear.

I have recently bought the new sandy bridge core i5 machine and been trying to install Win SBS 2008, but during the process, it asked me for the driver for the ethernet adaptor. I cannot find any whatever online or the driver CD. Can anyone help me to locate a Intel(R) 82579V Gigabit Network driver for Win SBS 2008 please?

Thanks a lot

Larry