robertoj

I got hardware acceleration working in wayland+labwc, in Bookworm, Linux 6.15.4, self built armbian With a self-compiled labwc (instructions: https://forum.armbian.com/topic/53797-labwc-wayland-crashes-on-exit/#findComment-223267 ) And the ffmpeg instructions in the original post were used with no changes... plus the extraargs=cma=256M in armbianEnv.txt Side question: can anybody make hardware acceleration work in Trixie?

Yes. Correct. Start with an armbian minimal or xcfe image that you build, with linux edge. Then install all the compilation dependencies mentioned in https://github.com/labwc/labwc/wiki and https://github.com/swaywm/sway/wiki/Debian-10-(Buster)-Installation#install-wlroots Some are mentioned as indicated for raspberry, but I installed them as well Do not install the debian bookworm libwlroots10 !! (this old wlroots interferes with the wlroots that will be installed now) Do not install libelogind-dev (it tried to modify my initramfs, it messed up the boot process, I didnt actually need it) You need a meson compiler more recent than bookworm provides. Install the backports repo: https://backports.debian.org/Instructions/ $ sudo apt install meson/bookworm-backports $ meson -v 1.7.0 Getting the labwc source code, and building: $ sudo apt install foot seatd (a minimal xterm for wayland, and a "seat manager" (may not be needed)) $ git clone https://github.com/labwc/labwc $ cd labwc $ meson setup build <-check that you have at least the GLES2 or EGL renderer If not, check that you have these dependencies: libegl-dev, libegl1-mesa-dev, libgles2-mesa-dev, libgles-dev If xwayland is desired, install xwayland from the bookworm repo After installing extra dependencies, run reconfiguration: $ meson setup --reconfigure build You will notice that the labwc build process auto-downloads and compiles a recent wlroots Finally compile (it took less than 5 minutes in my orange pi zero 3) $ meson compile -C build If it finishes compiling, check that the produced labwc works with: $ ./build/labwc -s foot If there's an error about memory allocation, add to armbianEnv.txt "extraargs=cma=256M", then reboot To install globally: $ sudo meson install -C build Test by exiting the labwc folder: cd ~ $ labwc -s foot Tomorrow, I will continue installing a display manager and greeter that works with wayland... since I am trying to avoid X11, due to my SPI LCD driver But all of you who try getting labwc in bookworm, hopefully the meson install command does something that lets lightdm see it is available as an option (I started with a minimal image)

I didn't try to replicate the problem in x86... but I compiled the latest labwc 0.9.0, in Orange Pi Zero 3 with Bookworm, and this problem does not show up

Thank you for the information I have completed the build dependencies step, for mesa 25.2, in Debian Trixie. However, when I build it, my orange pi zero 3 with 1 GB or RAM, it runs out of memory... even when I make a swap file of 2GB. I keep rebooting the opiz3, and continue the compilation job. Is this normal? In the raspberry forum, they told me that my LCD driver panel-mipi-dbi.ko doesn't work with X11... so I give up on this, and continue my development with labwc/wayland (easily installed in Trixie)

Thank you. I found that libllvmspirvlb 19 is only available in trixie... can you confirm? In bookworm, I needed to replace llvm-18-dev libclang-18-dev libllvmspirvlib-18-dev with llvm-19-dev libclang-19-dev libllvmspirvlib-15-dev But tomorrow I will try again with trixie

Thank you for your suggestions. I am trying to build Mesa in my Orange Pi Zero 3. When I tried installing the build dependencies, apt could not find libxatracker-dev, libllvm-18-dev, libspirv-tools-dev i added changed "deb-src" in the /etc/apt/debian.list, so I could download *-dev packages. How did you install all the dependencies? Are you in Bookworm, or Trixie? Actually I am looking for a double benefit with a new Mesa (bookworm provides mesa 22.3.6, trixie provides 25.0.7): *H264 hardware acceleration *I know that Raspberry has a newer Mesa (don't have it at hand), and X11 can handle the same LCD, with the same kernel module panel-mipi-dbi.ko

I have seen other threads where they recompile mesa to get an updated so module for X11, related to LCD panels and DRM. I haven't had time for that yet.

Sensor integration: buy a OBD2 to USB adapter and study the OBD2 codes to read the fuel liters/hour, km and km/h. It is very possible there is a python OBD2 library. The SBC should be running continuously in the vehicle, since the car electronic control unit does not have the memory to store the information for you. Python+tkinter/pyqt6+matplotlib is very effective for this kind of apps.

Has anybody had success with Armbian Trixie? I repeated the steps I did for Bookworm, to have HW accelerated H264 1080p in XFCE, X11, with Linux 6.15.4... and I get "Unsupported hwdec: drm" in Trixie: ffmpeg 7.1.1, mpv 0.4.0 mpv log in trixie (with double verbose): For reference, mpv log in Bookworm: I inspected ffmpeg build configuration, and I see that ffmpeg 7.1.1 doesn't have "--enable-libv4l2", while ffmpeg 5.1.6 has that option. I checked with "ffmpeg -codecs|grep h264" In bookworm: In trixie Although, here the ffmpeg manual reads that this is option is only for webcams and videocapture https://www.ffmpeg.org/ffmpeg-devices.html#video4linux2_002c-v4l2

Do you see all the needed files in the initramfs? Use lsinitramfs -l /boot/initrd... What guide did you use?

I would try the cma=256M argument anyway... this kernel argument eliminated my video glitches and dma errors. I don't know how a dtsi or dtbo parameter (loaded after linux is started) would override a kernel argument (given before the linux kernel is started).

Successful playing of H264 1080p mp4 Orange pi zero 3, 1GB Self-built Bookworm, with XFCE desktop Linux edge 6.15.4 No changed linux configurations Using ffmpeg+libraries provided in the first post of https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/ (you can even install all the bookworm ffmpeg, mpv, then when you add the new repository, update and upgrade, apt will replace the packages with their ffmpeg-v4l2request equivalents) Testing 1080P H264 (warning, some mp4's will actually be AV1 codec), checked with VLC Compositor on or off, doesn't make a difference. Video plays at full 30 fps To avoid video glitches during window resizing: add "extraargs=cma=256M" in /boot/armbianEnv.txt With hwdec=drm-prime, CPU is 50% in all 4 cores With hwdec=drm, CPU is 10% or less in all 4 cores Without HW acceleration, CPU is 100% in all 4 cores with many skipped frames mpv.conf and mpv log: Reveal hidden contents THANK YOU to all who gave me updated information! Edited just now by robertoj

You are right. I just downloaded something from youtube and assumed it was H264. When I checked it in VLC in my PC, the codec is: AOMedia's AV1 video (av01) I picked another mp4, which I verified in VLC as H264-MPEG4, 720p, and it played with 10% CPU This test below is with Bookworm XFCE, compositor ON, Linux 6.15.4 with default configuration Then I repeat the test with a 1080p H264 mp4. mpv tries to use hardware acceleration, but the mpv is black and there's continuous DRM_IOCTL errors: Then I tried this inside /etc/mpv/mpv.conf hwdec=drm-prime drm-drmprime-video-plane=primary drm-draw-plane=overlay and the 1080p H264 starts playing fluidly with just 40% CPU (compositor off) With compositor on, I get same 40% CPU Same video glitches, with or without compositor, but I am getting hardware acceleration (although there's the hwdec unsupported message) Update: Thank you to all who helped me. I have hardware acceleration again with my opiz3 hwdec=drm is more efficient extraargs=cma=256 is needed to avoid memory allocation problems and video glitches. https://forum.armbian.com/topic/29202-orange-pi-zero-3/page/26/#findComment-222596

I started building mesa 25.2 according to https://docs.mesa3d.org/install.html When I started meson, it complained about meson-1.0.1 is too old (Bookworm)... needs 1.4.0 Trixie will provide meson 1.7... is this what you did? Start with a self built Armbian-Trixie? When you type "replace the libs", do you mean to uninstall debian package, and install the just compiled source? libva2 - Video Acceleration (VA) API for Linux -- runtime Is this independent from ffmpeg (I only see libav in ffmpeg, not libva) Does mpv need any special configuration?

I have tried again with trixie, ensuring that the kernel patches were taken... no difference. Then I build a Bookworm Armbian image, with linux 6.15.4. It wasn't visible wether the kernel was downloaded from armbian, or the last one was included in my OS image. Just for fun, I tried it with Bookworm's default ffmpeg-5.1.6, with xfce with compositor off... and I got a 1080p MP4 playing with 100% mpv log: Note that mpv still complains about unsupported hwdec: drm I repeated the test with compositor ON: killall xfwm4 && xfwm4 --compositor=on --display :0.0 & Same result: CPU 100%, but nice full FPS video Then I tried with the ffmpeg-x.x.x-v4l2 request Adding the repo, updating, and checking the update: Then I tried playing the mp4, I got no complaint about "unsupported hwdec: drm", but the CPU was still 100% For the first time, I get some video glitches when I resize, and repeated messages: Failed to create scanout resource DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory compositor=on or off doesn't make a difference for me. mpv log: Summary: Armbian Trixie (and the correspoinding ffmpeg 7.1.1) will always result in "unsupported hwdec: drm", with default ffmpeg, or ffmpeg-v4l2 request Armbian Bookworm (ffmpeg 5.1.6) will never complain about "unsupported hwdec: drm", with default ffmpeg or ffmpeg-v4l2request. Still 100% CPU

It turns out I was closer than I thought... thank you!

I tried this in a raspberry pi with graphic services stopped. Labwc exits normally I tried it in a virtualbox x86, with Debian trixie netinstall (barebones+labwc+seatd). Labwc exits normally. I think other armbian users (probably non allwinner) have used labwc, but they never complained about Labwc crashes. YES. I will try it with a true intel system. I will also try the stable-version Linux (instead of edge).

Thank you Nick I tried again with compositor off I still get: [vd] Unsupported hwdec: drm [vd] Using software decoding. https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/page/4/

I have tried again with orange pi zero 3, debian trixie linux edge, xfce desktop. This time, I tried without compositor. I ran this from SSH, as my user: killall xfwm4 && xfwm4 --compositor=off & I got: (xfwm4:7880): Gtk-WARNING **: 10:45:56.629: cannot open display: Then I tried "killall xfwm4 && xfwm4 --compositor=off --display :0.0 &" and there were no errors. The orange transparent effect when moving windows is now a white line rectangle Then, mpv played my 1080p mp4 with low framerate (slow motion, 75% of speed)... sometimes with 100% CPU and sometimes with 25% CPU I noticed this in the log (both high and low CPU cases) [vd] Unsupported hwdec: drm [vd] Using software decoding. With high CPU: [cplayer] Set property: user-data/osc/margins={"b":0,"r":0,"t":0,"l":0} -> 1 With 25% CPU: [cplayer] Set property: user-data/osc/margins={"l":0,"b":0,"r":0,"t":0} -> 1 Whole log (low CPU case): (Mpv.conf at the bottom) Another sanity check: Ryzer, did you turn the compositor off? Are you using an armbian-downloaded OS, or self built? What kernel version? DId you change anything in the linux menuconfig? I am recompiling again, having checked again that the new linux patches are taken.... how could I check that my current Linux kernel has the new v4l2, cedrus functions? Then I will try again with Bookworm

Ryzer, you can navigate to the http link http://apt.undo.it:7242 click “pool” and all the other links until you see all the debs for download check you distribution recommended ffmpeg version with “apt list ffmpeg” download the matching deb versions: ffmpeg-x.x.x-v4l2request.deb, lib…x.x.x Sudo apt install ./lib…Deb (one by one) Sudo apt install./ffmpeg….deb sudo apt install mpv (from the original Armbian-configured repository)

Which arm board are you using? Do you have success with hardware acceleration with armbian?

I don't even have a reference viewpoint what should I start comparing? I read claims that Python3-numpy, python3-opencv are highly optimized, but I never researched HOW OPTIMIZED I have also heard that DRM can help accelerate machine learning https://www.youtube.com/watch?v=NQz6VqvtehI&t=5m7s

I have been trying to set up labwc as a replacement for openbox (X11) in my project. I can install it very simply by building a minimal image Trixie (Bookworm does not include labwc), then * sudo apt install labwc seatd foot * at the screen with usb keyboard (not from SSH) start: labwc -d -s foot Then I am in labwc, with a terminal emulator on my HDMI screen When I right click on the desktop and choose "Exit", I get a kernel oops: And the labwc process shows "defunct" Has anybody experienced this? Maybe my kernel is too new? I used 6.15.4 (edge). My labwc is 0.8.3 The error in the terminal that started labwc (the HDMI screen) is: ...wlr_drm_lease_v1.c:103] Destroying wlr_drm_lease_device_v1 for /dev/dri/cardiationsodifier LINEAR (0x0000.....) XT_EGL_image_storage_compression GL_EXT_texture_storage_compression GL_MESA_bgra im... Same error message here: https://github.com/labwc/labwc/issues/1424 Source of wlroots, mentioned in the error: https://github.com/swaywm/wlroots/blob/master/types/wlr_drm_lease_v1.c A developer in the labwc group suggest this might be GPU driver related https://github.com/labwc/labwc/discussions/2923 Can someone with an SBC other than H618 try running labwc and exiting? What about xfce in wayland mode... does it crash? Is anyone aware of a H618 or sunxi running wayland successfully?

Thank you for replying. I run xscreensavers-gl in a window and it always gets 30FPS with <10% CPU in my opiz3, I even show 3D models in F3D... so I am getting 3D MESA acceleration in HDMI and SPI-LCD displays. If the video decoding in my opiz3 is using ARM NEON instructions, then I am fortunate I have that, at least (note: this is possible without needing ffmpeg-v4l2request) I will have to re-check how I was successful with 1080P H264 acceleration last year (I was even getting temporary glitches and pink hues sometimes).

Ok, I finally built armbian 25.5.1, to get Linux-edge 14.7 Bookworm + XFCE for my opiz3... and this time copy/pasted the whole build log to verify that: * the new patches mentioned in Pull Request 8086 were applied * the affected C files are compiled to .o files And then I tried the new ffmpeg-v4l2request with Bookworm's MPV, following the instructions in the original post.... I got the same result: 1080P plays smoothly, but with 100% CPU in all 4 cores. There's no error message of "unsupported hwdec=drm"... but there isn't any confirmation message from MPV either. (same behavior as with plain ffmpeg, from previous experiments)