VMware Workstation Problems with new Fedora Core 2 Kernal Update..

Elite_Gamer04 · 06-23-2004, 08:08 AM

Hi,

Just finished updating FC2 to its new kernal and went to run VMware Workstation and it came up with a Error Box saying I have to re-configure VMware before using it on the new kernal, So I typed "vmware-config.pl" as root and followed the instructions and got the follow error:

Quote:

[root@localhost *]# vmware-config.pl
Making sure VMware Workstation's services are stopped.

Stopping VMware services:
Virtual machine monitor [ OK ]
Bridged networking on /dev/vmnet0 [ OK ]
DHCP server on /dev/vmnet8 [ OK ]
NAT service on /dev/vmnet8 [ OK ]
Host-only networking on /dev/vmnet8 [ OK ]
Virtual ethernet [ OK ]

Trying to find a suitable vmmon module for your running kernel.

None of VMware Workstation's pre-built vmmon modules 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.6-1.435/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-config1/vmmon-only'
make -C /lib/modules/2.6.6-1.435/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
make[1]: Entering directory `/lib/modules/2.6.6-1.435/build'
CC [M] /tmp/vmware-config1/vmmon-only/linux/driver.o
/tmp/vmware-config1/vmmon-only/linux/driver.c:131: warning: initialization from incompatible pointer type
/tmp/vmware-config1/vmmon-only/linux/driver.c:135: warning: initialization from incompatible pointer type
CC [M] /tmp/vmware-config1/vmmon-only/linux/hostif.o
/tmp/vmware-config1/vmmon-only/linux/hostif.c: In function `HostIF_FreeLockedPages':
/tmp/vmware-config1/vmmon-only/linux/hostif.c:738: error: structure has no member named `count'
/tmp/vmware-config1/vmmon-only/linux/hostif.c:740: error: structure has no member named `count'
make[2]: *** [/tmp/vmware-config1/vmmon-only/linux/hostif.o] Error 1
make[1]: *** [_module_/tmp/vmware-config1/vmmon-only] Error 2
make[1]: Leaving directory `/lib/modules/2.6.6-1.435/build'
make: *** [vmmon.ko] Error 2
make: Leaving directory `/tmp/vmware-config1/vmmon-only'
Unable to build the vmmon 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.

Whats going on someone please help?

eespenh · 06-23-2004, 08:51 AM

This error was fixed in the newest VMware version (4.5.2, build 8848 is current, I think).

It's mentioned in another thread, but I thought I'd repeat it, since it worked flawlessly
for me. (Apart from the display behaving a little strange at times now.)

Espen

Elite_Gamer04 · 07-01-2004, 10:27 PM

Thanks all updated and working but can someone answer me this:

Why can't I get my Full Screen mode to work? I keep recivceing an error saying "Undable to turn on direct Graphics. Failed to switch to Full Screen SVGA mode"... Im using Fedora Core 2 and I'd really like the full screen mode to work

Anyone?

MHouse · 07-14-2004, 11:18 PM

Check your monitor color depth. What is on your desktop should match what is configured on your X server. I've heard of problems with that but can't confirm, myself.

OrinocoRedhat · 07-17-2004, 08:52 PM

I have the same exact issue, Fedora Core 2, with Vmware 4, cannot go to full screen. Same exact depth, either 16 in guest and 16 on host, and tried 32 on host and 32 on guest. Same exact error message as you stated before. Why can't this go full-screen? I had this exact version of vmware working with Redhat 9, same identical laptop!!

Any other suggestions?

Why can't I get my Full Screen mode to work? I keep recivceing an error saying "Undable to turn on direct Graphics. Failed to switch to Full Screen SVGA mode"... Im using Fedora Core 2 and I'd really like the full screen mode to work

MHouse · 07-19-2004, 02:52 PM

I ended up editing my xorg and my XFree86 configuration files and forced the VM to run at the same resolution as Windows does. Then when I started up my Virtual Machine and X was running, I was able to switch to full-screen.

OrinocoRedhat · 07-19-2004, 05:52 PM

I already modified my xorg file, but you think that I need to change additional Xfree config files? I am running at 32bit depth on the xorg file and on the WinXP vm, but still I cannot go full-screen.

- Ryan

MHouse · 07-19-2004, 06:10 PM

Quote:

Originally posted by OrinocoRedhat
I already modified my xorg file, but you think that I need to change additional Xfree config files? I am running at 32bit depth on the xorg file and on the WinXP vm, but still I cannot go full-screen.

- Ryan

Not sure. Can only tell you what I did. Sorry, I'm a n00b.

The biggest thing for me was changing the screen resolution, and not the color depth. When I set my default resolution to 1280x1024 in order to match what Windows was running at, I had no issues running fullscreen.

OrinocoRedhat · 07-19-2004, 06:58 PM

Actually, I got the color depth to be the same as well as the screen resolution. Still does not go to to full screen. Are you running Fedora Core 2 as well? With vmware 4.0.5 or the new 4.5??

MHouse · 07-20-2004, 12:40 PM

Hmmm.... Running Fedora Core 2 on VMWare 4.5.2 build 8848 with the OS option set to Linux Other (2.6.x Kernel).

OrinocoRedhat · 07-20-2004, 05:10 PM

Vmware 4.0.5, kernel 2.4.20-8 with Fedora Core 2 is my setup.

vmware 4.5.2 supports kernels 2.6.x

vmware 4.0.5 works with the 2.4.x kernels and NOT the 2.6.x kernels

This means that my current setup should not conflict.

What else can I do to fix this?

What I am thinking is that 4.0.5 really likes to look for the old XF86Config and XF86Config-4 files for some reason, and since Fedora Core 2 is using xorg instead, perhaps this is why??? Can I create one of these again to make 4.0.5 like me thus going FULL-SCREEN??

MHouse · 07-20-2004, 05:23 PM

I would probably try the newer VMWare first. If you have 4.0.5, you are automatically entitled to 4.5.2 I think. The update seems to be relatively painless as compared to going from 3.x to 4.x.

BTW, how are you running the 2.4 kernel with Fedora Core 2? I thought that FC2 came with the 2.6 kernel??? Sorry, told you I was a n00b...

OrinocoRedhat · 07-20-2004, 05:32 PM

Well,

I am running 2.4.20-8 because, even though I got 2.6.7 (latest kernel) recompiled and configured completely, it did not allow me to use my Epson Photo 2400 scanner with the libusb thing as something got kind of screwed up, so I had to go back to a kernel old enough that had the "scanner.o" module for me to use which as soon as I got that configured, my scanner was found, and all was well in the world again. I als o have an Epson Stylus Photo 2200 printer which is also a USB/ Firewire printer.