No 3D acceleration in Trusty - Gallium3D XA version too new

[Michael Schaller]

Hi everyone,

On Trusty I have no 3D acceleration under VMware Workstation 10.0.1 build 1379776.
Looking into /var/log/Xorg.0.log it looks like the Gallium3D XA version check fails:

[ 6.026] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 6.045] (II) vmware(0): Gallium3D XA version: 2.0.0.
[ 6.045] (WW) vmware(0): Expecting 1.0.x >= XA version < 2.0.0.
[ 6.045] (WW) vmware(0): No render acceleration available.
[ 6.046] (WW) vmware(0): Skipped initialization of direct rendering due to lack of render acceleration.
[ 6.046] (--) vmware(0): Render acceleration is disabled.
[ 6.046] (==) vmware(0): Rendercheck mode is disabled.
[ 6.046] (--) vmware(0): Direct rendering (3D) is disabled.
[ 6.046] (==) vmware(0): Backing store disabled
[ 6.046] (==) vmware(0): Silken mouse enabled
[ 6.046] (II) vmware(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 6.047] (==) vmware(0): DPMS enabled
[ 6.047] (II) vmware(0): No 3D acceleration. Not setting up textured video.

On the same host with a Saucy VM 3D acceleration works without issues.

Best,

Michael Schaller

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Michael Schaller (misch-9)]

I want to confirm that xserver-xorg-video-vmware (1:13.0.1.git.20140115.8da9817-0ubuntu1) from the trusty-proposed repo fixes the issue for me.

$ apt-cache policy xserver-xorg-video-vmware
xserver-xorg-video-vmware:
  Installed: 1:13.0.1.git.20140115.8da9817-0ubuntu1
  Candidate: 1:13.0.1.git.20140115.8da9817-0ubuntu1
  Version table:
 *** 1:13.0.1.git.20140115.8da9817-0ubuntu1 0
        400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:13.0.1.gita40cbd7-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on SVGA3D; build: RELEASE;
OpenGL version string: 2.1 Mesa 10.0.1

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes

[Michael Schaller (misch-9)]

Maarten, is there any reason why there is still no new package available in Trusty?
I see the new package with the fix only in trusty-proposed.

$ sudo apt-get update -qq && apt-cache policy xserver-xorg-video-vmware
xserver-xorg-video-vmware:
  Installed: 1:13.0.1.git.20140115.8da9817-0ubuntu1
  Candidate: 1:13.0.1.git.20140115.8da9817-0ubuntu1
  Version table:
 *** 1:13.0.1.git.20140115.8da9817-0ubuntu1 0
        400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:13.0.1.gita40cbd7-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

[Launchpad Janitor (janitor)]

This bug was fixed in the package xserver-xorg-video-vmware - 1:13.0.1.git.20140115.8da9817-0ubuntu1

---------------
xserver-xorg-video-vmware (1:13.0.1.git.20140115.8da9817-0ubuntu1) trusty; urgency=low

  * Sync fixes from git to make libxatracker2 work correctly. (LP: #1271186)
 -- Maarten Lankhorst <email address hidden> Tue, 21 Jan 2014 17:28:41 +0100

[Michael Schaller (misch-9)]

Maarten, thanks for fixing this issue.

$ sudo apt-get update -qq && apt-cache policy xserver-xorg-video-vmware
xserver-xorg-video-vmware:
  Installed: 1:13.0.1.git.20140115.8da9817-0ubuntu1
  Candidate: 1:13.0.1.git.20140115.8da9817-0ubuntu1
  Version table:
 *** 1:13.0.1.git.20140115.8da9817-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status

[Barry Warsaw (barry)]

I'm reopening this because with today's dist-upgrade, the problem has returned.

[Robert Hooker (sarvatt)]

Barry, can you please open up a new bug with ubuntu-bug xorg and assign Maarten instead of reopening this one? It shouldn't be the same bug and we need the logs that'll get attached to figure out whats going on.