Is there anyway to use meson_vdec on Manjaro for video playback?
yes if you use mpv --hwdec=auto --vo=gpu
you will get v4l2m2m-copy (using meson-vdec) and rendering with panfrost (If Iâm wrong someone correct me please).
For firefox for now there isnât any solution
Just for knowledge purpose, now that mesa-20.3.2-2 also enabled Panfrost on G52, what is the difference between mesa and mesa-git? Previously with mesa-20.2.6 it does not enable Panfrost on linux-vim 5.10.1-2
In arch and manjaro, if any pkg have git in its name then it means that the pkg is built against the git source and just for information to normal users git source is updated on daily/regular basis depending on the new development.
While pkg without git are built against the last stable release according to the version number mentioned in the pkg.
So the current example can be mesa-git have open gl 3 enabled while it will be available in further stable version but not available in the current stable version as it is in the developement cycle.
I hope you understand the developement cycle if the source code and then pkging cycle of git and non-git pkgs with this explanation.
Thanks for the clarification between mesa and mesa-git. Learning everyday. Good to know mesa-git now have open-gl 3 support.
Not sure others had notice this on Chromium 87, with linux-vim 5.10.1-2 and linux 5.9.y with mesa-20.2.3 or 20.2.6, Chromium 87 default to Hardware Acceleration Enabled and Youtube video had high dropped frames even at 480p/30 and high CPU resource usage! Web pages with video advertisements will (small windows ads) causes very high CPU resources usage (all 6-Cores in the 70%-90%). Changing the settings to âDisabledâ hw accelerating using âchrome://flagsâ and re-launch Chromium 87 have NO effect on the defeating the hw acceleration as âchrome://gpuâ sitill indicates hw acceleration âEnabledâ. I notice this also in other distros Debian/Ubuntu Legacy-Arm and also in Armbian.
With the latest Manjaro-ARM-VIM3-XFCE- linux-5.10.5-3 and mesa-20.3.2-2, Chromium 87, it seems to default to hw acceleration âDisabled/Defaultâ either due to my earlier âdisablingâ it when in kernel linux-vim 5.10.1-2 and mesa-20.2.6 or linux-5.10.5-3 with mesa-20.3.2-2 have a different Chromium 87 start-up settings (do not know where to locate it in Manjaro). Now with hw acceleration settings âDisabledâ with the mesa-20.3.2-2, Youtube video of 720p/60 and 1080p/30 on Chromium 87 have low dropped frames still not as good as on Firefox 84.
Edit: Noticed Chromium âchrome://gpuâ reports two different Graphics Feature Status and Graphics Feature Status For Hardware GPU with different Status.
### Graphics Feature Status
* Canvas: Software only, hardware acceleration unavailable
* Compositing: Software only. Hardware acceleration disabled
* Multiple Raster Threads: Enabled
* Out-of-process Rasterization: Disabled
* OpenGL: Disabled
* Hardware Protected Video Decode: Disabled
* Rasterization: Software only. Hardware acceleration disabled
* Skia Renderer: Enabled
* Video Decode: Software only. Hardware acceleration disabled
* Vulkan: Disabled
* WebGL: Software only, hardware acceleration unavailable
* WebGL2: Software only, hardware acceleration unavailable
### Problems Detected
* Gpu compositing has been disabled, either via blocklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable.
*Disabled Features: gpu_compositing*
### Graphics Feature Status for Hardware GPU
* Canvas: Hardware accelerated
* Compositing: Software only. Hardware acceleration disabled
* Multiple Raster Threads: Enabled
* Out-of-process Rasterization: Disabled
* OpenGL: Enabled
* Hardware Protected Video Decode: Hardware accelerated
* Rasterization: Hardware accelerated on all pages
* Skia Renderer: Enabled
* Video Decode: Hardware accelerated
* Vulkan: Disabled
* WebGL: Hardware accelerated but at reduced performance
* WebGL2: Hardware accelerated but at reduced performanceTrying to understand what libva and libva-mesa-driver does in Manjaro-ARM. So far, I understand from Chromium, Firefox and MPV all seems to use libva for hw acceleration but from what I noticed in Chromium, Firefox and MPV all reported âlibvaâ error (so basically the âlibvaâ driver in Manjaro-ARM is not what these three applications are expecting or can work with. None highlighted anything relating to libva-mesa-driver.
From the limited info I gathered from web search, libva is for vaapi acceleration but somehow it with mesa-20.3.2-2 these libva-2.10.0-0.1 and libva-mesa-driver-20.3.2-2 doesnât seem to be functioning? Just would like to understand further into how Linux-Arm or Manjaro-Arm works especially in relation to hw acceleration. Have read Hardware video acceleration - ArchWiki but this article mainly explain/address X86 devices.
todayâs update xfwm4-4.14.6.1-1 fixed the issue with compositor
glxgears with compositor fullscreen 59.8 FPS
glxgears -fullscreen compositor disable 59.7-59.8 FPS
with manjaro mesa-git and kernel linux-vim 5.10.1-1 x96 air S905X3
Edit 1
XFCE enabled compositor glmark2 Score 55
XFCE disable compositor glmark2 Score 54
Edit 2 incorrect benchmark
XFCE enabled compositor glmark2-es2 Score 108
XFCE disable compositor glmark2 -es2 Score 193
I couldnât make glmark2-es2-wayland working in gnome it says command not found
gnome glmark2 -es2 Score is 146
âSo now compositor disable doesnât do so much differenceâ, compositor does a lot of difference
Using XFCE Stable Branch but with linux-5.10.5-3 and mesa-git-132971, similar results on glxgears but only when CPU Governor on âPerformanceâ when CPU Governor on âSchedutilâ glxgears performance dropped which is a bit surprise and I thought GPU is doing the rendering of the âglxgearsâ with Panfrost.
With Manjaro glmark2-201403-3
glimark2-es2 score G52: 69 (standard window).still very low. (libpng warning: iCCP: known incorrect sRGB profile)
I can confirm a score of 189 (single run) with these settings on my X96Max+ (S905X3, Mali G31).
And here are the results for glmark2-es2-wayland using sway: 
[themojoman@X96MaxPlus ~]$ glmark2-es2-wayland
=======================================================
glmark2 2020.04
=======================================================
OpenGL Information
GL_VENDOR: Panfrost
GL_RENDERER: Mali G31 (Panfrost)
GL_VERSION: OpenGL ES 2.0 Mesa 21.0.0-devel (git-0b910cc019)
=======================================================
[build] use-vbo=false: FPS: 191 FrameTime: 5.236 ms
[build] use-vbo=true: FPS: 196 FrameTime: 5.102 ms
[texture] texture-filter=nearest: FPS: 476 FrameTime: 2.101 ms
[texture] texture-filter=linear: FPS: 463 FrameTime: 2.160 ms
[texture] texture-filter=mipmap: FPS: 476 FrameTime: 2.101 ms
[shading] shading=gouraud: FPS: 122 FrameTime: 8.197 ms
[shading] shading=blinn-phong-inf: FPS: 124 FrameTime: 8.065 ms
[shading] shading=phong: FPS: 112 FrameTime: 8.929 ms
[shading] shading=cel: FPS: 110 FrameTime: 9.091 ms
[bump] bump-render=high-poly: FPS: 55 FrameTime: 18.182 ms
[bump] bump-render=normals: FPS: 493 FrameTime: 2.028 ms
[bump] bump-render=height: FPS: 446 FrameTime: 2.242 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 232 FrameTime: 4.310 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 89 FrameTime: 11.236 ms
[pulsar] light=false:quads=5:texture=false: FPS: 379 FrameTime: 2.639 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 58 FrameTime: 17.241 ms
[desktop] effect=shadow:windows=4: FPS: 303 FrameTime: 3.300 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 32 FrameTime: 31.250 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 34 FrameTime: 29.412 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 47 FrameTime: 21.277 ms
[ideas] speed=duration: FPS: 110 FrameTime: 9.091 ms
[jellyfish] <default>: FPS: 129 FrameTime: 7.752 ms
[terrain] <default>: FPS: 7 FrameTime: 142.857 ms
[shadow] <default>: FPS: 92 FrameTime: 10.870 ms
[refract] <default>: FPS: 14 FrameTime: 71.429 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 456 FrameTime: 2.193 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 233 FrameTime: 4.292 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 436 FrameTime: 2.294 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 351 FrameTime: 2.849 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 228 FrameTime: 4.386 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 333 FrameTime: 3.003 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 334 FrameTime: 2.994 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 190 FrameTime: 5.263 ms
=======================================================
glmark2 Score: 222
=======================================================
1 Like
Found why I couldnât run glmark2-es2-wayland (glmark2 package from the manjaro is old and doesnât have glmark2-es2-wayland). Installed a new version an now I have
Gnome glmark2-es2-wayland Score big surprise
[pedro@sala ~]$ glmark2-es2-wayland
glmark2 2020.04
=======================================================
OpenGL Information
GL_VENDOR: Panfrost
GL_RENDERER: Mali G31 (Panfrost)
GL_VERSION: OpenGL ES 2.0 Mesa 21.0.0-devel (git-a0314083be)
[build] use-vbo=false: FPS: 229 FrameTime: 4.367 ms
[build] use-vbo=true: FPS: 253 FrameTime: 3.953 ms
[texture] texture-filter=nearest: FPS: 835 FrameTime: 1.198 ms
[texture] texture-filter=linear: FPS: 840 FrameTime: 1.190 ms
[texture] texture-filter=mipmap: FPS: 855 FrameTime: 1.170 ms
[shading] shading=gouraud: FPS: 153 FrameTime: 6.536 ms
[shading] shading=blinn-phong-inf: FPS: 154 FrameTime: 6.494 ms
[shading] shading=phong: FPS: 139 FrameTime: 7.194 ms
[shading] shading=cel: FPS: 135 FrameTime: 7.407 ms
[bump] bump-render=high-poly: FPS: 58 FrameTime: 17.241 ms
[bump] bump-render=normals: FPS: 635 FrameTime: 1.575 ms
[bump] bump-render=height: FPS: 554 FrameTime: 1.805 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 240 FrameTime: 4.167 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 83 FrameTime: 12.048 ms
[pulsar] light=false:quads=5:texture=false: FPS: 861 FrameTime: 1.161 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 67 FrameTime: 14.925 ms
[desktop] effect=shadow:windows=4: FPS: 420 FrameTime: 2.381 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 49 FrameTime: 20.408 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 48 FrameTime: 20.833 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 59 FrameTime: 16.949 ms
[ideas] speed=duration: FPS: 140 FrameTime: 7.143 ms
[jellyfish] : FPS: 164 FrameTime: 6.098 ms
[terrain] : FPS: 8 FrameTime: 125.000 ms
[shadow] : FPS: 111 FrameTime: 9.009 ms
[refract] : FPS: 15 FrameTime: 66.667 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 553 FrameTime: 1.808 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 286 FrameTime: 3.497 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 532 FrameTime: 1.880 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 427 FrameTime: 2.342 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 277 FrameTime: 3.610 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 409 FrameTime: 2.445 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 409 FrameTime: 2.445 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 233 FrameTime: 4.292 ms
glmark2 Score: 310
=======================================================
Why the text is so big?
But is impressive the difference of gnome wayland
Impressive. In Gnome-Wayland or Sway-Wayland do you have much of the Panfrost visual glitches?
For now, no glitches in gnome-wayland
Indeed, very impressive!
For testing I installed gnome package as well, logged into gnome and ran glmark2-es2 which resulted in a score of only 134.
Then I tried to run glmark2-es2-wayland which threw an error (âCould not initialise canvasâ).
Were from did you download the package for the new version? Or did you compile the github source files by yourself?
Don tell @spikerguy (from here archlinuxdroid : /archlinuxdroid/aarch64/) the one I had from the manjaro repo is from 2014 and didnât had the glmark2-es2-wayland and I didnât want to compile it myself (but yours has the same date of the one of the repo).
Your first result is consistent with mine, this is xwayland result not wayland (and not bad for xwayland)
Be sure that you enable panfrost in wayland sudo sh -c âecho âPAN_MESA_DEBUG=bifrostâ >> /etc/environmentâ
And be sure to be in wayland ( The âWaylandEnable=Falseâ setting in /etc/gdm/custom.conf is commented out), if you are using GDM
Thanks - using GDM (instead of LightDM) did the trick!
(Now I score 306 - 308 when running glmark2-es2-wayland.)
Actually, I did not use this for months since Panfrost runs out of the box with XFCE and sway (when mesa package is installed). I also tested it for gnome and it is also NOT needed anymore.
Even worse: When I add PAN_MESA_DEBUG=bifrost to /etc/environment I cannot log in to XFCE anymore.
Got mine from archlinuxdroid repo as well which explains why I had glmark2-es2-wayland already installed.
Anyone with G52 box getting similar or better results? Are you all able to get similar results in XFCE and/or in KDE? I am on XFCE and mesa-git but the glmark2-es2 (glmark2-git) score is way lower. Is it due to settings or Panfrost support for G52?
I am on Xcfe without compositor, LINUX-VIM-5.10.1-2 and mesa-git. Glmark-es2 gives me 222 with the oldest box of the thread (G31). I think is just driver support and in the future G52 will win for sure.
After being able to log in to XFCE once using GDM I failed to do so after I used gnome (wayland), logged out and then tried to log in to XFCE.
So, I switched to using SDDM and this one correctly loads Gnome (wayland) and XFCE.
EDIT: Following this tutorial How to: Wayland with LightDM I can now also log in to Gnome Wayland.
Today I tried LibreELEC-AMLGX.arm-9.80.8-box.img that is a build of GitHub - chewitt/linux at amlogic-5.11.y that uses kernel 5.11 rc3
Apart for the old problem green screen that was solved using u-boot.ext method, sound was working and Ethernet. The screen was correct, there wasnât any offset. I used the meson-sm1-x96-air-4g.dtb that was in the image.
After I tried the same dtb wit kernel 5.11 rc2 that is in the manjaro repo (unstable) but I couldnât boot.
So libreelec has a lot of patches, drivers and firmware that arenât in mainline kernel.
1 Like