robertoj

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)

Regarding video acceleration in H618: Can you try the latest armbian with linux edge? https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/#findComment-216587 (the announcement refers to 6.13, but I don't know if it applies to 6.14 or 6.15) ... I think armbian 25.5.1 with linux edge option, builds linux 6.13.x https://github.com/armbian/build/releases/tag/v25.5.1 (and it seems that minimal images de-activates v4l2) I see the patches in my armbian build folder, I compiled in many ways, but I didn't get video acceleration. I didn't get new kernel modules that seem to be related to the patch source code. Perhaps I needed to check that the specific patches are activated or find the linux config option=m Update: you can see that the Linux source files are applied, right before the compilation stage... copy paste the entire terminal scrolled text (or find the appropriate output/log/... file)... search the patch file names I couldn't get acceleration, but hopefully someone else can, and share the method.

My story is definitely NOT a success story I see the media.patches in the cache folder, I compile armbian edge, but the image didn't contain the cedrus+v4l2 kernel modules I need for decoding acceleration

Hello Jock, thank you for all the work bringing this video acceleration to our boards. Can you give an updated comment about what to download or how to build Armbian OS, and get the needed requirements, before we apply the ffmpeg repository? I haven't been able to get video acceleration for many months. Can you tell us what new kernel modules are needed also?

Are there any linux build config options needed to get the v4l2 functions? Can I assume that the improvements in 6.13.11 would be also in 6.15.4? No, the patches in pull/8086 are not in 6.14, 6.15 build/patch/kernel/archive/sunxi-6.13/patches.media vs the 6.14,6.15 folders Right now, linux-current is 6.12 and linux-edge is 6.15... I want to compile a Linux 6.13 Armbian OS... what specific linux version would I need to enter inside userpatches/lib.config ? KERNELBRANCH="tag:v6.13.xx" I tried building armbian 25.5.1 so I could get linux 6.14.x... but in the image file, there aren't the ko files mentioned in the pull/8086. For example: roberto@orangepizero3:~$ ls /lib/modules/6.14.5-edge-sunxi64/kernel/drivers/media/v4l2-core/ tuner.ko v4l2-cci.ko v4l2-fwnode.ko v4l2-jpeg.ko v4l2-vp9.ko v4l2-async.ko v4l2-dv-timings.ko v4l2-h264.ko v4l2-mem2mem.ko videodev.ko roberto@orangepizero3:~$ ls /lib/modules/6.14.5-edge-sunxi64/kernel/drivers/media/v4l2-core/v4l2-io* ls: cannot access '/lib/modules/6.14.5-edge-sunxi64/kernel/drivers/media/v4l2-core/v4l2-io*': No such file or directory

Can someone tell me if Linux 6.14.8 or 6.15.4 supports this hardware acceleration? I can play 1080p H264, but with 100% CPU, with 6.14.8... and I get "unsuppoerted hwdec: drm" everytime I start mpv

Thank you!

What kernel version are you using now, and what was the linux version that failed before? If you can't remember: cat /var/log/apt/term.log |grep linux-image

I am checking now Before installing plymouth, I checked that panel-mipi-dbi-spi is still loaded late: I added the include-lcd-bin.sh and installed plymouth: Checking that my bin file is there: The LCD works with plymouth: it starts the LCD earlier, with a smaller font, then switches to normal font, showing all the boot messages My armbian is not setup yet with lightdm+openbox (x11) or greetd+gtkgreet+labwc (wayland)... I will continue tomorrow

Currently trying to follow the manual https://manpages.ubuntu.com/manpages/bionic/man8/initramfs-tools.8.html#configuration hook scripts I want to include this file: Creating this file: chmod +x include-lcd-bin.sh Then I updated the initrd: Then I checked, and the desired file was included I will repeat this with the actual armbian OS with plymouth, tomorrow.

I am using my orange pi zero 3 with an SPI 4.0" LCD, with driver panel-mipi-dbi-spi. It works great with Linux 6.13.7 (started with a self built image with edge, minimal, Bookworm) and older, but I am having troubles with 6.14.8. Result from armbianmonitor -u after upgrading to linux 6.14.8: sudo apt install linux-image-edge-sunxi64=25.5.1 I reboot and the SPI LCD starts the text mode console, then turns black instead of starting lightdm https://paste.armbian.com/ucoxuwetiq Also xorg log after "sudo startx" fails to start. When I start the opiz3 with an HDMI screen connected (appears as /dev/fb0), startx and lightdm start normally, but NOT displaying anything in the small LCD Then, I downgrade to linux 6.13.7, sudo apt install linux-image-edge-sunxi64=25.2.3 I reboot and lightdm starts normally in the 4.0 LCD https://paste.armbian.com/uqafuxexiv Stopping lightdm and trying x11 to see the log sudo startx ... starts xorg normally Just downgrading to Linux 6.13.7 allows the 4.0" SPI LCD to work again. Dowgrading the linux package did not cause a downgrade of X11 (version 1.21.1.7). The small LCD always works ok in text mode. The driver is DRM but it is using the X11 fbdev submodule The fbdev.conf file: Using an HDMI screen is not affected When I disable the fbdev conf file sudo mv 99-fbdev.conf 99-fbdev.conf.disabled Then x11 fails in another way: The xorg log doesn't show any error: dmesg|grep MESA shows nothing. Probably here is the solution https://github.com/agherzan/meta-raspberrypi/issues/1389 rebuilding mesa with some extra dependencies Bookworm containg mesa 22.3.6 right now, but Trixie contains mesa 25.0.5 I tried the same in Trixie and Sid, but still get the same error: not able to load panel-mipi-dbi_dri.so I have a newly built armbian OS with kernel 6.15.x... I will try it later today.

I haven't tested this... but I see that pins PH1, PI11, PI14 are not connectable in the orange pi zero 3. Only PH3 would be connectable. Is this correct? Is there an overlay to get PWM in PH2? (i read in the post from April 5 that it can be a PWM pin)

Thank you, I found the manual for initramfs-tools and hooks ... it looks like I can do it

Hello WDR_s, If you upgraded kernel recently, did you have any problem starting X11 (or lightdm, or desktop)? I started with a downloaded arm minimal image with linux 6.12, and my DTS would bring up the panel-mipi-dbi-spi driver correctly in text mode, but X11 can't start. When I have my normal 99-fbdev.conf, I get this: FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument, When I remove 99-fbdev.conf and let X11 setup everything automatically, X11 complains about needing panel-mipi-dbi_dri.so. I restored an old armbian OS backup with linux 6.11, and everything worked normally. You are using a different LCD driver, did you have any problem?

labwc is available in debian trixie: Start with a minimal armbian install Make sure your /dev/fb0 is DRM, not framebuffer $ sudo apt install seatd labwc foot $ labwc -s foot

I am having trouble with my SPI LCD, which uses driver panel-mipi-dbi It works great when I use a minimal Armbian image, but with a desktop image it doesn't work. This is because package "plymouth" does something in the ko loading order: it loads panel-mipi-dbi too early. Plymouth provides a graphical boot animation. The driver depends on a binary file /lib/firmware/panel-mipi-dbi-spi.bin (but the file name could change depending on the DTS) At boot time, I saw that the panel-mipi-dbi.ko is loaded BEFORE the EXT4 in the microSD is mounted... and the binary file is not in the initrd.img-version (checked with lsinitramfs) Is it possible to add something in /etc/initramfs-tools/ to include /lib/firmware/panel-mipi-dbi-spi.bin ? With my Raspberry Pi (Raspbian) I don't have this problem, because the panel-mipi-dbi driver is loaded AFTER EXT4-fs (and it also uses plymouth) I found that when plymouth is not installed, usr/lib/modules/6.15.0-edge-sunxi64/modules.dep doesn't have this line kernel/drivers/gpu/drm/tiny/panel-mipi-dbi.ko: kernel/drivers/gpu/drm/drm_mipi_dbi.ko Also, in Raspbian, the same file has the dependency line, but changed with 5 more dependencies kernel/drivers/gpu/drm/tiny/panel-mipi-dbi.ko: kernel/drivers/gpu/drm/drm_dma_helper.ko kernel/drivers/gpu/drm/drm_mipi_dbi.ko kernel/drivers/gpu/drm/drm_kms_helper.ko kernel/drivers/gpu/drm/drm.ko kernel/drivers/gpu/drm/drm_panel_orientation_quirks.ko kernel/drivers/video/backlight/backlight.ko And this is confirmed with modinfo drm_mipi_dbi: 1 dependency in armbian and 5 dependencies in raspbian... could this be the reason why the ko is loading too early?