On Mon, 2004-02-23 at 21:08, Alex Angerhofer wrote:
Hi Mark and everybody else who may be concerned about this. The problem is solved. vmware is now running fine on the latest suse 9.0 patch kernel, 2.4.21-192. The guilty party is the vmnet.o module. You don't want to use the one that is being supplied by the km_vmware package! Use the one that is being generated by running vmware-config.pl. However, you do want to use the vmmon.o that comes from km_vmware. I am also using vmppuser.o derived from km_vmware (I don't think it actually matters as it doesn't seem to get transplanted by the config script). That's all. Good luck, Alex.
Hey Alex, You certainly got down deeper than I did! I took David Bottrill's advice and got the latest any-any patch from the VMware Patch Maintainer site at http://ftp.cvut.cz/vmware/. The -50 version I had did not work, but a -51 version was released a few days ago, and that did work. There are no instructions with the any-any update patch, but basically all I did was (not sure if all steps are truly necessary, but...): 1. Install the new kernel and kernel sources. 2. Using YaST, disable vmware services 3. Reboot. 4. As root, run: 4a. cd /usr/src/linux 4b. make cloneconfig 4c. make dep && make clean 5. Unpack the vmware-any-any-update51.tar.gz patch 6. Run as root the runme.pl script from the any-any patch. 6a. Allow the runme.pl script to overwrite the modules. 6b. Ignore any errors. 6c. Allow the runme.pl script to launch vmware-config.pl. 7. Allow vmware-config.pl to build the modules. 8. Re-enable vmware services in YaST 9. Launch VMware. Looks like going forward before I update a kernel I'm going to wait a few days to see if a new any-any update gets released first. Thanks! Mark -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com