Re: D Link Dub E100 Driver Download Windows 8
Phyllis Sterlin
UPDATE: OK, this is just silly. I remebered I have acctualy onboard LAN so I edited rc.conf and dived into the dust under my desk to move cable and there I found out it was acctual onboard in use all the time Now this dosen't make much sense to me anymore, when I can't get net up all the stuff in dmesg is e100 related. Anyway, I connected network to e100 and rebooted, suprise, same story. Dmesg reported again link was not ready. I edited rc.conf to
Update: A Windows 10 driver now exists for the USB2-E1000. However, it will not appear in the CD that comes with the adapter until the next lot of adapters is shipped. The updated driver can be downloaded from this link: Windows 10/8/8.1, 7, Vista, and XP drivers for USB2-E1000.
In the context of setting up a virtual machine, e1000 emulates an Intel NIC, rtl8139 emulates a Realtek NIC, and virtio is a para-virtualized driver, i.e. it "knows" it's operating in a VM and basically just passes the network traffic between the VM and the host in the most straightforward way possible.
If you are running a legacy operating system within the VM, you may need to choose the virtual NIC according to what NICs are supported in the legacy OS. Intel e1000 has drivers available for even pretty old & obscure OSs. But the hardware of the physical e1000 NIC is pretty complex, so there will be some overhead because of the need to emulate it.
So far, I came to the same conclusion as you regarding the E1000/E1000E vs the VMXNET3. However, after reading a few articles on the web comparing the performance and overhead of the E1000, E1000E and VNXMET3 adapters, it seems that there are no significant performance degradation when using the emulated Intel adapters, especially between the E1000E and VMXNET3 on a gigabit physical network. So, since I don't need 10 Gbps link, I would prefer to use the driver that is actually recommended by VMware, the E1000E.
Summary: In VMware Guest running Windows Server 2012, or Windows Server 2012 R2, there is a problem running the Standard e1000e and e1000 drivers, resulting in loss of connections and possible corruption.
All Server 2012 VMs were built using the default e1000e NICs. They all functioned well, until we received the notice to immediately stop using the e1000e drivers as data corruption could occur. suggested fix was to switch to the e1000 or VMXNET3 driver. Given the fact we are a 1GB environment, I decided the e1000 would be the better driver. Also, some others informed of performance being better with the e1000 driver over VMXNET3 driver. With the change in place we ran for a week and maybe longer before we started noticing drives missing on the File Server (Server 2012 R2). A restart brings the drives back, as well as a disable, re-enable of the iSCSI NICs. This would happen randomly at all times day or night. Many searches later returned little about the errors, as it was not really producing any events, other than a basic network no longer available. After frustration, I decide to return to the e1000e driver on the ISCSI NICs. Problem solved, somewhat. We then started having the standard NIC (still on e1000) disappear and the server becoming unreachable. So, I believe the issue is the e1000 driver itself. I also have notice some less often, and shorter outages on the e1000e driver. Which lead me to the next test. I have now swapped all NICs to the VMXNET3 drivers on the Server 2012 R2 machines. No errors have been reported and no random (quick, or non quick) disconnects/reconnects. Drives seem stable, NICs are staying up.
This thread has been open for several months & I'm just checking to see if you have received an answer. I'm not sure if you've seen the alert bulletin on InfoSight pertaining to the e1000 NICs in VMware, but this has been an issue we've tried to communicate to our customers as much & often as possible. Here is a link to that notification: -bin/viewPDFFile?alert=NimbleStorageFieldAlertExt0003.pdf
I'm install windows 8.1 on HP Touchsmart 11-e110nr and have problem with driver ACPI\HPQ6007 (looks like unknown device in Windows device manager) ... I can not find link to download this driver on HP web site, all links what i found didn't work
aa06259810