VMware Fusion 1.1 (Build: 62573, released 11/12/2007) under Mac OS X 10.5.
I have to disable roaming and enable DHCP in order to get network access to work properly.
NetworkManager pop-up from tray displays "No network devices have been found" greyed out.
I seem to have the same issues in /sys/class/net:
$ ls -l /sys/class/net/
total 0
drwxr-xr-x 4 root root 0 2007-11-14 10:12 eth0
drwxr-xr-x 4 root root 0 2007-11-14 10:12 lo
$ ls -l /sys/class/net/*/devices
ls: /sys/class/net/*/devices: No such file or directory
Does anyone have the RPM or tarball for previous versions that did work? I'm thinking VMware Fusion beta or perhaps RC1 might have worked properly, I don't recall at the moment. I'd be happy to try previous drivers and see what works, and diff the source to see what might be different.
If any further information is needed, I'll be happy to help where I can. I am inclined to believe something changed in VMware's vmxnet driver that causes it not to play properly with sysfs, but above and beyond that, I have no idea.
I've got to add a "me too" comment here.
Ubuntu Gutsy Gibbon (7.10)
$ uname -r
2.6.22-14-generic
VMware Fusion 1.1 (Build: 62573, released 11/12/2007) under Mac OS X 10.5.
I have to disable roaming and enable DHCP in order to get network access to work properly.
NetworkManager pop-up from tray displays "No network devices have been found" greyed out.
I seem to have the same issues in /sys/class/net:
$ ls -l /sys/class/net/ net/*/devices net/*/devices: No such file or directory
total 0
drwxr-xr-x 4 root root 0 2007-11-14 10:12 eth0
drwxr-xr-x 4 root root 0 2007-11-14 10:12 lo
$ ls -l /sys/class/
ls: /sys/class/
Does anyone have the RPM or tarball for previous versions that did work? I'm thinking VMware Fusion beta or perhaps RC1 might have worked properly, I don't recall at the moment. I'd be happy to try previous drivers and see what works, and diff the source to see what might be different.
If any further information is needed, I'll be happy to help where I can. I am inclined to believe something changed in VMware's vmxnet driver that causes it not to play properly with sysfs, but above and beyond that, I have no idea.