Comment 6 for bug 153635

Hi,

I am suffering from the same problem. I've had the Gutsy beta running for the past couple of weeks, with VMWare Tools installed, no problem. Today, there were 92 updates (I think), and since I've rebooted, the nm-applet has been telling me that "no network devices have been found". No luck re-building the VMWare Tools kernel modules, including vmxnet.

I have exactly the same output as Ryan Gordon in the /sys/class/net/ directory. No device file (link ?) in either the eth0/ or lo/ folders.

Alexander, I do not know how to answer the question "what driver is used ?". The Restricted Drivers Manager tells me the VMWare Virtual Ethernet Driver is in use.

The VMWare tools re-configuration/re-building script says something about the vmxnet driver vs. the (original ?) pcnet32 one, at the end :

To use the vmxnet driver, restart networking using the following commands:
/etc/init.d/networking stop
rmmod pcnet32
rmmod vmxnet
modprobe vmxnet
/etc/init.d/networking start

These commands do not help. rmmod pcnet32 says that no such module is presently loaded.

Finally, dmesg | grep eth0 gives no results on a freshly rebooted machine. dmesg | grep vmxnet says :

[ 8.752953] vmxnet: module license 'unspecified' taints kernel.
[ 8.753723] VMware vmxnet virtual NIC driver
[ 8.754040] Found vmxnet/PCI at 0x2024, irq 16.

Thanks in advance for any help.

-- David Holmes