Intel 82579LM and 82579V

Discussion in 'Virtualized Computing' started by Chilly, May 13, 2011.

  1. 2eleven

    2eleven n00bie

    Messages:
    2
    Joined:
    May 1, 2012
    I'm also very interested in this fix so I can move to 5.0. I've been sticking with 4.1 in the mean time as that driver has been stable for me. Many thanks to Chilly for all the work he's done.
     
  2. bmeehan

    bmeehan n00bie

    Messages:
    8
    Joined:
    Mar 4, 2012
    I too am also interested in a solution as I've just pulled the trigger on this mother board.

    http://secure.newegg.com/WishList/PublicWishDetail.aspx?WishListNumber=18663045

    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.

    BTW -- The 2 x 8GB memory price is now starting to drop. Kingston just dropped the price from 259 per pair to 222 per pair. Although Newegg doesn't carry it again yet.

    I'd also like to add a thanks to chilly for working on this, you probably don't realize how much your efforts are appreciated.
     
  3. 2eleven

    2eleven n00bie

    Messages:
    2
    Joined:
    May 1, 2012
    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.
     
  4. rapster

    rapster n00bie

    Messages:
    1
    Joined:
    May 5, 2012
  5. bmh.01

    bmh.01 Gawd

    Messages:
    610
    Joined:
    Mar 28, 2002
    I'll try it out as soon as I get chance.
     
  6. bmh.01

    bmh.01 Gawd

    Messages:
    610
    Joined:
    Mar 28, 2002
    Code:
    ~ # 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.
    
    Tried it directly from the vm-help link and also from my own internal web server, same result. Nothing of great extra help in the logs unless i'm looking in the wrong place.
     
    Last edited: May 6, 2012
  7. bmh.01

    bmh.01 Gawd

    Messages:
    610
    Joined:
    Mar 28, 2002
    Right after realizing i'm an idiot and missed the .zip extension its still not good news. Vib installs fine but hangs ESXi when booting at esxfw loaded successfully.
     
  8. buckweet1980

    buckweet1980 n00bie

    Messages:
    2
    Joined:
    May 12, 2012
    I have a problem with this latest driver causing high cpu issues. It is also causing the machine to stall here and there. I went back to the 1.0 driver and issues are not there.

    Also is jumbo frames supported? Whenever I tried to do 9000 MTU with this driver it essentially hangs esxi up.

    What can I do to help?
     
  9. Chilly

    Chilly 2[H]4U

    Messages:
    2,110
    Joined:
    Oct 3, 2005
    FYI that is NOT my driver. It is a driver created by ichi.

    I am working on an update to my driver, but life has a way of becoming busy at times. ;)

    I'll get in contact with ichi and see if there's anything I can do to help him or vice versa. :)
     
  10. buckweet1980

    buckweet1980 n00bie

    Messages:
    2
    Joined:
    May 12, 2012
    My appologies :) I saw the naming was the same so I just assumed.

    Let me know how I can help. I'd like to see a newer more mature driver available if we can.

    Thanks!
     
  11. DlStreamnet

    DlStreamnet Limp Gawd

    Messages:
    359
    Joined:
    Mar 10, 2005
    Hey guys,

    New to this and just bought an Intel DQ67SW, with the intel 82579lm.

    Would the best driver to use be the link posted most recently (ichi?)

    If I use said driver, can I change it at a later date for a more reliable one? (I would like jumbo frames).

    Do I inject the driver using the ESXi Customizer?

    Many thanks.
     
  12. REDYOUCH

    REDYOUCH [H]ardness Supreme

    Messages:
    4,541
    Joined:
    Mar 17, 2001
    Bump! I have a SuperMicro board with the 82579LM and would love to find the latest and best supported driver. Any updates?
     
  13. bmh.01

    bmh.01 Gawd

    Messages:
    610
    Joined:
    Mar 28, 2002
    Short answer is there isn't one. Chilly's driver works but only if you are only using the 82579LM with no other NICs (intel ones at least).
     
  14. arryo

    arryo n00bie

    Messages:
    49
    Joined:
    May 23, 2012
    Thanks to Chilly, now i have both drivers working in x9scm board
     
  15. schleicher

    schleicher n00bie

    Messages:
    38
    Joined:
    Jun 4, 2012
    Hardware:

    Mainboard: SUPERMICRO X9SCM-F
    CPU: Intel Xeon E3-1230 V2
    RAM: 4 x KINGSTON 8GB DDR3 1333MHz ECC CL9 KVR1333D3E9S/8G

    ~ # vmware -v
    VMware ESXi 5.0.0 build-623860

    ~ # vmware -l
    VMware ESXi 5.0.0 Update 1

    ~ # esxcli software acceptance get
    CommunitySupported

    ~ # lspci
    000:000:00.0 Bridge: Intel Corporation
    000:000:25.0 Network controller: Intel Corporation 82579V Gigabit Network Connection [vmnic1]
    000:000:26.0 Serial bus controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2
    000:000:28.0 Bridge: Intel Corporation Cougar Point PCI Express Root Port 1 [PCIe RP[000:000:28.0]]
    000:000:28.4 Bridge: Intel Corporation Cougar Point PCI Express Root Port 5 [PCIe RP[000:000:28.4]]
    000:000:29.0 Serial bus controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1
    000:000:30.0 Bridge: Intel Corporation 82801 PCI Bridge
    000:000:31.0 Bridge: Intel Corporation Cougar Point LPC Controller
    000:000:31.2 Mass storage controller: Intel Corporation Cougar Point 6 port SATA AHCI Controller [vmhba0]
    000:000:31.3 Serial bus controller: Intel Corporation Cougar Point SMBus Controller
    000:002:00.0 Network controller: Intel Corporation 82574L Gigabit Network Connection [vmnic0]
    000:003:03.0 Display controller: Matrox Graphics, Inc. MGA G200eW WPCM450

    ~ # esxcfg-nics -l
    Name PCI Driver Link Speed Duplex MAC Address MTU Description
    vmnic0 0000:02:00.00 e1000e Up 1000Mbps Full 00:25:90:77:64:2c 1500 Intel Corporation 82574L Gigabit Network Connection

    ~ # esxcli software vib list
    Name Version Vendor Acceptance Level Install Date
    -------------------- ---------------------------------- ------ ------------------ ------------
    net-e1001e 1.0.0 Chilly CommunitySupported 2012-06-19
    ata-pata-amd 0.3.10-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ata-pata-atiixp 0.4.6-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ata-pata-cmd64x 0.2.5-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ata-pata-hpt3x2n 0.3.4-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ata-pata-pdc2027x 1.0-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ata-pata-serverworks 0.4.3-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ata-pata-sil680 0.4.8-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ata-pata-via 0.3.3-2vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    block-cciss 3.6.14-10vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ehci-ehci-hcd 1.0-3vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    esx-base 5.0.0-1.11.623860 VMware VMwareCertified 2009-01-02
    esx-tboot 5.0.0-0.0.469512 VMware VMwareCertified 2009-01-02
    ima-qla4xxx 2.01.07-1vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ipmi-ipmi-devintf 39.1-4vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ipmi-ipmi-msghandler 39.1-4vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ipmi-ipmi-si-drv 39.1-4vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    misc-cnic-register 1.1-1vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    misc-drivers 5.0.0-1.11.623860 VMware VMwareCertified 2009-01-02
    net-be2net 4.0.88.0-1vmw.500.0.7.515841 VMware VMwareCertified 2009-01-02
    net-bnx2 2.0.15g.v50.11-5vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-bnx2x 1.61.15.v50.1-1vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-cnic 1.10.2j.v50.7-2vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-e1000 8.0.3.1-2vmw.500.0.7.515841 VMware VMwareCertified 2009-01-02
    net-e1000e 1.1.2-3vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    net-enic 1.4.2.15a-1vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-forcedeth 0.61-2vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-igb 2.1.11.1-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-ixgbe 2.0.84.8.2-10vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-nx-nic 4.0.557-3vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    net-r8168 8.013.00-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-r8169 6.011.00-2vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-s2io 2.1.4.13427-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-sky2 1.20-2vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    net-tg3 3.110h.v50.4-4vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    ohci-usb-ohci 1.0-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    sata-ahci 3.0-6vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    sata-ata-piix 2.12-4vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    sata-sata-nv 3.5-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    sata-sata-promise 2.12-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    sata-sata-sil 2.3-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    sata-sata-svw 2.3-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-aacraid 1.1.5.1-9vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    scsi-adp94xx 1.0.8.12-6vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-aic79xx 3.1-5vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-bnx2i 1.9.1d.v50.1-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-fnic 1.5.0.3-1vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-hpsa 5.0.0-17vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-ips 7.12.05-4vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-lpfc820 8.2.2.1-18vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-megaraid-mbox 2.20.5.1-6vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-megaraid-sas 5.34-1vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    scsi-megaraid2 2.00.4-9vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-mpt2sas 06.00.00.00-6vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    scsi-mptsas 4.23.01.00-5vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-mptspi 4.23.01.00-5vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-qla2xxx 901.k1.1-14vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-qla4xxx 5.01.03.2-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    scsi-rste 2.0.2.0088-1vmw.500.1.11.623860 VMware VMwareCertified 2009-01-02
    uhci-usb-uhci 1.0-3vmw.500.0.0.469512 VMware VMwareCertified 2009-01-02
    tools-light 5.0.0-1.11.623860 VMware VMwareCertified 2009-01-02

    ~ # cat /var/log/esxupdate.log
    expert from:
    2012-06-19T00:35:41Z esxupdate: downloader: DEBUG: Downloading from http://files.v-front.de/net-e1001e-1.0.0.x86_64.vib...
    2012-06-19T00:35:41Z esxupdate: Transaction: INFO: Skipping installed VIBs
    2012-06-19T00:35:41Z esxupdate: Transaction: INFO: Final list of VIBs being installed: Chilly_bootbank_net-e1001e_1.0.0
    2012-06-19T00:35:41Z esxupdate: imageprofile: INFO: Adding VIB Chilly_bootbank_net-e1001e_1.0.0 to ImageProfile (Updated) ESXi-5.0.0-20120302001-standard

    It simply does not work for me...

    Any hints are welcome, maybe the second lan port is defective, haven't tested yet...
    Does the method only work with a plain vanilla 5.0 install, or did anyone also try the update 1 already?

    What i don't get the controller is listed as [vmnic1] with lspci, but it does not show up in the esxi network
    controllers. Is there anything in need to do in addition to get it work (there is no device in vtd mode though)?

    Edit:

    When i remove the vib again lspci looks like this:

    ~ # lspci
    000:000:00.0 Bridge: Intel Corporation
    000:000:25.0 Network controller: Intel Corporation 82579V Gigabit Network Connection
    000:000:26.0 Serial bus controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2
    000:000:28.0 Bridge: Intel Corporation Cougar Point PCI Express Root Port 1 [PCIe RP[000:000:28.0]]
    000:000:28.4 Bridge: Intel Corporation Cougar Point PCI Express Root Port 5 [PCIe RP[000:000:28.4]]
    000:000:29.0 Serial bus controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1
    000:000:30.0 Bridge: Intel Corporation 82801 PCI Bridge
    000:000:31.0 Bridge: Intel Corporation Cougar Point LPC Controller
    000:000:31.2 Mass storage controller: Intel Corporation Cougar Point 6 port SATA AHCI Controller [vmhba0]
    000:000:31.3 Serial bus controller: Intel Corporation Cougar Point SMBus Controller
    000:002:00.0 Network controller: Intel Corporation 82574L Gigabit Network Connection [vmnic0]
    000:003:03.0 Display controller: Matrox Graphics, Inc. MGA G200eW WPCM450


    Thanks in advance!

    Greets schleicher
     
    Last edited: Jun 19, 2012
  16. schleicher

    schleicher n00bie

    Messages:
    38
    Joined:
    Jun 4, 2012
    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
     
  17. Xfinity

    Xfinity n00bie

    Messages:
    57
    Joined:
    Apr 14, 2009
    Thats great news and I am glad that your troubles are resolved. Do you mind sharing the files from supermicro?
     
  18. schleicher

    schleicher n00bie

    Messages:
    38
    Joined:
    Jun 4, 2012
    Hi!

    Ehm no, i think thats ok to share, i hope i don't get in trouble with supermicro ;)

    UPDATE: ONLY DO THIS IF YOUR NIC IS NOT WORKING AT ALL!!!!
    CHECK THIS ON OTHER OPERATING SYSTEMS.
    NOT THAT EVERYONE HAVING PROBLEMS GETTING THE NIC TO WORK
    IS FLASHING AND ITS NOT NECESSARY.


    USE THIS AT YOUR OWN RISK AND ONLY IF YOU KNOW WHAT YOU ARE DOING.
    I AM NOT RESPONSIBLE FOR ANY DAMAGES CAUSING THIS!!!


    BEST IS TO WRITE DOWN THE MAC ADDRESSES BEFORE FLASHING!!!

    SUPERMICRO X9SCM-F NIC EPROMS

    From the support mail:

    "For the boards that have a corrupted LAN 2 port, please update the LAN EEPROM which will fix the problem. If you are not able to boot to the bootable USB, please disable IPMI by moving jumper JPB to pins 2 and 3. The LAN EEPROM package is attached above which is labeled “X9SCL5”. For boards that still have 1.0c BIOS, you will have to update it to 1.1a first before updating it to 2.0 BIOS. I have also attached the file named “x9scm1.928” which is the 1.1a BIOS.

    Steps to flash onboard LAN EEPROM

    Extract the files and Copy them to a bootable USB stick or to a bootable floppy disk. (If you don’t have a bootable USB stick you can make it using:
    http://www.softpedia.com/get/System/Boot-Manager-Disk/BootFlashDOS.shtml).
    http://www.softpedia.com/get/System/Hard-Disk-Utils/HP-USB-Disk-Storage-Format-Tool.shtml

    Boot up the system using the USB stick.
    At the command prompt type --- <filename>.bat
    Enter the 48-bit LAN MAC address, when prompted.
    Power cycle the system.
    Reinstall the LAN drivers after EEPROM is flashed. ftp://ftp.supermicro.com/driver/LAN/

    When you flash the boards to BIOS version 2.0, please follow these step by step instructions so that you do not get a corrupted LAN 2 again.

    1. Enable LAN2 OPROM in BIOS then boot up to USB
    2. Rename afudosu.smc to afudosu.exe
    3. Type in as follows "afudosu x9scm2.508 /p /b /n /r /k /fdt /mer /opr"
    4. Unplug AC power after successful flash (when prompt shows up)
    5. Power back on

    Please let us know if you run into any complications or if you have any other questions."

    Anyways the workflow not to corrupt the rom again did not work for me, i had to flash the
    nics again after updating to the latest bios version.

    Greets schleicher
     
    Last edited: Jun 21, 2012
  19. Snowknight26

    Snowknight26 [H]ardness Supreme

    Messages:
    4,124
    Joined:
    May 8, 2005
    Thanks schleicher, I was wondering why my rev 1.11a X9SCL-F had a NIC that showed up as 82579V (VEN_8086&DEV_1503) instead of 82579LM (VEN_8086&DEV_1502).
     
  20. BoomGoesTheDynamite

    BoomGoesTheDynamite n00bie

    Messages:
    13
    Joined:
    Jul 5, 2012
    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?
     
  21. Monstieur

    Monstieur Limp Gawd

    Messages:
    147
    Joined:
    Jun 10, 2011
    I'm going to test this on ESXi 5.1. I wonder if there are optimisations that Chilly can perform for 5.1.
     
  22. bmh.01

    bmh.01 Gawd

    Messages:
    610
    Joined:
    Mar 28, 2002
    I had no sucess with 5.1 either, although VMMV.
     
  23. danswartz

    danswartz 2[H]4U

    Messages:
    3,585
    Joined:
    Feb 25, 2011
    I'm still astonished how a year later, this NIC is still not officially supported. Is it just that uncommon? Or what?
     
  24. eltarik

    eltarik n00bie

    Messages:
    1
    Joined:
    Oct 23, 2012
    Installed ESXi 5.1 & though via local CLI I can see the two nics (Intel 82579LM and 82579V) using lspci, I only have ONE network adapter via the System Customization interface on the local server. vSphere client also just shows me ONE network adapter. I have tried using the e10001 vib file others have used for solving this issue and when I use the command "esxcli software vib install" to install it, I always get the same vmware error saying that file not found in depot, even though it is locally present in both the datastore1 and the /var/log/vmware/ directories!
    Going really crazy with this. It is the reason I love windows and hate linux. I can do anything in windows, but in linux, it is a nightmare hehehe.
    Any help much appreciated!
     
  25. TeeJayHoward

    TeeJayHoward Limpness Supreme

    Messages:
    9,047
    Joined:
    Feb 8, 2005
    Hopefully this isn't too bad of a necro, but since the information is still relevant, and might help someone else...

    Got it working on my X9SCM by doing the following:
    1) Install ESXi 5.1
    2) Enable console
    3) Alt+F1, and type the following:
    Code:
    esxcli software acceptance set –-level=CommunitySupported
    esxcli software vib install -v http://files.v-front.de/net-e1001e-1.0.0.x86_64.vib
    4) Alt+F2 when it's done (took me forever) and disable IPv6
    5) It's gonna reboot. Let it do it's thing.
    6) Configure Management Network, Network Adapters, toggle vmnic1

    Might have skipped a step or two, doing this out of memory. Still, it's up and running!
     
  26. Monstieur

    Monstieur Limp Gawd

    Messages:
    147
    Joined:
    Jun 10, 2011
    Motherboards with this NIC are even on the VMware HCL list. e.g. Intel S1200BTS.
     
  27. BoomGoesTheDynamite

    BoomGoesTheDynamite n00bie

    Messages:
    13
    Joined:
    Jul 5, 2012
    The only way I was able to get the 82574L NIC to work again was to uninstall the community driver. I would like to have both working agin, are there any updates? I am currently running 5.1 on two esxi boxes. One box works fine with the 1.0.0 community driver on both NICs.
     
  28. aeros2k

    aeros2k n00bie

    Messages:
    5
    Joined:
    Jan 8, 2013
  29. nicolas9510

    nicolas9510 Limp Gawd

    Messages:
    169
    Joined:
    Sep 21, 2006
  30. hjgmcse98

    hjgmcse98 n00bie

    Messages:
    1
    Joined:
    Mar 17, 2013
    do you have the oem.tgz for intel driver 82579V for esxi 5.1
     
  31. webbrowser

    webbrowser n00bie

    Messages:
    31
    Joined:
    Jun 12, 2013
  32. Rectal Prolapse

    Rectal Prolapse Gawd

    Messages:
    575
    Joined:
    Jan 19, 2007
    Thanks webbrowser for the update! Will this work with ESX 5.0 too?
     
  33. sybreeder

    sybreeder Limp Gawd

    Messages:
    193
    Joined:
    Oct 24, 2010
    That version 2.3.2 works without any problem :) Thanks :)
     
  34. bmh.01

    bmh.01 Gawd

    Messages:
    610
    Joined:
    Mar 28, 2002
    This version seems to have fixed the issues with other intel adapters that i've experienced with the earlier versions. Good to see!
     
  35. DillonFoulds

    DillonFoulds n00bie

    Messages:
    1
    Joined:
    Nov 23, 2013
    I hope this isn't necro-bumping too hard, again, for this thread...

    My hardware is:

    Acer AC100
    Onboard NIC: Intel 82579LM (8086:1502 - 0000:00:19.0) [vmnic1]
    PCIe NIC: Broadcom BCM5721 (14e4:1659 - 0000:01:00.0) [vmnic0]

    I've tried using 5.1.0, 5.1.0u1, and 5.5.0 all on fresh vanilla installs, or with net-e1000e-1.0.0.x86_64.VIB or net-e1000e-2.3.2.x86_64.vib slipstreamed in with the ESXi Customizer tools. I'm using LiLi to copy the ISOs to USB for installation.

    The installs all complete okay. On the vanilla installs, I run the following two commands:

    Code:
    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
    
    The drivers both will install fine and I'll disable IPv6 (as a precautionary only, not disabling makes no difference).

    When I run:
    Code:
    ~ # vmkload_mod -u e1000e
    Module e1000e successfully unloaded
    ~ # vmkload_mod e1000e
    Module e1000e loaded successfully
    Alt+F12 says a different story though!

    I get (paraphrasing)...
    Code:
    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.
    
    Hmmm...

    ~ #: lspci -v |grep net
    0000:00:19.0 Ethernet controller Network controller: Intel Corporation 82579LM Gigabit Network Connection [vmnic1]
    0000:01:00.0 Ethernet controller Network controller: Broadcom Coporation NetXtreme BCM5721 Gigabit Ethernet [vmnic0]

    ... so vmnicX IDs are being assigned for both interfaces. vmnic0 and vmnic1 both show up in passthrough, but only the Broadcom one [vmnic0] shows up in the network adapters list.

    In my BIOS I've got...
    [Processor Configuration]
    Intel Virtualization Technology - Enabled
    C1E Support - Disabled
    CPU C6 Report - Disabled

    [PCI Configuration]
    PCI Express Slot #1 I/O ROM - Disabled
    Onboard LAN Controller - Enabled
    Onboard LAN I/O ROM - Disabled
    PCI Rom Priority - Legacy ROM (Alternate option of EFI Compatible ROM)

    I'm at a loss of where to proceed from here. Does anyone have any suggestions or possible commands I could run for further diagnostics?