dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915
Date: Thu, 18 Oct 2018 17:51:08 +0000	[thread overview]
Message-ID: <bug-108487-502@http.bugs.freedesktop.org/> (raw)


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

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

            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
  --> https://bugs.freedesktop.org/attachment.cgi?id=142082&action=edit
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:
You are the assignee for the bug.

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

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

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

             reply	other threads:[~2018-10-18 17:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 17:51 bugzilla-daemon [this message]
2018-10-19 13:18 ` [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915: missing EGL_ANDROID_native_fence_sync extension bugzilla-daemon
2018-10-19 13:56 ` bugzilla-daemon
2018-10-19 14:02 ` bugzilla-daemon
2018-10-19 14:10 ` bugzilla-daemon
2018-10-19 17:00 ` bugzilla-daemon
2018-10-19 17:12 ` bugzilla-daemon
2018-10-29 10:56 ` [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915 bugzilla-daemon
2018-10-29 10:57 ` bugzilla-daemon
2018-12-04  6:46 ` bugzilla-daemon
2018-12-04  6:59 ` bugzilla-daemon
2018-12-04 11:13 ` bugzilla-daemon
2018-12-04 13:23 ` bugzilla-daemon
2018-12-05 19:47 ` bugzilla-daemon
2018-12-10  8:36 ` bugzilla-daemon
2019-01-31  3:02 ` bugzilla-daemon
2019-01-31 18:25 ` bugzilla-daemon
2019-03-09 14:18 ` bugzilla-daemon
2019-03-09 14:21 ` bugzilla-daemon
2019-04-27 23:33 ` bugzilla-daemon
2019-05-13  2:23 ` bugzilla-daemon
2019-05-16 14:14 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-108487-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).