Testing vmwgfx running under VMware in Linux

[Benedykt]

As far as I can advise, the authentic components consisting vmwgfx Gallium3D are: VMware winsys `, and` svga "driver. It seems that, EGL provide GLX (and OpenGL 2.1), although many of the things tracking state is particularly associated to vmwgfx. Vmwgfx is still underneath progress, nevertheless it is probable that the test today, and acquire some attractive consequences. By "attractive" I mean, is not completely functional, although definitely showing signs of progress.

[Badrunath]

Steps for testing:

1. Compiling a kernel 2.6.34 or 2.6.35 with CONFIG_DRM_VMWGFX = m
2. Libdrm compiles git
3. Compile table git
4. Modify xorg.conf to see incredible like this:
Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection
 Section "Files"
    ModulePath   "/usr/lib/xorg/modules"
    FontPath     "/usr/share/fonts/X11/misc"
    FontPath     "/usr/share/fonts/X11/cyrillic"
    FontPath     "/usr/share/fonts/X11/100dpi/:unscaled"
    FontPath     "/usr/share/fonts/X11/75dpi/:unscaled"
    FontPath     "/usr/share/fonts/X11/Type1"
    FontPath     "/usr/share/fonts/X11/100dpi"
    FontPath     "/usr/share/fonts/X11/75dpi"
    FontPath     "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
    FontPath     "built-ins"
EndSection
 Section "Module"
    Load  "glx"
    Load  "dbe"
    Load  "record"
    Load  "dri2"
    Load  "extmod"
    Load  "dri"
EndSection
 Section "InputDevice"
    Identifier  "Keyboard0"
    End Session

[MahaGuru]

I'm trying to vmwgfx under Gentoo; I have successfully compiled the latest development versions of the table and libdrm, both in the midst of support for VMware video card. I also installed a new X. Org X Server (1.8.2) and the essential driver’s xf86-video-vmware and I've managed to facilitate support for gallium to the table, glxinfo gives me the following result:

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4 
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on softpipe
OpenGL version string: 2.1 Mesa 7.9-devel
OpenGL shading language version string: 1.20

[Neutrals]

The first trouble is that says you are using the softpipe.
You must set the option 3DAccel (symmetric to the option 2DAccel) in xorg.conf. And make positive that / usr / lib / dri / vmwgfx_dri.so and / usr / lib / xorg / modules / drivers / vmwgfx_drv.so exist. If not, you set incredible incorrect throughout compilation.

[Bull50]

Fortunately I have no / usr / lib / xorg / modules / drivers / vmwgfx_drv.so were already attentive of that, nevertheless all my hard works were in vain, probing

[$tatic]

It is constructed from table / src / gallium / objectives / xorg-vmwgfx

[Gunilla]

This is output I am getting. After following above instructions.

The /var/log/Xorg.0.log confirms the driver being loaded:
 LoadModule: "vmwgfx"
Loading /usr/lib/xorg/modules/drivers/vmwgfx_drv.so
Module vmwgfx: vendor="X.Org Foundation"
compiled for 1.8.2, module version = 11.0.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 7.0vmwgfx: Driver for VMware SVGA device: VMware SVGA Device
vmwgfx(0): # Usefull debugging info follows #
vmwgfx(0): Using libkms backend
vmwgfx(0): 2D Acceleration is disabled
vmwgfx(0): Fallback debugging is disabled
vmwgfx(0): 3D Acceleration is disabled
vmwgfx(0): Swap Throttling is enabled.
vmwgfx(0): Dirty Throttling is disabled.

[CodGuru]

Well, approximately 2011, and vmwgfx still seems not capable to do appropriately with 3D acceleration enabled. If you position the alternative "3DAccel" "off" (default) in the xorg.conf, what it does is right, but not 3D, so you can also use versa.

If you position the selection "3DAccel" "on", you can give the impression of being forward to to have knowledge comparable to the `r300g 'driver, in view of the fact that it is also a driver of gallium. But unlike vmwgfx, r300g gets almost invariable maintenance and improvement of a variety of stakeholders, AMD and others. Unlike r300g, an mistake is quite understandable for months to set vmwgfx, and since the driver has no authorized website of the means of contact with developers, the mistake is likely to remain until someone at VMware decide to work on it.

[Ryszard]

Anybody had fortune with running GNOME 3

[void]

Actually, this driver has not worked at all for me since 2010! Used to work at least in part, although 3D speeding up now seems to be completely disabled, for the reason that all you can get is 2d + software rasterizer. I believe the holdup of vmwgfx going back possibly decided that it is a bad idea and stopped trying to develop it. Or maybe you have 25,000 lines of new-fangled code and bright sitting in the house who have not released yet. I really do not know.

But now, you will not get 3d acceleration with the Unit, Gnome 2, Gnome 3, or anything else with vmwgfx. Is disabled.

[Asclepius]

VMware, having expressly requested to turn off vmwgfx Ubuntu in their cores [LP # 606139] then asked to return CONFIG_DRM_VMWGFX = m-enabled. This application [LP # 698009] very recent addition to the core 3.0.0-9-13 dream.

Obviously vmwgfx is enabled already in Debian kernel 3.0.0-1, because I have two of them working with the same methods. No need to build a custom kernel. Other distributions do not know. This still seems to require a big effort to work, but at least not enough to build a custom kernel.

Git clone table, assemble table with 'scons xorg-dri-vmwgfx vmwgfx; Gallium3D copy the drivers you just build the places of the ordinary library search path X.