Can you report on progress with SR-IOV discoverability across the existing IaaS Stacks beyond VMware / ESXi?

We are working with OpenStack and CloudStack setups, and try to assure VMs can get set up that predictably deliver a high I/O load ya means of using the respective orchestration functions, but we seem to see that pattern repeat that I/O and networking is somewhat underrepresented in the FOSS IaaS Stacks.

It seems that support of SR-IOV is currently restricted to VMware only, and even there they say you need the most recent ESXi v5.1 [1] before you can hope to do anything with it, plus you loose ability to migrate the virtual machine using their vMotion – where there ais material at Microsoft that suggests their HyperV can handle by a short period of switching from SR-IOV to fully virtualised I/O (before migration) and back (after migration) [2].

Now I am of course wondering if and when all Linux distributions (especially other than RedHat) can offers a verified SR-IOV support, and KVM will be offering full support for SR-IOV including live migration across as many Linux distributions as possible…

Overall, it seems that creating a rather detailed inventory of the available resources, INCLUDING I/O is functionality that is preconditions to discover the capabilities of the underlying hardware that an IaaS management stack has to do to make proper placement decisions for creating VMs - and functions to find and offer discovered I/O resources in an abstracted way to a party requesting a VM (through UI or API) is simply not part of the concept (yet).

Of course if I am just mistaken and all that already exists, I'd be very happy if you could point me to folks at Intel and/or (or at the large Intel NIC-I/O chip customers) who are currently working in the OpenStack Community on making discovery, differentiation and abstraction of underlying I/O properties a regular feature of IaaS, KVM and the Ubuntu LTS Linux distribution.

One should also think HP as a prime partner of Intel in NICs, servers and now as well with an OpenStack based Cloud DC offering of their own should have a vested interest on bringing this forward…. well, maybe we just need pointers to the right folks at HP.

So, if there are any interesting signals on anyone’s radar on this, please share !

Thank you !

Sources:

[1] http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2038739

[2] http://msdn.microsoft.com/en-us/library/windows/hardware/hh440249%28v=vs.85%29.aspx

I have been looking across many sources, to find a card that can do all of the following

• Have more than 2 x 10GbE in I/O capacity - interestingly there now are several [1]
• Use a chipset that is known for SR-IOV support (e.g. Intel 82599)
• Fit into a low profile card slot on a high density HP SL230s servers [2]

Now, while It seem that just recently, the vendor community indeed came up with one first card that can match that list, which seemingly is Niagara 32714L from Interface Masters [3].

Even if maybe not in this particular HP server: Did anyone here or at Intel ever see this (rather young) card actually running

* under Linux

* using SR-IOV

anywhere at all yet?

Of course additional information on running it in HP SL230s servers would be extremely useful (I would not ask here if had gotten a useful answer already elsewherey...)

[1] 10GbE - 40GbE - NICs offers a quite impressive overview on 10GbE and 40 GbE cards in all forms and fashions

[2] HP ProLiant SL230s Gen8 Server overview - HP Small & Medium Business products

[3] Niagara 32714L - Quad Port Fiber 10 Gigabit Ethernet NIC Low Profile PCI-e Server Adapter Card

I have a software application that runs on a laptop running Windows 7 SP1 which receives data at around 100Mbps via a UDP stream over a 1GbE connection.  I've run the software on multiple laptops successfully in the past (older network adapters - e.g. 82577LM) .  Recently I installed the software on a newer model laptop which has a 82579LM network adapter.  When running the software on the laptop with the 82579LM adapter.  With the 82579LM adapter I'm seeing approximately one lost packet every 25K-60K packets.

1.  I'm running the version 16.7 (latest) of the Intel Network Drivers

2.  Windows 7 - SP1 + latest updates

3.  I've observed the same behavior on multiple laptop models by different vendors which contain the 82579LM adapter.

Searching the Internet I've seen some postings of issues under Linux complaining about similar 82579LM adapter issues:

http://www.mail-archive.com/e1000-devel@lists.sourceforge.net/msg04765.html

And some more here:

https://bugs.launchpad.net/ubuntu/natty/+source/linux/+bug/870127

