Bug 688 - Unable to run OpenGL applications in qemux86 images
Summary: Unable to run OpenGL applications in qemux86 images
Status: RESOLVED FIXED
Alias: None
Product: System Startup
Classification: Runtime
Component: system-startup (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.0 M4
Assignee: Edwin Zhai
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-01-31 09:48 UTC by Joshua Lock - Disabled
Modified: 2011-04-18 10:58 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Lock - Disabled 2011-01-31 09:48:55 UTC
root@qemux86:~# glxgears 
go on...
You maybe forgot to launch QEMU with -enable-gl argument.
Trying TCP/IP communication instead
impossible to connect to server: Connection refused

AFAIK we *do* boot with -enable-gl....

Note for bug investigation glxgears comes from libgl-xprogs
Comment 1 Edwin Zhai 2011-02-23 16:55:51 UTC
Josh,
I assume we can still run opengl applications without -enable-gl, but the speed is slow.

Can you see the gears running slowly, or it just failed?

Although Jeff and I didn't test GL after upgrading qemu, I remember one hacked GL library is needed to trigger the GL path. Did you do it?

Thanks,
edwin
Comment 2 Kevin Tian 2011-02-23 17:00:15 UTC
you can use glxinfo to see whether sw mesa is used
Comment 3 Paul Eggleton 2011-03-03 08:15:16 UTC
I haven't worked out quite what's going wrong, but I can say that this bug occurs if you add a gl-using application into your image e.g. by adding mesa-demos to IMAGE_EXTRA_INSTALL; however if you simply install libgl1 and mesa-demos after the fact it works fine (albeit a little slowly). glxinfo in the failing image reports the same error as glxgears above, whereas in the working image it reports the following:

root@qemux86:~# export DISPLAY=0:0
root@qemux86:~# glxinfo 
name of display: 0:0.0
display: 0:0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, 
    GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, 
    GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_MESA_copy_sub_buffer, GLX_INTEL_swap_event
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
    GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, 
    GLX_INTEL_swap_event
GLX version: 1.4
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_OML_swap_method, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_INTEL_swap_event
OpenGL vendor string: Mesa Project
OpenGL renderer string: Software Rasterizer
OpenGL version string: 2.1 Mesa 7.10.1-devel
OpenGL shading language version string: 1.20
... (further details omitted)

I still have both images around on my machine if you need further diagnostic information.