Unfortunally, I don't have much more to report than I'm seing performance issues under Wayland/Sway. Starting the compositor, spawning a terminal, operating in the terminal, all these actions are significantly (usually a couple of seconds) delayed. No crashes occur and nothing is brought up in dmesg.
Mesa was compiled by portage from firstname.lastname@example.org with:
meson --buildtype plain --wrap-mode nodownload -Dplatforms=surfaceless,wayland,drm -Dllvm=false -Dlmsensors=false -Dlibunwind=false -Dgallium-nine=false -Dgallium-va=false -Dgallium-vdpau=false -Dgallium-xa=false -Dgallium-xvmc=false -Dgallium-opencl=disabled -Dosmesa=none -Dbuild-tests=false -Dglx=disabled -Dshared-glapi=true -Ddri3=true -Degl=true
-Dgbm=true -Dgles1=false -Dgles2=true -Dglvnd=false -Dselinux=false -Dvalgrind=false -Ddri-drivers= -Dgallium-drivers=iris,swrast -Dvulkan-drivers=intel -Dvulkan-overlay-layer=false --buildtype plain -Db_ndebug=true
Just as a first thought, this sounds very much like how the experience is when one runs gnome-shell with a software rasterizer. Is there some log output from sway that would prove it is HW accelerated? You could use strace to see which dri module it opens (iris_dri.so, not swrast_dri.so) or for example gdb the process and set break to iris_draw_vbo that should get called on each draw.
True, everything points to SW being used. I will attach output of sway and strace. I had to run it as root, because strace would't get the correct caps, so sway terminates prematurely, but late enough to get to the point.
Created attachment 145268 [details]
Strace as root
There is new evidence, suggesting that with MESA_LOADER_DRIVER_OVERRIDE=iris the driver is actually loaded, but only if run by root (as seen in the attached files). If run as non-root, however, mesa attempts (and fails) to load i965 rather than iris. There might be a permission/caps problem.
Created attachment 145269 [details]
Sway log as root
(In reply to Cedric Sodhi from comment #3)
> Created attachment 145268 [details]
> Strace as root
> There is new evidence, suggesting that with MESA_LOADER_DRIVER_OVERRIDE=iris
> the driver is actually loaded, but only if run by root (as seen in the
> attached files). If run as non-root, however, mesa attempts (and fails) to
> load i965 rather than iris. There might be a permission/caps problem.
Oh that is strange :/ Maybe try installing iris as regular user (as example under /home/user/iris, just use --prefix= with meson), then use LD_LIBRARY_PATH so that sway finds it there?
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1362.