Since this is running under Windows 7 SP1 we obviously have different drivers but I'm wondering if the issue is related.  Any ideas for things I could try to fix the issue?

Thanks,

Ryan

When I install an Intel Gigabit ET Quad Port Server Adapter in an HP DC7900 SFF business desktop computer, the machine hangs at Power On with no beep code or error message. I do get video, the memory check, and a message about initialising PXE boot on the internal NIC (when enabled in BIOS). That is the only indicator I have about the progress of the BIOS routine before it hangs.

I have tried every combination of visible BIOS setting on the HP. I am on the latest BIOS, and it is stated to be impossible to downgrade the BIOS, so I cannot try another BIOS for the HP.

The Intel ET Quad works in another machine, and using that machine I have configured the ET from a DOS environment in a number of different ways, e.g. I have both enabled and disabled I/O Map Mode using the IOUTIL utility; and I have both enabled and disabled the option ROMs using the command BOOTUTIL -ENABLE=DISABLED.

What else can I do, other than replace the HP machine with another computer?

1. I have not flashed the NIC with the latest Intel software, because the documentation indicates that updates only deal with option ROM functions such as PXE, iSCSI, Fibre Channel, and also EFI (but my machine does not have UEFI). Could this make a difference?

2. I have also had a look at the Intel Datasheet for 82576EB Controller (Revision 2.63 dated December 2011) on which the ET Quad is based (it has two such controllers), and it seems to me there are registers in non-volatile memory that could be re-programmed using ethtool within a Linux environment to test aspects of the configuration, e.g. it is possible to switch off one of the two controllers on the card.

Section 4.3.4.1 Multi-Function Advertisement states:"If one of the LAN devices is disabled, the 82576 is no longer a multi-function device. The 82576 normally reports a 0x80 in the PCI Configuration Header field Header Type .... However, if a LAN is disabled, the 82576 reports a 0x00 in this field to signify single-function capability."

It seems to me that this could make a considerable difference to the ability of the HP to enumerate its PCI devices at Power On. This is just one example of the control registers available in non-volatile memory.

My difficulty is that it is non-trivial to program non-volatile memory using ethtool, and for example I know there are protective measures such that one needs to specify a magic number in order for the 82576 controllers to accept any writes to its internal registers, and there is endian-ness to deal with when updating multi-byte registers and so forth. All this is a bit intimidating, but the difficulties do not seem insuperable. Does anyone know of any good guides to doing this, or am I condemned to work only from datasheets?

Does anyone who understands PCI device enumeration know of any configuration registers that could be configured differently from the defaults in such a way as to give the HP BIOS another chance to bring up the card? Obviously I would prefer a solution that does not require one of the two 82576 controllers to be disabled, because my 4-port card would then be a 2-port card.

I have an Intel 82566DM-2 Gigabit NIC in a HP desktop running Windows 7 Pro 32-bit.

How do I configure a LAN configuration to have a specific VLAN id?  Is there any utility available/needed?

Thanks.

This is an older windows server 2003 box, but it's still a fine and dandy file server.  Consists of a SuperMicro dual xeon board, a ton of ram and a 3ware 9550SX and is stuffed full of drives - a couple mirrors and 10TB in a raid.

It also handles domain, dns, dhcp

My adventure started off trying to update the network drivers on it. It has a number of Intel Pro/1000 MT cards in it.

The new drivers from Intel will not 'upgrade', the previous version must be uninstalled first.

And there in lies the rub.  These drivers refuse to uninstall giving a '1713.Intel Pro Network Connections...' error.

Drivers are listed as

13.5.32.0 and 10.3.32.2

After spending the day on it yesterday I have managed to get it unbootable (a failed winserv 2008 upgrade)

So'kay, it's sister machine had been retired last year when I moved mail to the cloud so I could just steal the boot disk and try that.

Got it booted and it's network cards are funky too.  They also are refusing to uninstall with the same error.  And even though I configure them correctly it's got no connectivity.  Weird.

Anyway, sorry for the long explanation, can anyone help me get these darn old drivers off this system?

Thanks in advance.

Intel(R) 82576 Gigabit Dual Port Network Connection

Intel(R) Gigabit ET Dual Port

have Option rom can not be invoke ID:0x8086h

how can i fix it?

Hello,

Short story - cannot receive ipv6 packets in a KVM guest using SR-IOV interfaces (VF), but, ipv4 works fine.

Long Story:

Have 2 KVM VMs set up on 2 separate hosts. OS in the host and the guest is RHEL6.4. The hosts use the 82599 NICs.  Have assigned a VFs to each guest (eh4/eth5) using unique mac addresses in the XML guest definition (the other interfaces in the VM are bridged interfaces).  Assigned a unique VLAN to each VF per VM (eth4 is 610, eth5 is 611) using 'ip link set' commands.  Using Intel provided driver ixgbe (3.15.1) on the host and ixgbevf (2.8.7) in the guest. Plumbed ipv4 and ipv6 IP in the guests for eth4 on each VM.  Ping (ipv4) works fine.  We can see the packet enter the NIC  on the receive side host (tcpdump) and can see it in the guest too.  When we repeat the process for ipv6, it fails.  It leaves the guest fine, we see it hit the NIC on the received host), but it is NOT received by the guest across the VF.  If we pull out the VFs and replace with bridges, ipvv6 works fine so it's not a routing/network issue. 

Is there something we need to set up/configure to get ipv6 to show up in the guest??  Note we can also ping out successfully to the upstream L3 switch (subnet gateway), but not to the other VM.

Thanks,

Shawn

I'm having an issue making the latest ixgbe driver (3.15.1) with NAPI enabled. No matter how I try to compile it, it won't show -napi at the end of the version. Is there a parameter I could check whether my kernal has NAPI enabled?gbe

[root@linux ~]# modinfo ixgbe

filename:       /lib/modules/3.9.4-200.fc18.x86_64/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko

version:        3.15.1

license:        GPL

description:    Intel(R) 10 Gigabit PCI Express Network Driver

author:         Intel Corporation, <linux.nics@intel.com>

srcversion:     9355E6A8DE2F272233819DA

alias:          pci:v00008086d0000155Dsv*sd*bc*sc*i*

alias:          pci:v00008086d0000155Csv*sd*bc*sc*i*

alias:          pci:v00008086d00001557sv*sd*bc*sc*i*

alias:          pci:v00008086d0000154Fsv*sd*bc*sc*i*

alias:          pci:v00008086d0000154Dsv*sd*bc*sc*i*

alias:          pci:v00008086d00001528sv*sd*bc*sc*i*

alias:          pci:v00008086d000010F8sv*sd*bc*sc*i*

alias:          pci:v00008086d0000151Csv*sd*bc*sc*i*

alias:          pci:v00008086d00001529sv*sd*bc*sc*i*

alias:          pci:v00008086d0000152Asv*sd*bc*sc*i*

alias:          pci:v00008086d000010F9sv*sd*bc*sc*i*

alias:          pci:v00008086d00001514sv*sd*bc*sc*i*

alias:          pci:v00008086d00001507sv*sd*bc*sc*i*

alias:          pci:v00008086d000010FBsv*sd*bc*sc*i*

alias:          pci:v00008086d00001517sv*sd*bc*sc*i*

alias:          pci:v00008086d000010FCsv*sd*bc*sc*i*

alias:          pci:v00008086d000010F7sv*sd*bc*sc*i*

alias:          pci:v00008086d00001508sv*sd*bc*sc*i*

alias:          pci:v00008086d000010DBsv*sd*bc*sc*i*

alias:          pci:v00008086d000010F4sv*sd*bc*sc*i*

alias:          pci:v00008086d000010E1sv*sd*bc*sc*i*

alias:          pci:v00008086d000010F1sv*sd*bc*sc*i*

alias:          pci:v00008086d000010ECsv*sd*bc*sc*i*

alias:          pci:v00008086d000010DDsv*sd*bc*sc*i*

alias:          pci:v00008086d0000150Bsv*sd*bc*sc*i*

alias:          pci:v00008086d000010C8sv*sd*bc*sc*i*

