openSUSE LEAP 16.0 on Raspberry Pi 4 B

Decided to buy Raspberry Pi 4 B (8GB RAM model) - primarily to test my openSUSE packages for aarch64 - already tested audacious - see https://src.opensuse.org/products/PackageHub/issues/2095

Enabling OpenGL

It is somehow disabled as default as we can found from glxinfo -B:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: llvmpipe (LLVM 19.1.7, 128 bits) (0xffffffff)
    Version: 24.3.3
    Accelerated: no
    Video memory: 7835MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.5
    Max compat profile version: 4.5
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

There are 2 indicators that it is disabled:

• llvmpipe - meaning that Mesa uses real CPU for rendering (not GPU)
• Accelerated: no

To enable OpenGL (called V3D) apply this change to your /boot/efi/config.txt:

-- boot/efi/orig/config.txt    2026-08-19 20:42:26.000000000 +0200
+++ boot/efi/config.txt 2026-08-19 21:31:24.000000000 +0200
@@ -78,7 +78,7 @@
 # can still use it through efifb by adding 'dtoverlay=disable-vc4' in
 # 'extraconfig.txt'.
 dtoverlay=vc4-kms-v3d-pi4,cma-default
-dtoverlay=disable-v3d
+#dtoverlay=disable-v3d
 
 [cm4]
 

And reboot. glxinfo -B should now change to:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Broadcom (0x14e4)
    Device: V3D 4.2.14.0 (0xffffffff)
    Version: 24.3.3
    Accelerated: yes
    Video memory: 7835MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 3.1
    Max compat profile version: 3.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL vendor string: Broadcom
OpenGL renderer string: V3D 4.2.14.0
OpenGL core profile version string: 3.1 Mesa 24.3.3
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)

Notice Accelerated: yes and Device: V3D (other than llvmpipe).

But there is a catch: this OpenGL acceleration has somehow limited memory:

• so far I'm able to play video up to around 1280x720
• but not fullscreen 1920x1080 - there will start following: error messages

  DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
  Failed to create scanout resource
  

• similar problem is for glxgears Mesa demo - when I enlarge Window too much it starts printing Allocation memory errors and flickers...
• this problem is not yet resolved

mpv with GPU acceleration

MPV video player by default uses SW rendering. I use GPU acceleration on both x86_64 and aarch64:

• create file ~/.config/mpv/mpv.conf with contents:

  vo=gpu
  save-position-on-quit
  

• later line Saves video position on exit (so it will resume from that position when mpv is run again.