Re: Enable V3D on Raspberry Pi 4!
Thank you Diederik for your support.
I am actually a Fedora user, so I don't know more about Debian. But I
think they both are similar in kernel/linux as they use only
mainline/upstream kernel release.
After Fedora announced that, it is supported v3d/RPi4, I thought that
would work easily in Debian as well, so I tried adding lines from
Fedora/config.txt to Debian, specifically:
```
# Enable DRM VC4 V3D driver
# dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-v3d-pi4
dtoverlay=cma,cma-256
max_framebuffers=2
```
But no difference in terms of the issue with firefox and chromium.
I am glad to hear that 'no need to recompile kernel' from you. I wish
RPi4 get fully supported soon in Debian.
Regards,
Sally.
On Thu, 2023-01-19 at 20:00 +0100, Diederik de Haas wrote:
> On Thursday, 19 January 2023 19:02:58 CET Sally A.haj wrote:
> > Since the release of kernel 6.0.X, which has been announced the
> > enabling
> > of v3d to support hard acceleration in RPi4, I've tried
> > tested/daily
> > image from raspi.debian.net, the latest test, I installed Gnome,
> > and I
> > can see from Settings/About, that 'v3d' is the GPU driver. (I've
> > attach
> > the screenshot).
> >
> > That initial support is out of the box, after I asked in
> > #debian-raspberrypi on IRC, they have suggested me to follow the
> > link of
> > https://melissawen.github.io/blog/2022/11/10/v3d-in-the-mainline ;.
>
> We were led to believe that it was NOT working, hence the suggestion
> to try
> what Melissa Wen suggested would fix it.
> But your screenshot shows that it IS working \o/
>
> > I am not sure if recompiling the kernel is necessary, especially, I
> > am
> > getting some indicate that there is v3d, so I just added the
> > 'device_tree=bcm2711-rpi-4-b.dtb' to config.txt, but nothing has
> > been
> > changed.
>
> There no need to recompile the kernel and apparently the device_tree
> line is
> also not needed.
>
> > There are problems with firefox and chromium when launching them
> > and
> > window/maximizing/... .
>
> That is userland and AFAIK you need to set special settings to make
> that work
> and IIRC also in combination with Wayland. Which those are, I do not
> know.
>
> > DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
> > Failed to create scanout resource
>
> It *might* be that you need to increase the value for CMA memory.
> But I can be totally wrong on this.
>
> > Here when run "glxgears -info":
> >
> > $ glxgears -info
> >
> > 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 22.3.3
> > GL_VENDOR = Broadcom
>
> And this is the part which makes be conclude that everything is
> working.
> When V3D was not working, you'd see LLVMPIPE indicating software
> rendering.
>
> > Here when run glxinfo:
> >
> > $ glxinfo
> > name of display: :0
> > display: :0 screen: 0
> > direct rendering: Yes
> > server glx vendor string: SGI
> > server glx version string: 1.4
> > ....
> > Extended renderer info (GLX_MESA_query_renderer):
> > Vendor: Broadcom (0x14e4)
> > Device: V3D 4.2 (0xffffffff)
> > Version: 22.3.3
> > Accelerated: yes
>
> AFAIK this couldn't be more clearer to show V3D is working \o/
>
> > Video memory: 7800MB
> > Unified memory: yes
> > Preferred profile: compat (0x2)
> > Max core profile version: 0.0
> > Max compat profile version: 2.1
> > Max GLES1 profile version: 1.1
> > Max GLES[23] profile version: 3.1
> > OpenGL vendor string: Broadcom
> > OpenGL renderer string: V3D 4.2
> > OpenGL version string: 2.1 Mesa 22.3.3
> > OpenGL shading language version string: 1.20
> >
> > I wish debian to get the fully 3d supported as it's already in the
> > kernel.
>
> Apart from figuring out how to make userland software like browsers
> *also* make
> use of V3D/HW rendering, I don't know what you're missing.
> But making browsers fully utilise GPU rendering is something the user
> needs to
> do on their own devices with their own software.
>
> HTH,
> Diederik
Reply to: