On Sat, 2006-10-28 at 13:02 -0400, Jeffrey D. Yuille wrote: > Paul Smith wrote: > > On 10/28/06, Thomas Cameron <thomas.cameron@xxxxxxxxxxxxxxx> wrote: > >> Jeffrey D. Yuille wrote: > >> > I already manually installed the i686 kernel and the kernel-devel > >> > but I still come up with the same problem in installing VMware. What > >> > should I do next or where do I go to find out step-by-step to fix this > >> > problem? > >> > >> Have you rebooted so that the i686 kernel is running? > >> > >> What is the exact error you are seeing? Can you copy & paste it to the > >> list? > > > > The method here (in this thread) suggested caused a lot of booting > > problems in my case. Thus, in my opinion, a safer technique is the > > following: > > > > 1. keep the same i586 kernel; > > > > 2. download the i586 kernel-devel; > > > > 3. install it; > > > > 4. run vmware-config.pl . > > > > And that is all. > > > > Paul > > > Hello Paul, > > Here is a copy of the error that I come up with when trying to > install VMware server: > > [jeffy@jeffy ~]$ su - > Password: > [root@jeffy ~]# /usr/bin > -bash: /usr/bin: is a directory > [root@jeffy ~]# cd /usr/bin > [root@jeffy bin]# vmware-config.pl > Making sure services for VMware Server are stopped. > > Stopping VMware services: > Virtual machine monitor [ OK ] > Bridged networking on /dev/vmnet0 [ OK ] > DHCP server on /dev/vmnet1 [ OK ] > Host-only networking on /dev/vmnet1 [ OK ] > DHCP server on /dev/vmnet8 [ OK ] > NAT service on /dev/vmnet8 [ OK ] > Host-only networking on /dev/vmnet8 [ OK ] > Virtual ethernet [ OK ] > > Configuring fallback GTK+ 2.4 libraries. > > In which directory do you want to install the mime type icons? > [/usr/share/icons] /usr/share/icons > > What directory contains your desktop menu entry files? These files have a > .desktop file extension. [/usr/share/applications] /usr/share/applications > > In which directory do you want to install the application's icon? > [/usr/share/pixmaps] /usr/share/pixmaps > > Trying to find a suitable vmmon module for your running kernel. > > None of the pre-built vmmon modules for VMware Server is suitable for your > running kernel. Do you want this program to try to build the vmmon > module for > your system (you need to have a C compiler installed on your system)? > [yes] yes > > Using compiler "/usr/bin/gcc". Use environment variable CC to override. > > What is the location of the directory of C header files that match your > running > kernel? [/lib/modules/2.6.18-1.2798.fc6/build/include] > /lib/modules/2.6.18-1.2798.fc6/build/include > > Extracting the sources of the vmmon module. > > Building the vmmon module. > > Using 2.6.x kernel build system. > make: Entering directory `/tmp/vmware-config3/vmmon-only' > make -C /lib/modules/2.6.18-1.2798.fc6/build/include/.. SUBDIRS=$PWD > SRCROOT=$PWD/. modules > make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686' > CC [M] /tmp/vmware-config3/vmmon-only/linux/driver.o > CC [M] /tmp/vmware-config3/vmmon-only/linux/hostif.o > CC [M] /tmp/vmware-config3/vmmon-only/common/cpuid.o > CC [M] /tmp/vmware-config3/vmmon-only/common/hash.o > CC [M] /tmp/vmware-config3/vmmon-only/common/memtrack.o > CC [M] /tmp/vmware-config3/vmmon-only/common/phystrack.o > CC [M] /tmp/vmware-config3/vmmon-only/common/task.o > CC [M] /tmp/vmware-config3/vmmon-only/common/vmx86.o > CC [M] /tmp/vmware-config3/vmmon-only/vmcore/moduleloop.o > LD [M] /tmp/vmware-config3/vmmon-only/vmmon.o > Building modules, stage 2. > MODPOST > CC /tmp/vmware-config3/vmmon-only/vmmon.mod.o > LD [M] /tmp/vmware-config3/vmmon-only/vmmon.ko > make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686' > cp -f vmmon.ko ./../vmmon.o > make: Leaving directory `/tmp/vmware-config3/vmmon-only' > The module loads perfectly in the running kernel. > > This program previously created the file /dev/vmmon, and was about to > remove > it. Somebody else apparently did it already. > > This program previously created the file /dev/vmnet0, and was about to > remove > it. Somebody else apparently did it already. > > This program previously created the file /dev/vmnet1, and was about to > remove > it. Somebody else apparently did it already. > > This program previously created the file /dev/vmnet8, and was about to > remove > it. Somebody else apparently did it already. > > You have already setup networking. > > Would you like to skip networking setup and keep your old settings as > they are? > (yes/no) [yes] yes > > Extracting the sources of the vmnet module. > > Building the vmnet module. > > Using 2.6.x kernel build system. > make: Entering directory `/tmp/vmware-config3/vmnet-only' > make -C /lib/modules/2.6.18-1.2798.fc6/build/include/.. SUBDIRS=$PWD > SRCROOT=$PWD/. modules > make[1]: Entering directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686' > CC [M] /tmp/vmware-config3/vmnet-only/driver.o > CC [M] /tmp/vmware-config3/vmnet-only/hub.o > CC [M] /tmp/vmware-config3/vmnet-only/userif.o > CC [M] /tmp/vmware-config3/vmnet-only/netif.o > CC [M] /tmp/vmware-config3/vmnet-only/bridge.o > CC [M] /tmp/vmware-config3/vmnet-only/procfs.o > /tmp/vmware-config3/vmnet-only/procfs.c:33:26: error: linux/config.h: No > such file or directory > make[2]: *** [/tmp/vmware-config3/vmnet-only/procfs.o] Error 1 > make[1]: *** [_module_/tmp/vmware-config3/vmnet-only] Error 2 > make[1]: Leaving directory `/usr/src/kernels/2.6.18-1.2798.fc6-i686' > make: *** [vmnet.ko] Error 2 > make: Leaving directory `/tmp/vmware-config3/vmnet-only' > Unable to build the vmnet module. > > For more information on how to troubleshoot module-related problems, please > visit our Web site at > "http://www.vmware.com/download/modules/modules.html"; and > "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html";. > > Execution aborted. > > [root@jeffy bin]# > > Also, you say that I should install the i686 kernel, but I already have > that installed. What should I do now? Have you tried the vmware-any-any-update104 from http://ftp.cvut.cz/vmware/ ? Works for me. Paul.
