Bug ID 108487
Summary Wayland compositors are unable to use hardware acceleration on i915
Product Mesa
Version 18.2
Hardware Other
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component Drivers/DRI/i915
Assignee dri-devel@lists.freedesktop.org
Reporter magiblot@hotmail.com
QA Contact dri-devel@lists.freedesktop.org

Created attachment 142082 [details]
Error messages printed by weston when attempted to run from tty.

Hello,

On my i915 system (Intel Atom N455 + Intel GMA 3150), Wayland compositors are
unable to use hardware acceleration. I have tried KWin (KDE Plasma), Sway and
weston.

Sway uses llvmpipe software rendering. Plasma 5 showed an error message similar
to 'Could not initialize OpenGL' until version 5.13.0, when it began to fall
back on software rendering as well. weston justs reveals the error messages
'failed to create gbm surface' / 'Failed to init output gl state' nowadays with
its default configuration on Arch Linux x86_64.

Of course, there are no such issues on X11 sessions or when booting the same
installation of linux in another computer that's not i915.

Here is some relevant output from glxinfo on X11:

> Extended renderer info (GLX_MESA_query_renderer):
>     Vendor: Intel Open Source Technology Center (0x8086)
>     Device: Mesa DRI Intel(R) Pineview M  (0xa011)
>     Version: 18.2.2
>     Accelerated: yes
>     Video memory: 384MB
>     Unified memory: yes
>     Preferred profile: compat (0x2)
>     Max core profile version: 0.0
>     Max compat profile version: 1.4
>     Max GLES1 profile version: 1.1
>     Max GLES[23] profile version: 2.0
> OpenGL vendor string: Intel Open Source Technology Center
> OpenGL renderer string: Mesa DRI Intel(R) Pineview M 
> OpenGL version string: 2.1 Mesa 18.2.2
> OpenGL shading language version string: 1.20
> OpenGL ES profile version string: OpenGL ES 2.0 Mesa 18.2.2
> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16

I'm also attaching the entire startup log from weston which contains the error
messages I mentioned above.

I don't know if this is a bug or if it's a limitation of my hardware. In any
case, I thought it best to report the issue here. Please ask me for any further
information you need.

Thanks.


You are receiving this mail because: