Port Devices


Posted On
Posted By admin

I just change it to read: By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of service , privacy policy and cookie policy , and that your continued use of the website is subject to these policies. After modifying the file, I ran update-modules and rebooted the machine and I still have pcnet32 being used by the nic. VMware vmxnet virtual NIC driver release 3. If you’d like to contribute content, let us know. If you need to reset your password, click here. I’ve tride going straight to step 2, but then eth0 was still on pcnet32 after reboot.

Uploader: Tetaur
Date Added: 26 October 2010
File Size: 16.21 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 29407
Price: Free* [*Free Regsitration Required]

Extract initrd image to a temp directory: I commented out the 2 lines added by the vmware tools for the nics and added the one in bold as you suggested. Since changing this on all VMs will be a lot of work since its only doable from the config file?

For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. All times are GMT I’ve tride going straight to step 2, but then eth0 was still on pcnet32 after reboot.


You ljnux not post a blank message. Which virtualization product are you using? I noticed that even if I got the vmware tools installed with the vmxnet driver, the guest system still use the pcnet32 driver.

We are using ESXi 4. Pccnet32 can I load pcnet32 in slackware 10? If i run the following manually, I get to use the vmxnet driver no problem.

Email Required, but never shown.

CONFIG_PCNET32: AMD PCnet32 PCI support

I am assuming your original initrd image is named initrd. How can I solve this? Having trouble installing a piece of hardware? Also what version of vmware tools are you using.

Available on Rough Cuts at http: Exactly same problem here. It might be ne2k-pci. BB code is On. Find More Posts by bluecell.

AMD PCnet32 Lance problem

What you’ve got, from what I can google, needs the module: Please enter a title. I just updated all my linux machines on ESX and they all work fine. Ran “update-initramfs -u” which does the regenerating initrd part for your current kernel.


Server Fault works best with JavaScript enabled. Now everything works fine. Server, Workstation or ESX? What virtualization tool are you using? If you’d like to contribute content, let us know. Best regards, Edward L.

For ESX Debian etch requires some patches to vmware-tools. By using our site, you acknowledge that you have read and understand our Cookie PolicyPrivacy Policyand our Terms of Service. This tool uses JavaScript and much of it will not work correctly without it enabled. This works, but it does not use the vmxnet driver on reboot. Registration is quick, simple and lcnet32 free.