From: Peter Seiderer <ps.report@gmx.net>
To: Michael Taubert <info@arachnodroid.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Mesa3D / RPi4 - Failed to open bo 1: Permission denied
Date: Tue, 30 Nov 2021 09:52:43 +0100 [thread overview]
Message-ID: <20211130095243.4e0d68dc@gmx.net> (raw)
In-Reply-To: <f3e486d3-af27-1c7c-7022-c2a733216a7f@arachnodroid.de>
Hello Michael,
On Tue, 30 Nov 2021 08:30:01 +0100, Michael Taubert <info@arachnodroid.de> wrote:
> Hi list!
>
> I've switched from branch 2021.02.x to 2021.08.x and got a problem with
> Mesa3D. Mesa3D does not build with DRI3 support by default, which leads
> into the error message 'Failed to open bo 1: Permission denied' when
> running glxgears -info.
>
> Earlier this year I already got caught by this problem, but could work
> around by enabling DRI SWRAST driver for Mesa3D. But this driver is not
> available anymore. The meson-log says, it's not built with DRI3:
>
> buildroot-rpi4/output/host/lib/pkgconfig -Dgallium-omx=disabled
> -Dpower8=disabled -Dllvm=disabled -Dgallium-opencl=disabled -Dglx=dri
> -Dgallium-xa=disabled -Dgallium-vc4-neon=auto -Dshared-glapi=enabled
> -Dgallium-drivers=v3d,vc4 -Dgallium-extra-hud=true -Ddri-drivers=
> -Ddri3=disabled ...
>
> This is the output of glxgears:
>
> root@buildroot:~# glxgears -info
> Failed to open bo 1: Permission denied
> Running synchronized to the vertical refresh. The framerate should be
> approximately the same as the monitor refresh rate.
> GL_RENDERER = V3D 4.2
> GL_VERSION = 2.1 Mesa 21.1.6
> GL_VENDOR = Broadcom
>
> It runs, but the screen stays black.
>
> When I change mesa3d.mk to this:
>
> ifeq ($(BR2_PACKAGE_MESA3D_DRI_DRIVER),)
> MESA3D_CONF_OPTS += \
> -Ddri-drivers= -Ddri3=enabled
> else
> ...
>
> It works again and the error disappears. How am I supposed to enable
> DRI3 support for my RPI4 now?
The problem is maybe addressed by the following patchset:
- [PATCH v1 1/2] package/mesa3d: add config option for DRI3 support (see [1])
- [PATCH v1 2/2] package/mesa3d: gallium/kmsro drivers require dri3 for X11 (see [2])
But did not find enough spare time/interest to do further work on this ones...
Regards,
Peter
[1] http://lists.busybox.net/pipermail/buildroot/2021-June/312614.html
[2] http://lists.busybox.net/pipermail/buildroot/2021-June/615147.html
>
> Thanks in advance.
>
> Best regards,
> Michael
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-30 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 7:30 [Buildroot] Mesa3D / RPi4 - Failed to open bo 1: Permission denied Michael Taubert
2021-11-30 8:52 ` Peter Seiderer [this message]
2021-11-30 13:56 ` Michael Taubert
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=20211130095243.4e0d68dc@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=info@arachnodroid.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.