https://bugs.freedesktop.org/show_bug.cgi?id=32864 --- Comment #9 from Darxus <darxus at chaosreigns.com> 2011-01-08 12:52:11 PST --- The wayland compositor is now starting, but shows up as a completely garbled apparently random chunk of video memory. Output: $ ~/wayland/wayland/compositor/compositor libEGL debug: added /usr/lib/egl/egl_gallium.so to module array libEGL debug: added /usr/lib/egl/egl_dri2.so to module array libEGL debug: added /usr/lib/egl/egl_glx.so to module array libEGL debug: dlopen(/usr/lib/egl/egl_gallium.so) libEGL info: use DRM for display 0x5 libEGL debug: searching for pipe module nouveau libEGL debug: loaded /usr/lib/egl/pipe_nouveau.so libEGL debug: Failed to get KMS resources. Disable modeset. libEGL debug: the best driver is Gallium (score 100) libEGL debug: searching for st module GLESv2 libEGL debug: loaded /usr/lib/egl/st_GLESv2.so nv50_screen_get_param:162 - Unknown PIPE_CAP 11 XDG_RUNTIME_DIR not set, falling back to . using socket ./wayland-0 Mesa: User error: GL_INVALID_FRAMEBUFFER_OPERATION in glClear(incomplete framebuffer) Mesa git commit: 6a102074bb30e44273e999ee8cdd2afbfbc4e333 -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
