[Bug 78453] [HAWAII] Get acceleration working

[bugzilla-daemon@freedesktop.org]

[-- Attachment #1.1: Type: text/plain, Size: 2829 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=78453

--- Comment #35 from Luzipher <luziphermcleod@yahoo.ie> ---
(In reply to comment #16)
> You need to build mesa with the "--with-egl-platforms=x11,drm" and
> "--enable-gallium-egl" flags, and then starts with "EGL_LOG_LEVEL=debug
> EGL_PLATFORM=drm ./es2_gears" command.

First sorry for not responding for so long, I've been out of town. Thanks for
the info, vincent, and thanks for picking up the tests where I stopped ! I
figured out that "--enable-gallium-egl" was missing, because the gentoo ebuild
only enables it, if the "openvg" is enabled as well. Is OpenVG really needed or
is it a bug in the ebuild ?

On the most recent deathsimple-kernel, mesa, libdrm and llvm from git, with
three monitors attached (2 dvi, 1 hdmi) I now get es2gears_screen trying to do
something with the following command:
    EGL_LOG_LEVEL=debug EGL_PLATFORM=drm es2gears_screen
On the HDMI screen I get instant corruption while on the DVI screens nothing
changes. Then the gpu reset cycles start (the screens only came back once).

Output of es2gears_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)
    Found 16 modes:
      0: 1920 x 1080
      1: 1920 x 1080
      2: 1920 x 1080
      3: 1920 x 1080
      4: 1920 x 1080
      5: 1920 x 1080
      6: 1920 x 1080
      7: 1920 x 1080
      8: 1920 x 1080
      9: 1920 x 1080
     10: 1920 x 1080
     11: 1280 x 720
     12: 1280 x 720
     13: 1280 x 720
     14: 720 x 576
     15: 720 x 480
    Will use screen size: 1920 x 1080
    vertex shader info:
    fragment shader info:
    info:

I retried with only one DVI monitor attached and got a white screen after a
short black blanking of about a second (instead of corruption) before the gpu
reset cycles started and I got multiple of those cycles. dmesg looks like
always.

I also tried egltri_screen and also got a white screen for a few seconds, then
it went back to console. No lockup, nothing in dmesg. Last line of output was:
    1 frames in 5.0 seconds =  0.200 FPS
I'm also able to re-run this multiple times with the same result, but I'm not
entirely sure if it uses radeon or maybe llvmpipe (eglinfo doesn't print
anything useful in this regard). Any idea how I could find out reliably ?


I also wondered why glxinfo, eglinfo and es2_info crash the gpu or at least
disable subsequent invocations of anything accelerated.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3698 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel