I downloaded the Vulkan Examples that has the Vulkan Gears app. And after a download and build process yielding a project size of 2.2GB, I have the app.
And it reports ~130 fps… and the app is 1.7MB in size. 
Edit: Running Vulkan Gears on Plasma on X11, it reports ~264 fps!
I built kodi 19 packages today that I want you to test but I am
going to sleep right now.
My test video playing HEVC with HW decoding on 64bit with kodi 19.
Tried the same thing got everything up and running, but the system had way too many crashes. I can confirm that vulkan radically improves, browsing, responsiveness and video playback (tried Youtube) in chromium. Enabling the settings given by Darksky in Firefox dramatically improves overall responsiveness, snappines… But video playback is a mess (at least in Youtube).
Ran everything from an SSD on KDE plasma…
Opened another thread recently about thunderjaro/swiftjaro, and the dev left a comment on YT with some notes and he also enabled vulkan for smoother playback.
Could not test any further because my system was crashing/freezing a lot, so I needed to pull the plug too many times. Checked my SSD and it’s supposedly still healthy, and reflashed good old Raspi Os 32bit on it (back up from sd card), already built vulkan on that image and Chromium is very snappy with it.
Still need to test the SSD later on, because I had to catch some sleep…
I have not run Kodi before but I would be interested, glad to give it a try.
When starting chromium from a terminal, I see the following:
[2661:2661:1128/063821.114414:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: Could not load GLX entry point glXSwapIntervalEXT
[2661:2661:1128/063821.115357:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: Could not load GLX entry point glXSwapIntervalEXT
[2661:2661:1128/063821.115758:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[2661:2661:1128/063821.116459:ERROR:angle_platform_impl.cc(43)] Display.cpp:805 (initialize): ANGLE Display::initialize error 12289: Could not load GLX entry point glXSwapIntervalEXT
[2661:2661:1128/063821.116896:ERROR:gl_surface_egl.cc(773)] EGL Driver message (Critical) eglInitialize: Could not load GLX entry point glXSwapIntervalEXT
[2661:2661:1128/063821.117159:ERROR:gl_surface_egl.cc(1322)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[2661:2661:1128/063821.117448:ERROR:gl_initializer_linux_x11.cc(160)] GLSurfaceEGL::InitializeOneOff failed.
[2661:2661:1128/063821.126292:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[2716:2716:1128/063821.245309:ERROR:vaapi_wrapper.cc(541)] vaInitialize failed: unknown libva error
So this likely explains the loss of opengl support in chromium.
Edit: I switched over to X11 but the same error.
The kwin compositor crashes on startup with X11. Not a huge loss for me. I just notice the loss of shadowing. With Wayland it seems to run fine, so I am back to Wayland since Chromium opengl support is not working on X11 either.
Edit: And switching between X11 and Wayland does not seem to be smooth. I am not sure if it is related to the compositor issue or even if it is repeatable at this point. But I have needed to power cycle/reboot when switching.
Edit2: My desktop on wayland just crashed, so there is some instability.
@Darksky If you were wanting me to test on a 4k monitor, I don’t plan to be back in the office until Monday. I just have use of a 1080p atm.
And for the curious about Vulkan Gears, here is a screenshot. You may notice the gears are in a different orientation, this version lets you move them around.
Might as well get a feel for kodi now so you do have to at work.
https://forum.manjaro.org/t/kodi-19-hevc-64-bit-rpi-4-test-packages/40293
I am following unstable and I modified my config.txt
I installed xf86-video-fbturbo-git
I had to roll back from mesa-git to mesa, as the git version always found v3dv. But I do have llvmpipe in Plasma on X11 now.
I installed the packages included in the tar via Ark by double clicking the four packages. They seemed to install without issue but maybe this is my error?
However, shift-ctl-f[1-8]? I usually use ctrl-alt-f[1-8] but neither work for me currently. So I changed from graphical to multi-user to run kodi. I ran kodi passing the mkv on the command line. Unfortunately, I did not get hw acceleration, so it stuttered.
You are right I typed the wrong sequence. I corrected the mistake. Try starting by opening up kodi and play from inside it. @spikerguy guy says his test was smooth.
I passed it on the command line because I could not find where to open the file from inside. It never showed up in the any of the file dialogs that I tried.
Edit: Btw, my sddm now has a Kodi session option… but login results returning to sddm.
I figured it out but still have SW rendering. The system info shows V3D 4.2 as the GPU.
If I take a look at Orphans, I see kodi-bin 18.9-1
I doubt that is the cause of SW rendering but it is interesting that it is installed and now shows as an orphan.
I loaded up my plasma install and CTRL-ALT-F2 does not work logged into plasma wayland but does work in regular plasma and at the graphical login screen. It did play the HEVC vid with HW decoding. I also had mesa-git installed and it was not an issue.
The only issue is I could never get back to the graphical screen with CTRL-ALT-F7.
Ah, I was not paying enough attention, sorry. Kodi is failing to work with libva, same error as chrome. Sorry for not catching this earlier. I tried reinstalling libva, no change.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)vainfo also throws the error. So I use strace and find this:
openat(AT_FDCWD, "/usr/lib/dri/vc4_drv_video.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
faccessat(AT_FDCWD, "/usr/lib/dri/vc4_drv_video.so", F_OK) = -1 ENOENT (No such file or directory)
write(2, "vaInitialize failed with error c"..., 66vaInitialize failed with error code -1 (unknown libva error),exit) = 66
This file does not exist on my system, I have /usr/lib/dri/vc4_dri.so
Which kernel are you on?
Also you seem to have mix kodi packages please remove all the kodi 18 packages first.
This is normal. It’s just trying it basically trying it and moving on. Mpv also goes this and maybe vlc.
It will not work in graphical mode.
Remove all kodi packages and reinstall my kodi 19 packages. The p8-platform package should stay there.
Thanks @spikerguy. I need to add some conflicts to the PKGBUILD.