Android-x86 4.4-r3 with VMware: no graphics

1,845 views
Skip to first unread message

brunofax

unread,
Aug 2, 2015, 7:23:28 PM8/2/15
to Android-x86
Previous version of Android-x86 worked well on vmware virtual machines (except apps needing OpenGL ES).

Now with 4.4-r3 the GUI does not start, I just get a command line prompt. I found the following in the log, don't know if it is relevant:

08-01 19:35:20.705 I/SurfaceFlinger( 4994): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
08-01 19:35:20.705 D/libEGL ( 4994): loaded /system/lib/egl/libGLES_mesa.so
08-01 19:35:20.706 W/GRALLOC-PIPE( 4994): failed to create pipe screen for vmwgfx
08-01 19:35:20.706 E/GRALLOC-DRM( 4994): unsupported driver: vmwgfx
08-01 19:35:20.706 W/EGL-GALLIUM( 4994): failed to create DRM screen
08-01 19:35:20.706 W/EGL-GALLIUM( 4994): will fall back to other EGL drivers if any
08-01 19:35:20.706 W/GRALLOC-PIPE( 4994): failed to create pipe screen for vmwgfx
08-01 19:35:20.706 E/GRALLOC-DRM( 4994): unsupported driver: vmwgfx
08-01 19:35:20.706 W/EGL-DRI2( 4994): fail to get drm fd
08-01 19:35:20.706 I/EGL-GALLIUM( 4994): using SW screen
08-01 19:35:20.706 W/GRALLOC-PIPE( 4994): failed to create pipe screen for vmwgfx
08-01 19:35:20.706 E/GRALLOC-DRM( 4994): unsupported driver: vmwgfx
08-01 19:35:20.706 W/GRALLOC-PIPE( 4994): failed to create pipe screen for vmwgfx
08-01 19:35:20.706 E/GRALLOC-DRM( 4994): unsupported driver: vmwgfx
08-01 19:35:20.706 E/hwcomposer( 4994): framebuffer_open failed (Invalid argument)
08-01 19:35:20.706 W/hwcomposer( 4994): getting VSYNC period from thin air: 16666666
08-01 19:35:20.706 D/hwcomposer( 4994): Intel hwcomposer module
08-01 19:35:20.706 E/SurfaceFlinger( 4994): ERROR: failed to open framebuffer (Invalid argument), aborting
08-01 19:35:20.706 F/libc ( 4994): Fatal signal 6 (SIGABRT) at 0x00001382 (code=-6), thread 4994 (surfaceflinger)


Is there anything I could try?

pstglia

unread,
Aug 2, 2015, 8:57:32 PM8/2/15
to Android-x86
Try enabling 3d acceleration on settings. vmwgfx driver requires it

brunofax

unread,
Aug 3, 2015, 12:44:40 AM8/3/15
to Android-x86
Thanks, this solved the problem: now the GUI starts.  And some applications needing OpenGL ES now work!!!

However I still have a problem:  the mouse pointer is not correctly positioned on the screen and when trying to approach the borders it jumps back in the middle... It's impossible to use the mouse.
I tried a couple of different screen resolution, with vga=nnn on the kernel grub line, but all seem to have this pointer problem.

pstglia

unread,
Aug 3, 2015, 8:00:02 AM8/3/15
to Android-x86
Mouse pointer is a known issue. Last time I tested using vmware player, there was not even a drawn cursor.

Suppose it is be related to something on drm gralloc... Have to investigate it

John Smyth

unread,
Aug 25, 2015, 10:32:18 PM8/25/15
to Android-x86
I've got a similar issue with 4.4-r3 + Vmware (3d acceleration enabled).
GUI does start, but it's really buggy. Most of what I see is a black screen.
I can see system buttons (most of the time), overlay effects (homescreen overscroll), search widgets and app menu. But if there's a popup window screen becomes black, no wallpapers, no cursor.
The interesting thing, that then i set, for example, a live wallpaper and quit selection menu, I can see it for a moment.
When I turned on cursor coordinates in a developers settings i couldn't see anything but top line with those coordinates.
So it might have something to do with alpha channel.

And also, the system completely ignores screen resolution and runs 800x600 only.

brunofax

unread,
Aug 28, 2015, 3:14:46 PM8/28/15
to Android-x86
I see the same problems with the GUI.   But screen resolution seems to work, I haven't tried many cases, but at least 800x600, 1024x768, 1280x1024 worked, both in 16 and 32 bit (for example vga=0x344 gives 1280x1024x32).
Reply all
Reply to author
Forward
0 new messages