alias:          pci:v00008086d000010C7sv*sd*bc*sc*i*

alias:          pci:v00008086d000010C6sv*sd*bc*sc*i*

alias:          pci:v00008086d000010B6sv*sd*bc*sc*i*

depends:        dca

vermagic:       3.9.4-200.fc18.x86_64 SMP mod_unload

parm:           InterruptType:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default IntMode (deprecated) (array of int)

parm:           IntMode:Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default 2 (array of int)

parm:           MQ:Disable or enable Multiple Queues, default 1 (array of int)

parm:           DCA:Disable or enable Direct Cache Access, 0=disabled, 1=descriptor only, 2=descriptor and data (array of int)

parm:           RSS:Number of Receive-Side Scaling Descriptor Queues, default 0=number of cpus (array of int)

parm:           VMDQ:Number of Virtual Machine Device Queues: 0/1 = disable, 2-16 enable (default=8) (array of int)

parm:           max_vfs:Number of Virtual Functions: 0 = disable (default), 1-63 = enable this many VFs (array of int)

parm:           L2LBen:L2 Loopback Enable: 0 = disable, 1 = enable (default) (array of int)

parm:           InterruptThrottleRate:Maximum interrupts per second, per vector, (0,1,956-488281), default 1 (array of int)

parm:           LLIPort:Low Latency Interrupt TCP Port (0-65535) (array of int)

parm:           LLIPush:Low Latency Interrupt on TCP Push flag (0,1) (array of int)

parm:           LLISize:Low Latency Interrupt on Packet Size (0-1500) (array of int)

parm:           LLIEType:Low Latency Interrupt Ethernet Protocol Type (array of int)

parm:           LLIVLANP:Low Latency Interrupt on VLAN priority threshold (array of int)

parm:           FdirPballoc:Flow Director packet buffer allocation level:

            1 = 8k hash filters or 2k perfect filters

            2 = 16k hash filters or 4k perfect filters

            3 = 32k hash filters or 8k perfect filters (array of int)

parm:           AtrSampleRate:Software ATR Tx packet sample rate (array of int)

parm:           FCoE:Disable or enable FCoE Offload, default 1 (array of int)

parm:           LRO:Large Receive Offload (0,1), default 1 = on (array of int)

parm:           allow_unsupported_sfp:Allow unsupported and untested SFP+ modules on 82599 based adapters, default 0 = Disable (array of int)

dmesg:

[ 1022.867423] Intel(R) 10 Gigabit PCI Express Network Driver - version 3.15.1

[ 1022.867424] Copyright (c) 1999-2013 Intel Corporation.

[ 1022.867865] ixgbe: 0000:1f:00.0: ixgbe_check_options: FCoE Offload feature enabled

[ 1023.030542] ixgbe 0000:1f:00.0: irq 68 for MSI/MSI-X

[ 1023.030551] ixgbe 0000:1f:00.0: irq 69 for MSI/MSI-X

[ 1023.030558] ixgbe 0000:1f:00.0: irq 70 for MSI/MSI-X

[ 1023.030566] ixgbe 0000:1f:00.0: irq 71 for MSI/MSI-X

[ 1023.030574] ixgbe 0000:1f:00.0: irq 72 for MSI/MSI-X

[ 1023.030582] ixgbe 0000:1f:00.0: irq 73 for MSI/MSI-X

[ 1023.030589] ixgbe 0000:1f:00.0: irq 74 for MSI/MSI-X

[ 1023.030597] ixgbe 0000:1f:00.0: irq 75 for MSI/MSI-X

[ 1023.030604] ixgbe 0000:1f:00.0: irq 76 for MSI/MSI-X

[ 1023.030612] ixgbe 0000:1f:00.0: irq 77 for MSI/MSI-X

[ 1023.030619] ixgbe 0000:1f:00.0: irq 78 for MSI/MSI-X

[ 1023.030627] ixgbe 0000:1f:00.0: irq 79 for MSI/MSI-X

[ 1023.030635] ixgbe 0000:1f:00.0: irq 80 for MSI/MSI-X

[ 1023.030643] ixgbe 0000:1f:00.0: irq 81 for MSI/MSI-X

[ 1023.030651] ixgbe 0000:1f:00.0: irq 82 for MSI/MSI-X

[ 1023.030658] ixgbe 0000:1f:00.0: irq 83 for MSI/MSI-X

[ 1023.030666] ixgbe 0000:1f:00.0: irq 84 for MSI/MSI-X

[ 1023.032512] ixgbe 0000:1f:00.0: (PCI Express:5.0GT/s:Width x8) 90:e2:ba:18:c4:94

[ 1023.032845] ixgbe 0000:1f:00.0 eth4: MAC: 2, PHY: 12, SFP+: 5, PBA No: G43015-001

[ 1023.032851] ixgbe 0000:1f:00.0 eth4: Enabled Features: RxQ: 16 TxQ: 16 FdirHash RSC

[ 1023.032883] ixgbe 0000:1f:00.0 eth4: Intel(R) 10 Gigabit Network Connection

[ 1023.033225] ixgbe: 0000:1f:00.1: ixgbe_check_options: FCoE Offload feature enabled

[ 1023.058493] systemd-udevd[1839]: renamed network interface eth4 to p4p1

[ 1023.236420] IPv6: ADDRCONF(NETDEV_UP): p4p1: link is not ready

[ 1023.301750] ixgbe 0000:1f:00.0 p4p1: detected SFP+: 5

[ 1023.436512] ixgbe 0000:1f:00.0 p4p1: NIC Link is Up 10 Gbps, Flow Control: RX/TX

[ 1023.436635] IPv6: ADDRCONF(NETDEV_CHANGE): p4p1: link becomes ready

[ 1024.146214] ixgbe 0000:1f:00.1: irq 85 for MSI/MSI-X

[ 1024.146226] ixgbe 0000:1f:00.1: irq 86 for MSI/MSI-X

[ 1024.146234] ixgbe 0000:1f:00.1: irq 87 for MSI/MSI-X

[ 1024.146242] ixgbe 0000:1f:00.1: irq 88 for MSI/MSI-X

[ 1024.146249] ixgbe 0000:1f:00.1: irq 89 for MSI/MSI-X

[ 1024.146257] ixgbe 0000:1f:00.1: irq 90 for MSI/MSI-X

[ 1024.146265] ixgbe 0000:1f:00.1: irq 91 for MSI/MSI-X

[ 1024.146272] ixgbe 0000:1f:00.1: irq 92 for MSI/MSI-X

[ 1024.146280] ixgbe 0000:1f:00.1: irq 93 for MSI/MSI-X

[ 1024.146287] ixgbe 0000:1f:00.1: irq 94 for MSI/MSI-X

[ 1024.146295] ixgbe 0000:1f:00.1: irq 95 for MSI/MSI-X

[ 1024.146304] ixgbe 0000:1f:00.1: irq 96 for MSI/MSI-X

[ 1024.146311] ixgbe 0000:1f:00.1: irq 97 for MSI/MSI-X

[ 1024.146318] ixgbe 0000:1f:00.1: irq 98 for MSI/MSI-X

[ 1024.146326] ixgbe 0000:1f:00.1: irq 99 for MSI/MSI-X

[ 1024.146333] ixgbe 0000:1f:00.1: irq 100 for MSI/MSI-X

[ 1024.146341] ixgbe 0000:1f:00.1: irq 101 for MSI/MSI-X

[ 1024.148223] ixgbe 0000:1f:00.1: (PCI Express:5.0GT/s:Width x8) 90:e2:ba:18:c4:95

[ 1024.148555] ixgbe 0000:1f:00.1 eth4: MAC: 2, PHY: 1, PBA No: G43015-001

[ 1024.148561] ixgbe 0000:1f:00.1 eth4: Enabled Features: RxQ: 16 TxQ: 16 FdirHash RSC

[ 1024.148631] ixgbe 0000:1f:00.1 eth4: Intel(R) 10 Gigabit Network Connection

Hello,

I have been using my ASUS P8Z68 Deluxe/GEN3 mobo for some time with Intel's 16.7 drivers. I noticed that 16.8 drivers were released, installed them and problems began:

