Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Mesa3D / RPi4 - Failed to open bo 1: Permission denied
@ 2021-11-30  7:30 Michael Taubert
  2021-11-30  8:52 ` Peter Seiderer
  0 siblings, 1 reply; 3+ messages in thread
From: Michael Taubert @ 2021-11-30  7:30 UTC (permalink / raw)
  To: buildroot

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?

Thanks in advance.

Best regards,
Michael
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Buildroot] Mesa3D / RPi4 - Failed to open bo 1: Permission denied
  2021-11-30  7:30 [Buildroot] Mesa3D / RPi4 - Failed to open bo 1: Permission denied Michael Taubert
@ 2021-11-30  8:52 ` Peter Seiderer
  2021-11-30 13:56   ` Michael Taubert
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Seiderer @ 2021-11-30  8:52 UTC (permalink / raw)
  To: Michael Taubert; +Cc: buildroot

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Buildroot] Mesa3D / RPi4 - Failed to open bo 1: Permission denied
  2021-11-30  8:52 ` Peter Seiderer
@ 2021-11-30 13:56   ` Michael Taubert
  0 siblings, 0 replies; 3+ messages in thread
From: Michael Taubert @ 2021-11-30 13:56 UTC (permalink / raw)
  To: buildroot

Thanks Peter,

yes it addresses this issue. Unfortunately, the KMSRO driver option has 
been removed, so it may render this issue (further down) partly invalid now.

Your patch doesn't apply anymore either, and is partly rejected. I've 
put some thought into this, but it looks quite complicated with all 
these dependencies, which might break something somewhere else.

The easiest solution to make it work, at least on the RPi, seems to be 
to change

ifeq ($(BR2_PACKAGE_MESA3D_DRI_DRIVER),)

to

ifeq ($(BR2_PACKAGE_MESA3D_DRI_DRIVER)
    $(BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_V3D)
    $(BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VC4),)

That way it chooses to disable dri3 if none of the drivers is selected, 
which might take use of it.

According to https://bugs.buildroot.org/show_bug.cgi?id=13831 it might 
be a good idea to add the lima and panfrost driver too.

Well, I would consider this a short-term solution that people can get 
dri3 to work for their devices, without modifying mesa3d.mk. It doesn't 
solve the problem of a kind of broken logic in that matter.

To get this solved, someone with more insight should take a look at the 
logic and all the effects that a change might cause. Or, maybe this 
simple attempt is the solution already?

If there is anything I can provide to support a solution that will be 
merged into the repository, please, anybody let me know.

Best regards,
Michael

Am 11/30/21 um 9:52 AM schrieb Peter Seiderer:
> 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
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-11-30 13:57 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-11-30  7:30 [Buildroot] Mesa3D / RPi4 - Failed to open bo 1: Permission denied Michael Taubert
2021-11-30  8:52 ` Peter Seiderer
2021-11-30 13:56   ` Michael Taubert

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox