Re: VMware guest GL driver not loading

Brian Paul <[email protected]>
Newsgroups gmane.comp.video.mesa3d.user
Message-ID <[email protected]>
On 04/23/2017 06:34 PM, [email protected] wrote:
> Hi,
>
> I'm running VMWare Workstation 12 Pro, and attempting to get OpenGL 3.3
> up and running. I've followed the instructions listed here:
>
> https://www.mesa3d.org/vmware-guest.html
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__owa.exchange.mit.edu_owa_redir.aspx-3FSURL-3DLRWP-2Dmx9LYX8Oh4-2DyjobYX5xMNsismlgyA-5FcKtWGmzGt6zl0qYrUCGgAdAB0AHAAcwA6AC8ALwB3AHcAdwAuAG0AZQBzAGEAMwBkAC4AbwByAGcALwB2AG0AdwBhAHIAZQAtAGcAdQBlAHMAdAAuAGgAdABtAGwA-26URL-3Dhttps-253a-252f-252fwww.mesa3d.org-252fvmware-2Dguest.html&d=DwMDaQ&c=uilaK90D4TOVoH58JNXRgQ&r=Ie7_encNUsqxbSRbqbNgofw0ITcfE8JKfaUjIQhncGA&m=ZDX20-ms-XeyWy3rszqbEwCfrkcRYIHaPHDWQMJWQR8&s=cMloYFhV3AmWUouTOdtMg8Dm9T_Rj4DZnh1a2LLglzQ&e=>
>
> I
> copied|/lib/modules/{version}/extra/vmwgfx.ko|into|/lib/modules/{version}/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko|,
> since the final install step seems to throw them in the wrong spot.
>
> When I run dmesg, I see the following:
>
> [    1.364132] vmwgfx: module verification failed: signature and/or
> required key missing - tainting kernel
> [    1.377186] [vmwgfx] Initialized drm 1.1.0 20060810
> [    1.745804] [vmwgfx] Allocing minor.
> [    1.746035] [vmwgfx] Allocing minor.
> [    1.746063] [vmwgfx] Allocing minor.
> [    1.746434] [vmwgfx] DMA map mode: Using physical TTM page addresses.
> [    1.746496] [vmwgfx] Capabilities:
> [    1.746497] [vmwgfx]   Rect copy.
> [    1.746498] [vmwgfx]   Cursor.
> [    1.746498] [vmwgfx]   Cursor bypass.
> [    1.746499] [vmwgfx]   Cursor bypass 2.
> [    1.746499] [vmwgfx]   8bit emulation.
> [    1.746499] [vmwgfx]   Alpha cursor.
> [    1.746500] [vmwgfx]   3D.
> [    1.746500] [vmwgfx]   Extended Fifo.
> [    1.746501] [vmwgfx]   Multimon.
> [    1.746501] [vmwgfx]   Pitchlock.
> [    1.746501] [vmwgfx]   Irq mask.
> [    1.746502] [vmwgfx]   Display Topology.
> [    1.746502] [vmwgfx]   GMR.
> [    1.746503] [vmwgfx]   Traces.
> [    1.746503] [vmwgfx]   GMR2.
> [    1.746503] [vmwgfx]   Screen Object 2.
> [    1.746504] [vmwgfx]   Command Buffers.
> [    1.746504] [vmwgfx] Max GMR ids is 64
> [    1.746505] [vmwgfx] Max number of GMR pages is 196608
> [    1.746505] [vmwgfx] Max dedicated hypervisor surface memory is
> 786432 kiB
> [    1.746506] [vmwgfx] Maximum display memory size is 131072 kiB
> [    1.746507] [vmwgfx] VRAM at 0xe8000000 size is 131072 kiB
> [    1.746507] [vmwgfx] MMIO at 0xfe000000 size is 2048 kiB
> [    1.746509] [vmwgfx] global init.
> [    1.747480] [vmwgfx] Supports vblank timestamp caching Rev 2
> (21.10.2013).
> [    1.747481] [vmwgfx] No driver support for vblank timestamp query.
> [    1.747756] [vmwgfx] Screen Objects Display Unit initialized
> [    1.747801] [vmwgfx] width 640
> [    1.747809] [vmwgfx] height 480
> [    1.747817] [vmwgfx] bpp 32
> [    1.758502] [vmwgfx] Fifo max 0x00200000 min 0x00001000 cap 0x0000077f
> [    1.760448] [vmwgfx] Using command buffers with DMA pool.
> [    1.760461] [vmwgfx] DX: no.
> [    1.760461] [vmwgfx] Atomic: yes
> [    1.799117] [vmwgfx] Initialized vmwgfx 2.12.256 20170302 for
> 0000:00:0f.0 on minor 0
>
> Note the "DX:no." Not good. When running glxinfo, I see the following:
>
> MESA-LOADER: failed to retrieve device information
> libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/vmwgfx_dri.so
> libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so
> MESA-LOADER: failed to retrieve device information
> MESA-LOADER: failed to retrieve device information
>
> Any suggestions?

What is your guest OS?

What's the output of glxinfo in the guest?

It would help to see the vmware.log file from the VM.  If you send it to 
me I'll take a look.

-Brian

_______________________________________________
mesa-users mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.