Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Sorry - can't answer that first hand as I use chilly's driver for intel dq67ep boards with no nic other than the on board 82579LM. I use the single pcie slot for sas. It's a neat board because of its size and low power, but no ecc and 16gb max limits its application.2eleven -- Does 4.1 support both NICs (with or without Chilly's fix)? I run 4.1 in production and if it is more stable I'll stick with that for the time being.
~ # esxcli software vib install -v http://www.vm-help.com/forum/download/file.php?id=898
[VibFormatError]
Bad VIB archive header
filename = http://www.vm-help.com/forum/download/file.php?id=898
Please refer to the log file for more details.
Hello again.
Just for your information, the problem was hardware related.
Somehow the eprom of the nic got corrupted while the bios
update to version 2.x of the main board. I contacted the
supermicro support and they send me a super fast response
with the needed files to reflash the nics. both adapters are working
now!
Greets schleicher
Hopefully this isn't too bad of a necro, but since the information is still relevant, and might help someone else...I had no sucess with 5.1 either, although VMMV.
esxcli software acceptance set -level=CommunitySupported
esxcli software vib install -v http://files.v-front.de/net-e1001e-1.0.0.x86_64.vib
I'm still astonished how a year later, this NIC is still not officially supported. Is it just that uncommon? Or what?
I am using a SuperMicro X9SCM-F and I followed the steps below to get the 82579LM NIC to work:
1. Installed ESXi 5.0 U1 ISO.
2. Ran the following commands from SSH while in maintenance mode:
esxcli software acceptance set --level=CommunitySupported
esxcli software vib install -v http://files.v-front.de/net-e1001e-1.0.0.x86_64.vib
The 82579LM NIC showed up afterwards and everything was good. All of the sudden the 82574L NIC drops connectivity and won't restore until the box is rebooted.
I have both NICs setup in an etherchannel with a Cisco switch and have also noticed very poor performance connecting to the NAS.
This is the output from the ethtool:
/var/log # ethtool -i vmnic0
driver: e1000e
version: 1.3.10a-NAPI
firmware-version: 2.1-2
bus-info: 0000:02:00.0
/var/log # ethtool -i vmnic1
driver: e1000e
version: 1.3.10a-NAPI
firmware-version: 0.13-4
bus-info: 0000:00:19.0
Any suggestions for getting stability back on the original NIC?
thats the the instructions that i used and the driver as well. works on my X9SCM-F-O with esxi 5.1 with no issues so farHi,
has anyone tried this 82579LM driver?
http://virtual-drive.in/2012/11/16/enabling-intel-nic-82579lm-on-intel-s1200bt-under-esxi-5-1/
Thanks
esxcli software acceptance set --level=CommunitySupported
esxcli software vib install -v http://shell.peach.ne.jp/~aoyama/wordpress/download/net-e1000e-2.3.2.x86_64.vib
-or-
esxcli software vib install -v http://files.v-front.de/net-e1001e-1.0.0.x86_64.vib
~ # vmkload_mod -u e1000e
Module e1000e successfully unloaded
~ # vmkload_mod e1000e
Module e1000e loaded successfully
Module heap vmklnx_e1000e: creation succeeded. id = 0x4110cc7ac000
<6>Intel(R) PRO/1000 Network Driver - 2.3.2-NAPI
<6>Copyright(c) 1999 - 2013 Intel Corporation.
PCI: driver e1000e is looking for devices
<6>e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
<6>e1000e 0000:00:19.0: Using NUMA node 0 for memory allocations
Enabling MSI for dev 0000:00:19.0
IntrVector: 288: Vector 0x32 allocated 1 interrupts (intrType 2)
Disabling MSI for dev 0000:00:19.0
IOMMUIntel: 3749: FreeIRTE index 0x10 Vector 0x32
VMK_PCI: 720: device 0000:00:19.0allocated 1 interrupts (intrType1)
[B]WARNING: vmklinux: pci_announce_device:1488: PCI: driver e1000e probe failed for device 0000:00:19.0[/B]
LinPCI: LinuxPCI_DeviceUnclaimed:275: Device 0000:00:19.0 unclaimed.
PCI: driver e1000e claimed 0 device
Mod: 4780: Initialization of e1000e succeeded with module ID 4190
e1000e loaded successfully.