Comment # 68
on bug 78453
from Luzipher
Created attachment 99906 [details] xorg and then glxinfo with kernel patch from attachment 99839 [details] [review] Sorry, I have to make another correction to my last post - mesa wasn't from git but from commit 58c659703bed86ea004a2e64ee231e3ba99b3d45. I can't get EGL to work with newest mesa, with the following messages when trying to run egltri_screen: # EGL_LOG_LEVEL="debug" EGL_PLATFORM="drm" ./egltri_screen libEGL debug: Native platform type: drm (environment overwrite) libEGL debug: EGL search path is /usr/lib64/egl libEGL debug: added /usr/lib64/egl/egl_gallium.so to module array libEGL debug: added egl_dri2 to module array libEGL debug: dlopen(/usr/lib64/egl/egl_gallium.so) libEGL info: use DRM for display (nil) libEGL debug: the best driver is Gallium EGL_VERSION = 1.4 (Gallium) libEGL debug: the value (0x0) of attribute 0x3040 did not meet the criteria (0x8) libEGL debug: the value (0x0) of attribute 0x3040 did not meet the criteria (0x8) libEGL debug: the value (0x0) of attribute 0x3040 did not meet the criteria (0x8) EGLUT: failed to choose a config I attached a dmesg with patch 99839 from Christian König but NOT patch 99594 from Alex Deucher, with newest mesa, where I did a "Xorg -retro" start and then glxinfo (which garbles the screen). I think there might be some new messages like: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C466 (len 254, WS 0, PS 4) @ 0xC490 [drm:atom_execute_table_locked] *ERROR* atombios stuck executing B9EC (len 145, WS 0, PS 8) @ 0xBA77 And: radeon 0000:02:00.0: still active bo inside vm Also glxgears still crashes and causes garbage, but it seems ore recoverable (Ctrl-C makes the gpu reset cycle quit sometimes) and it seems to believe to render more frames (messages like "3 frames in XXX sec" instead of "1 frame"). With older mesa egltri_screen still causes gpu resets and garbage.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
