Bug 864 - VMware driver no longer works
Summary: VMware driver no longer works
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/VMWare (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high blocker
Assignee: Xorg Project Team
QA Contact:
Depends on:
Reported: 2004-07-13 10:12 UTC by Roland Mainz
Modified: 2004-09-03 01:25 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description Roland Mainz 2004-07-13 10:12:18 UTC
2004-07-13-trunk, the VMware driver in "trunk" refuses to work like this:
-- snip --
# X :0

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted
to fixes@XFree86.Org.  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository

XFree86 Version (4.4.0 RC 2)
Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: SuSE Linux [ELF] SuSE
Current Operating System: Linux suse91xorgtest 2.6.5-7.75-default #1 Mon Jun 14
10:44:37 UTC 2004 i686
Build Date: 06 April 2004
Changelog Date: 29 February 2004
        Before reporting problems, check http://www.XFree86.Org/
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Tue Jul 13 19:05:35 2004
(==) Using config file: "/etc/X11/XF86Config"

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to http://www.suse.de/feedback.

-- snip --
Comment 1 Roland Mainz 2004-07-13 10:18:30 UTC
More info:
- VMware version is 4.5.2 build 8848 with VMware tools installed (disabling or
deinstaling them does not cure the problem)
Comment 2 Nolan Leake 2004-07-22 16:07:08 UTC
Without the tools, it works for me with an X.org trunk build on FC2 from around
20 July in both depth 24 and 16 (my host is in 16).  So X.org works fine.

Installing the 4.2.x compiled vmmouse_drv from the tools causes the sigsegv. 
The vmmouse driver is not yet part of X.org or XFree86's tree, but is installed
by our tools.

This is a VMware tools bug.
Comment 3 Nolan Leake 2004-08-27 13:14:26 UTC
We (VMware) have fixed this bug internally.

For users of released products, a workaround is to change:
Driver   "vmmouse"
Driver   "mouse"
in your xorg.conf.
Comment 4 Roland Mainz 2004-09-03 18:25:35 UTC
Nolan Leake wrote:
> We (VMware) have fixed this bug internally.
> For users of released products, a workaround is to change:
> Driver   "vmmouse"
> to:
> Driver   "mouse"
> in your xorg.conf.

I have good news and bad news...

First the bad news:
The workaround doesn't work.

And the good news:
The workaround works if the VMware guest OS has been restarted... :)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.