- upon each reboot NIC is randomly detected either as 82579V (properly) or as 82579LM (not properly)

- if NIC is detected as LM version then on next reboot Intel PXE BIOS appears on the screen during mobo initialization while corresponding option (Intel NIC BIOS) is NOT enabled in UEFI BIOS settings

- sometimes after reboot NIC cannot detect that link is up - I had to replug the Ethernet cable to detect connection

I reverted back to 16.7 drivers and everything is OK again.

Has anybody noticed similar behavior with similar setup ?

Best regards,

Zbyniu

Hello everyone

I have a Fujitsu Siemens workstation (Celsius m460) which has an Intel 82566DM-2 onboard network interface card. I am running Windows 7 Enterprise (x64).

The device manager shows me driver version of: 9.13.4.10. This seems to be drivers coming with the operating system. This driver gives me the following tabs: "General", "Advanced", "Driver", "Ressources", "Power Management" - but no VLAN tab.

So I went to Intel's download page and downloaded the latest driver (ProWinx64.exe) version for my NIC, which seems to be version 18.3 (Download-Center). According to the description it contains the "Advanced-Network-Services (ANS)" feature.

Installing this driver (and of course selecting ANS) results in having the following tabs: "General", "Driver", "Ressources", "Power Management". So suddendly also the "Advanced" tab disapears!!

NB: I have already checked that the "Windows Management Instrumentation" Service is running. And no, I am not connecting via RDP to that machine....

So what am I doing wrong here? Any help is greatly appreciated.

Thanks and regards

Matthias

Hello,

I am sorry if this question has been answered, or if this is being posted in the wrong place.

I have an ASUS z77 motherboard with an Intel 82579V Gigabit Network Connection. I am getting slow speeds when playing some online intensive games. After searching support forums, a solution that popped up was enabling ipv4 offloading in the network controller's advanced settings. I went and I changed the settings,  The connection was dropped, but it immediately reestablished itself. However, the ipv4 offload setting I had changed reverted back to disabled. I tested several other settings, each revert back whenever I click "OK" to close the advance settings dialog box.

I am running windows 8 and I am running driver version 12.6.45.0.

Thank you

Good day Gentlemen,

I'm trying to upgrade my Windows 7 Home Premium to Windows 8 but Intel(R) Network Connections 17.3.63.0 is not compatible. I googled this issue and I found that if I uninstall Intel(R) Network Connections 17.3.63.0 and do the upgrade, I will lose my connection to the Internet. I'm not sure about this information and I can't risk my connection. So, what do I have to do with Intel(R) Network Connections 17.3.63.0 so I can upgrade to Windows 8 ?

Hi,

I got a Gigabyte GA-Z77X-UD5H motherboard with a Intel 82579V network adaptater, and running Windows 7 64 bits.

My issue is whenever I change some adaptater options (through the device manager), they always disable themselves when I go back to the settings, like the Large Send Offload and Checksum Offload. They are quite critical ones, it's like disabling hardware capability of the device.

Is there a way to force it enabled ?

Thanks.

I've spent some time searching for an solution to my problem but I can't find it on my own so hopefully someone will have some advice.

Essentially, I've been trying to configure my PC so that I can keep it in Hibernation mode when I'm not using it.  The reason I want to keep it in Hibernation mode and not just power it off is that my PC is also my server so I need it to power up when I'm streaming my shows to the TV or access files on my laptop.

The problem is that when it goes into hibernation mode (either manually or automatically) the PC keeps waking itself up when I'm not around or doing anything (i.e. nothing else on the network 'should' be trying to access the PC).

I've run 'powercfg' and it is saying it's the Network card that it waking it up but I'm getting no more info than that.

Here's the system info:

OS: Windows 8 Enterprise

Motherboard: Asus P8Z77-V Pro

NIC: Intel 82579V Gigabit Network Card (w latest driver version 12.2.45.0 installed)

Router: dLink DIR-825

What I've done so far:

