Bug 95086 - black screen with cursor via weston-launch, vmwgfx from tty
Summary: black screen with cursor via weston-launch, vmwgfx from tty
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Wayland bug list
QA Contact:
Depends on:
Reported: 2016-04-23 15:11 UTC by Yong Bakos
Modified: 2018-06-08 23:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

weston log (7.56 KB, text/plain)
2016-04-23 15:11 UTC, Yong Bakos

Description Yong Bakos 2016-04-23 15:11:45 UTC
Created attachment 123185 [details]
weston log

Using VMWare Fusion 8.
Host: OSX 10.11.3 (15D21)
Guest: Ubuntu 16.04 (Unity) or Fedora 23 (Gnome 3)
Switch to tty3. (ctrl-alt-F3)
Start weston-launch.
Expected: See weston desktop shell.
Result: tty3 displays black screen with mouse cursor (arrow)

The log (attached) reports a permission denied error related to page flipping:
queueing pageflip failed: Permission denied

The console output also reports:
failed to bind extensions
failed to load driver: vmwgfx

I can run weston fine as the main display server / DE when I select Weston from the login manager. Weston also runs fine within the existing Unity/Gnome session as an X client, via weston.

During an earlier attempt at running weston-launch, the console reported the inability to find ~/Wayland/install/lib/dri/vmwgfx_dri.so, but still ran, resulting in the same "black screen with cursor behavior" and the same "permission denied" page flipping error. Appending "svga" to the --with-gallium-drivers option for mesa/autogen.sh results in make compiling successfully and creates vmwgfx_dri.so.

Built mesa with:
./autogen.sh --prefix=$WLD --enable-gles2 --disable-gallium-egl --with-egl-platforms=x11,wayland,drm --enable-gbm --enable-shared-glapi --with-gallium-drivers=r300,r600,swrast,nouveau,svga --with-dri-drivers=swrast

Despite the driver existing, I now see the aforementioned errors in the log and console output.
Comment 1 Yong Bakos 2016-04-23 15:23:40 UTC
I've just tried disabling hardware acceleration in VMWare Fusion, restarting the guest, and running weston-launch from a tty. In this scenario, the weston desktop shell appears, but there are two mouse cursors, and I cannot seem to control the "real" mouse cursor - it doesn't move, nor can I click on anything. Furthermore, the screen "flickers" as I move the mouse around. Depending on when I stop moving, the desktop shell is either visible, or I see a black screen.
Comment 2 Pekka Paalanen 2016-04-25 08:47:13 UTC
Your weston log is using drm-backend with gl-renderer, and says the GL implementation is "llvmpipe" which is a software renderer. I think that is not the vmwgfx Mesa driver ("svga"?). This also puts you on the Mesa-software-render-with-GBM-DRM-KMS path, which is probably rarely tested by anyone.

The mode set and page flip failures are related to the kernel driver, not the Mesa driver. Also the complain about insane delay seems to indicate the kernel driver is not properly handling timestamps, or maybe it's just fallout from the flip failures.

You should isolate and look at only one thing at a time:
- The kernel DRM driver / KMS support: run Weston with drm-backend and pixman-renderer. This avoid all the hassle with Mesa drivers.
- *If* you are interested in llvmpipe+KMS combination, then look into that after pixman renderer works fine.
- Finally try to get the Mesa vmware driver working.

Otherwise there are just too many combinations and moving things to figure out anything.
Comment 3 GitLab Migration User 2018-06-08 23:54:36 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/77.

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.