Hello, I have been running VMWare 4.5.2 on my SuSE 9.3 for some time with no problem. When I started VMware today I got a message that there was an upgrade available and sure enough there was a 4.5.3 dated 12/27 available. I installed the RPM but got an error message when running vmware-config.pl: make: Leaving directory `/tmp/vmware-config3/vmnet-only' Unable to make a vmnet module that can be loaded in the running kernel: insmod: error inserting '/tmp/vmware-config3/vmnet.o': -1 Unknown symbol in module There is probably a slight difference in the kernel configuration between the set of C header files you specified and your running kernel. You may want to rebuild a kernel based on that directory, or specify another directory. This surprised me since just two weeks ago I rebuilt the VMware modules successfully when I upgraded the kernel. So, I figured no big deal I'll just re-install the older version of VMware and re-run vmware-config.pl to get back to where I was. Well, that didn't work! I am getting the same error. The one thing I tried was to re-run "make cloneconfig" and "make prepare-all" but that didn't help. Here is some info on my system: # uname -a Linux paulsen 2.6.11.4-21.10-smp #1 SMP Tue Nov 29 14:32:49 UTC 2005 i686 i686 i386 GNU/Linux # rpm -qa | grep VMware VMwareWorkstation-4.5.2-8848 Can anyone help me out with this? Thanks.
On Friday 30 December 2005 23:37, Robert Paulsen wrote:
Hello,
I have been running VMWare 4.5.2 on my SuSE 9.3 for some time with no problem.
When I started VMware today I got a message that there was an upgrade available and sure enough there was a 4.5.3 dated 12/27 available. I installed the RPM but got an error message when running vmware-config.pl:
make: Leaving directory `/tmp/vmware-config3/vmnet-only' Unable to make a vmnet module that can be loaded in the running kernel: insmod: error inserting '/tmp/vmware-config3/vmnet.o': -1 Unknown symbol in module There is probably a slight difference in the kernel configuration between the set of C header files you specified and your running kernel. You may want to rebuild a kernel based on that directory, or specify another directory.
To answer my own question -- I forgot that you need to run the vmware patch program whenever a new version of vmware is installed. The latest is vmware-any-any-update96.tar.gz. With that all worked well. Bob
participants (1)
-
Robert Paulsen