• According to Microsoft, Windows 8 has changed their power profiles so that Wake-On-Lan can only work in either Sleep or Hibernation mode (not power off) so it is set to go to Sleep after 30 minutes and Hibernate after 60 minutes (http://support.microsoft.com/kb/2776718).
• Made sure nothing else would wake up the computer like small movements from the mouse.  So, the power management settings for my Logitech keyboard and mouse have been changed to not wake the PC.  Powercfg now lists only the NIC as being able to wake the PC.
• There doesn't seem to be any settings in the BIOS for the motherboard that would affect the computer waking up.  The 'APM' (Advanced Power Management) settings are all pretty much disabled for Wake form PCI/Wake from PCIE.
• I've cleaned up the scheduled tasks in Windows 8 to disable anything that may be waking it up.
• There seems to be nothing in my router that I can set for Wake-On-Lan.
• Windows 8 File Backup is turned on.
• Windows 8 Event viewer is only stating that the wake source is the LAN.  Example:
  • The system has returned from a low power state.
    Sleep Time: 2012-11-18T19:32:27.037670400Z
    Wake Time: 2012-11-18T19:35:43.846373900Z
    Wake Source: Device -Intel(R) 82579V Gigabit Network Connection

So, I've been trying to figure out what is waking it up.  The other devices on my network are:

• Epson 835 printer (I can't see that needing the PC and it's turned off)
• HTPC running XBMC (The PC is still turning on when this is kept off but it does wake up the PC when I turn it on).
• Denon network receiver (Technically, my PC is set to stream audio to the Denon but I don't know how to check to see if that is the cause)
• A couple of PlayBooks but neither of them are running anything to grab files from the PC.

I'm really at my wits end since I'm trying to find a power friendly way to keep my computer ready without having to keep it on full time.  I'm trying to narrow down the source so I plan on posting here, the Asus forums and Windows forums.

Thanks in advance for any support you may have.

Cheers.

I am trying to connect one PC and one embedded device directly with a crossover cable and make a data transmission between them. There is general connection info as below:

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

PC:

OS – Windows 7

Network Adapter – Intel 82579LM; driver version – 12.2.45.0

Send and receive packet using Winpcap library

Device:

No OS

Network Adapter – SMSC LAN91C111

Send and receive packet directly using Ethernet chip driver interface

Transmitted packet uses my own protocol on data link layer which is not related to any network Ethernet protocol such as arp, tcp/ip.

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

My problem is when setting device to auto-negotiation and PC to auto-negotiation or 100 full duplex and plugging crossover cable, I can see twoLED indicators on both side blinking together at the same time about once a second. It does make sense because one of LEDs should be solid green for Ethernet link established. After that, PC becomes slow and “display driver stopped responding” message shows up.

But I do the same thing to connect the PC in Windows XP and device, everything is fine. PC can detect stably of the network link with device and data transmissions are stable with the following network setting: PC – 100 full duplex; device – auto-negotiation.

And I also make an experiment in Ubuntu. It turns out that under the same situation, PC still can detect the link from device. If I use straight cable with switch to connect them (all OSs), there is no problem at all.

I just can’t seem to figure it out. Anyone have any suggestions? Thanks in advance.

I have multiple Lenovo T500 laptops that are getting horrible data transfer rates while on Win7 x64. These work fine when running WinXP.  I have tried the latest drivers on both the Intel and Lenovo support sites.  Also tried a couple previous versions with no luck.  Has anyone seen this issue or have a work around to resolve?

Can someone post a how to for the INFs on the 82579V for windows 2003 server 32bit.

Thank you

Stephen

Just upgraded from Windows 7 to the Windows 8 Preview. I was using the Intel 82579LM Drivers with ANS so I could use the VLAN teaming features. These driver to do not work in Windows 8 and I don't see any preview drivers for it. Any idea when these will be out.

Hi! I would like to know what are the difference between

E10G42BTDA and E10G42BFSR

the first one has a cable type:

SFP+ direct attached

twin axial cabling up to 10 m

and the second one:

MMF 62.5/50 μm

up to 300 m

I need to use the E10GSFPSR. Wich one of the previously mentioned network adapter is compatible with this sfp+ module?

And what about your E10G41BFSR?

Thank you.

Regards,

Kaiyu