- Intel(r) I219v Slow Speed
- Intel I218v Vs Killer E2205
- Intel I218v Vs I211at
- Intel(r) I219v 1 X Gigabit Lan
- Hi wb, This appears to be a feature of the 'Intel Ethernet Connection I218-V', so much so that Intel created a batch file (on behalf of ASUS) to fix this problem in Windows 8.1.
- Net-e1000e (obsolete!) Description. Because with ESXi 5.5 Update 3 VMware introduced a newer version of e1000e which supports the same set of devices plus Intel i219 adapters (PCI IDs 8086:156f, 8086:1570, 8086:15b7, 8086:15b8)! Please use this instead. For details read this blog post.
- Use whichever you want. Unless the port is defective, you are not going to see much of a difference between any two. Intel's summary does not say much about what their chip can do but Realtek's mentions some offloading capabilities so the Realtek may have somewhat lower CPU usage.
I'm having troubles in enabling Wake On Lan on an Intel I218-V network adapter. It's integrated in an Asus Z97-A board.
The BIOS is properly set, since WOL works under Linux.
For Windows 10, it is my understanding that you have to enable it from Device Manager, as countless tutorials recommend.
But I cannot select the proper checkbox, since it's inactive:
Suggestions?
MadHatterMadHatter
Editing the INF is a great idea. However I was able to get everything working on a MSI Z97 MPOWER MAX AC with the Intel I218-V on board Network Chip by forcing it to use the Intel I218-LM version #2. It is working so far and even the unmodified Intel utility software installs fine. It just sees the forced installed I218-LM driver and moves on.
migrated from serverfault.comJan 16 '18 at 5:45
This question came from our site for system and network administrators.
1 Answer
You need to enable
Power on by PME
in BIOS setup / APM. Without it, the NIC signals WoL but the board ignores it.Zac67Zac67
Not the answer you're looking for? Browse other questions tagged windowsnetworkingwake-on-lan or ask your own question.
Posted by2 years ago
Archived
ESXi 6.5 - Intel I219-V not workingdespite being on the HCL (NUC7 onboard-nic)
Hello everyone, i'm out of ideas.
vmnic0 isn't working on the latest NUC7i3BNH, installer just gives me the dreaded 'no network adapter found'.
So i popped in my USB-Ethernet Adapters and updated the installer with r8152 drivers, that worked and i can start looking for the error with the onboard-nic:
[root@ESX2:/var/log] esxcfg-nics -l
Name PCI Driver Link Speed Duplex MAC Address MTU Description
Corel draw 11 for mac free download. vmnic32 Pseudo r8152 Up 1000Mbps Full 84:16:f9:17:f7:e3 1500 Unknown Unknown
But where is vmnic0 - it's not working.
[root@ESX2:/tmp] lspci -v | grep 'Class 0200' -B 1
0000:00:1f.6 Ethernet controller Network controller: Intel Corporation Ethernet Connection (4) I219-V [vmnic0] Class 0200: 8086:15d8
I used the latest ESXi 6.5a Image (VMware-VMvisor-Installer-201701001-4887370.x86_64.iso), so i guess the NUC7/I219-V should actually work out of the box?
Now, here is where i got confused:
[root@ESX2:~] grep 15d8 /etc/vmware/driver.map.d/* /etc/vmware/driver.map.d/e1000e.map:regtype=linux,bus=pci,id=8086:15d8 0000:0000,driver=e1000e,class=network
There it is, that should be the correct driver. Yet it does not work.
[root@ESX2:~] grep 15d8 /var/log/.
/var/log/jumpstart-stdout.log:Error binding driver ne1000 for bus=pci addr=m00008501 id=808615d880862068020000
/var/log/jumpstart-stdout.log:Error binding driver vmklinux_9 for bus=pci addr=m00008501 id=808615d880862068020000
/var/log/vmkdevmgr.log:2017-02-09T22:11:53Z vmkdevmgr[65908]: ADD event for bus=pci addr=m00008501 id=808615d880862068020000.
/var/log/vmkdevmgr.log:2017-02-09T22:11:53Z vmkdevmgr[65908]: Found driver ne1000 for device bus=pci addr=m00008501 id=808615d880862068020000.
/var/log/vmkdevmgr.log:2017-02-09T22:11:53Z vmkdevmgr[65908]: Error binding driver ne1000 for bus=pci addr=m00008501 id=808615d880862068020000
/var/log/vmkdevmgr.log:2017-02-09T22:11:53Z vmkdevmgr[65908]: Found driver e1000e for device bus=pci addr=m00008501 id=808615d880862068020000.
/var/log/vmkdevmgr.log:2017-02-09T22:11:53Z vmkdevmgr[65908]: Error binding driver vmklinux_9 for bus=pci addr=m00008501 id=808615d880862068020000
/var/log/vmkdevmgr.log:2017-02-09T23:23:38Z vmkdevmgr[65906]: ADD event for bus=pci addr=m00008501 id=808615d880862068020000.
/var/log/vmkdevmgr.log:2017-02-09T23:23:38Z vmkdevmgr[65906]: Found driver ne1000 for device bus=pci addr=m00008501 id=808615d880862068020000.
/var/log/vmkdevmgr.log:2017-02-09T23:23:38Z vmkdevmgr[65906]: Error binding driver ne1000 for bus=pci addr=m00008501 id=808615d880862068020000
/var/log/vmkdevmgr.log:2017-02-09T23:23:38Z vmkdevmgr[65906]: Found driver e1000e for device bus=pci addr=m00008501 id=808615d880862068020000.
/var/log/vmkdevmgr.log:2017-02-09T23:23:38Z vmkdevmgr[65906]: Error binding driver vmklinux_9 for bus=pci addr=m00008501 id=808615d880862068020000
/var/log/vmkernel.log:0:00:00:04.602 cpu0:65536)PCI: 1024: 0000:00:1f.6: probing 8086:15d8 8086:2068
/var/log/vmkernel.log:0:00:00:04.603 cpu0:65536)PCI: 1231: 0000:00:1f.6: registering 8086:15d8 8086:2068
/var/log/vmkernel.log:0:00:00:04.603 cpu0:65536)Device: 1320: Registered device: 0x4302fabd4c10 m00008501 808615d880862068020000 (parent=0x60194302fabd4542)
/var/log/vmkernel.log:2017-02-09T22:11:53.267Z cpu1:65908)DEBUG (ne1000): device ID: 8086:15d8:8086:2068
/var/log/vmkernel.log:2017-02-09T22:11:53.267Z cpu1:65908)WARNING: Device: 2223: Failed to start device 0x4302fabd4c10 m00008501 808615d880862068020000.
/var/log/vmkernel.log:2017-02-09T22:11:53.268Z cpu1:65908)WARNING: Device: 2453: Device 0x4302fabd4c10 m00008501 808615d880862068020000 already claimed (state=6).
Intel(r) I219v Slow Speed
/var/log/vmkernel.log:0:00:00:04.612 cpu0:65536)PCI: 1024: 0000:00:1f.6: probing 8086:15d8 8086:2068
/var/log/vmkernel.log:0:00:00:04.613 cpu0:65536)PCI: 1231: 0000:00:1f.6: registering 8086:15d8 8086:2068
/var/log/vmkernel.log:0:00:00:04.613 cpu0:65536)Device: 1320: Registered device: 0x4302fabd4c90 m00008501 808615d880862068020000 (parent=0x3e804302fabd454a)
Intel I218v Vs Killer E2205
/var/log/vmkernel.log:2017-02-09T23:23:38.238Z cpu3:65906)DEBUG (ne1000): device ID: 8086:15d8:8086:2068
/var/log/vmkernel.log:2017-02-09T23:23:38.238Z cpu3:65906)WARNING: Device: 2223: Failed to start device 0x4302fabd4c90 m00008501 808615d880862068020000.
/var/log/vmkernel.log:2017-02-09T23:23:38.239Z cpu3:65906)WARNING: Device: 2453: Device 0x4302fabd4c90 m00008501 808615d880862068020000 already claimed (state=6).
/var/log/vmksummary.log:2017-02-09T22:11:53.267Z cpu1:65908)WARNING: Device: 2223: Failed to start device 0x4302fabd4c10 m00008501 808615d880862068020000.
/var/log/vmksummary.log:2017-02-09T22:11:53.268Z cpu1:65908)WARNING: Device: 2453: Device 0x4302fabd4c10 m00008501 808615d880862068020000 already claimed (state=6).
/var/log/vmksummary.log:2017-02-09T23:23:38.238Z cpu3:65906)WARNING: Device: 2223: Failed to start device 0x4302fabd4c90 m00008501 808615d880862068020000.
/var/log/vmksummary.log:2017-02-09T23:23:38.239Z cpu3:65906)WARNING: Device: 2453: Device 0x4302fabd4c90 m00008501 808615d880862068020000 already claimed (state=6).
Intel I218v Vs I211at
Now what?
Intel(r) I219v 1 X Gigabit Lan
81% Upvoted