robertoj

Thank you for sharing it Can you include these specifications, for quick reference for future readers? Board, Debian version, Kernel, Graphics (console, X11, wayland)

There's a new version of the kwiboo ffmpeg+v4l2request function https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3 And it was shown as a work in progress in the ffmpeg community https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 Then, it was noticed in the mpv community https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427 They previously said that v4l2request first needs to be integrated in ffmpeg officially, then mpv would start working on v4l2request This is needed, to have mpv+v4l2request compiling successfully and working under Debian Trixie (my experience)

In bookworm, trixie or noble?

Can someone confirm that xwayland is working in the other wayland desktops in armbian? I can't make it work in labwc

Share your DTS. It is the most challenging part of this. We can customize, based on SBC model.

Start with this DTS and change the GPIO for your OPIZ3 https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/overlays/piscreen-overlay.dts Or start with your DTS and change the "compatible" line to "compatible=waveshare,rpi-lcd-35" and copy the other parameters of piscreen-overlay.dts if needed Let us know if it works

Getting video acceleration is realtively easy in bookworm, but making it work in Trixie would be newsworthy

It all depends on the GUI apps you want to run. Web browser: at least 4GB Your own Python GUI app: 1GB 16GB storage is fine. "A more advanced build framework" only refers to the laptop you use to compile your own Armbian OS... it doesn't refer to the SBC where you will run it.

Yes, CONFIG_TINYDRM_ILI9486 is the kernel module for that model of LCD with DRM. There's another thread explaining how to use it. I think you can use udev rules to force SPI LCD as /dev/fb0 and HDMI as /dev/fb1 always.

I noticed this problem a long time ago, but now I feel it is important to fix it: I get a slim black bar on the left side, and a portion of the pixels on the right get "cropped" because they don't fit in the LCD display area? I get the left 2 pixels of the screen "cropped", so in console, the first left-side are always missing the left pixels. Do you get the same in your LCD? Do you know a way to fix it? I am talking about this LCD: RED PCB LCD https://www.aliexpress.us/item/3256802847521952.html?

In that case, dont try my solution: it is for the red ili9341. If you search ili9486 threads in this forum, that same blue LCD is ili9486... so you were wrong in calling it ili9341 in the first place If you have time, find another solution to get you a DRM frambuffer (instead of a classic FB). Then you can enjoy smoother animations and video. Regarding displaying boot messages to the LCD, instead of HDMI. I don't know, but it may be because your HDMI is /dev/fb0 and the LCD is /dev/fb1 Will you use X11?

Try this solution for the orange pi zero LTS, which is the same chip as the opiPC, but change the pin definitions to what you have. Do you have a 480x320 ili9341? Which one is it?

If anyone in interested in a lightweight wayland desktop, inspired by openbox, you should try labwc. In orange pi zero 3, we need to stay in bookworm to get video acceleration, so this guide helps build labwc in bookworm As a greeter, I chose pi-greeter, because it is the lightest login manager I could setup, without any X11 https://github.com/robertojguerra/opiz3-labwc-setup I am open to read any improvements, or show me how I could make deb packages. In the near future, I will make a step-by-step video tutorial in Youtube.

For video acceleration, you need to stick with Bookworm.

Has anybody tried compiling mpv-0.35 + PR14690 within Trixie and ffmpeg 7.x.x? If anyone is curious... mpv-0.37 fails in the compilation step in ad-spdif.c due to an incompatible pointer But mpv-0.38 (without patches) compiles successfully

Dont write that "fbi works correctly", when it is not. The display remains white, and the kernel doesn't show any errors. * Re-check your wiring * Disconnect the touch part of the LCD pins * Try reversing the polarity: dc-gpios = <&pio 2 6 1>; << change the 1 to 0 reset-gpios = <&pio 2 9 1>; << change the 1 to 0 If the CPU is successful sending the reset signal, the data/command, the chip select and any bytes through SPI, at least the LCD should turn black.

I got my issue resolved with labwc+greetd+nwg-hello See this link https://github.com/nwg-piotr/nwg-hello/issues/43 Please check it and post any corrections if needed Getting rpi-greeter (no python) and wf-panel-pi (combines panel and launcher in compact form) would be ideal, but not resolved yet. If anyone is interested in getting rpi-greeter working, this is my partial progress, and I still cannot make it start under lightdm, without any X11: sudo apt install lightdm accountsservice polkitd sudo apt install libgtk-layer-shell-dev librsvg2-common sudo apt install gnome-common gobject-introspection gir1.2-gtk-3.0 These might be needed. I installed them the day after I installed greetd and ngw-hello. Note: I am working from a minimal debian trixie image appmenu-gtk-module-common libaccountsservice-dev gir1.2-accountsservice-1.0 liblightdm-gobject-dev liblightdm-gobject-1-0 libgtk-3-dev gnome-common nasm ~$ mkdir rpi-greeter ; cd rpi-greeter wget https://github.com/raspberrypi-ui/pi-greeter/archive/refs/heads/master.zip unzip master.zip ; cd rpi-greeter-master autogen.sh ./configure make sudo make install Change /etc/lightdm/lightdm.conf with: greeter-session=pi-greeter-labwc Test with: $ sudo lightdm --test-mode --debug or $ sudo systemctl start lightdm $ journalctl -b -u lightdm.service The error is: Oct 13 22:01:49 orangepizero3 lightdm[845]: Error updating user /org/freedesktop/Accounts/User1000: GDBus.Error:org.freedesktop.Accounts.Error.PermissionDenied: Not authorized: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PolicyKit1 was not provided by any .service files DEBUG: Could not run plymouth --ping: Failed to execute child process ?plymouth? (No such file or directory) I think I am very close to getting rpi-greeter working. What could be missing? I see that in a raspberry pi, the folder /etc/xdg/labwc-greeter/ exists, with 3 files inside, but in armbian, it doesn't exist. Should it be created by sudo make install? sudo nano /var/log/lightdm/lightdm.log: Nothing weird. Only: [+0.07s] DEBUG: Session pid=6392: Running command /usr/bin/labwc -C /etc/xdg/labwc-greeter/ (and this folder /etc/xdg/labwc-greeter/ does not exist) In raspberry: /etc/xdg/labwc-greeter/ contains autostart, rc.xml and environment sudo nano /var/log/lightdm/seat0-greeter.log: ** (process:6392): WARNING **: 00:23:07.745: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.E> 00:00:00.000 [ERROR] [../src/main.c:202] XDG_RUNTIME_DIR is unset The etc/xdg/labwc-greeter/autostart, etc files come from a package named raspberrypi-ui-mods (raspberry$ dpkg -S /etc/xdg/labwc-greeter/autostart) What part of https://github.com/raspberrypi-ui/raspberrypi-ui-mods would get my lightdm+labwc+rpigreeter working? Copying the /etc/xdg/labwc-greeter/ folder with the 3 files, with the same permissions, allow the pi-greeter to display (it is very plain), but after entering the password, the text mode display shows for 2 seconds, then the labwc black background and cursor shows for 1/4 second, then returns to the login screen. Found this error in the log: /etc/xdg/labwc-greeter//autostart: 2: /usr/bin/kanshi: not found Final part of solution: lightdm should contain: user-session=LXDE-pi-labwc Create file /usr/share/wayland-sessions/ LXDE-pi-labwc.desktop: [Desktop Entry] Type=Application Name=Labwc Desktop on Wayland Exec=/usr/bin/labwc rpi-greeter does not allow selection of other sessions: only labwc

Thank you. I meant to ask about that PR14690 I would rather stay with trixie and low fps, because it seems easier to solve my other problem: need 100% wayland and 0% X11 due to a LCD driver problem.

Hello Jock, Can you confirm that you use the patch in mpv PR1460, or something else? --vo=gpu or -vo=gpu-next? I installed mesa-vulkan-drivers today, with some difference in the mpv log, but same performance I also get: [vo/gpu-next/libplacebo] Found no suitable device, giving up. [vo/gpu-next/libplacebo] Failed initializing vulkan device and ... Does it matter? If I want to test the latest libplacebo route (with git clone https://code.videolan.org/videolan/libplacebo.git...) do I need to uninstall libplacebo and libplacebo-dev?

This bug is not showing again with Trixie, and the repository labwc 0.8.3 (same), same orange pi zero 3, same HDMI monitor.

Those who are not getting hardware acceleration in Trixie, should compile their own mpv-0.4.0 with patches (in addition of using the ffmpeg-v4l2request deb version) Some guidelines here: https://forum.armbian.com/topic/32449-repository-for-v4l2request-hardware-video-decoding-rockchip-allwinner/page/5/#findComment-226875

I was successful in compiling mpv-0.3.9 + the 2 patches from PR14690. I downloaded the release mpv as a tar.gz, expanded it, and applied the 2 patches. One hunk failed but it wasnt needed A 720p h264 video played with 10% CPU: (note that the options are --hwdec=v4l2request --drm-drmprime-video-plane=primary --drm-draw-plane=overlay -v Next, I tried with a 1080p h264... in this case, I needed the extraargs=cma=256M line in armbianEnv.txt. Result, low CPU usage, but dropped frames (choppy video) I didn't need to install mpv, because I ran it from within the build directory Removing the --drm-drmprime-video-plane=primary --drm-draw-plane=overlay from the options didn't make any positive or negative difference I repeated the test with mpv-0.4.0 and the result was the same. I am using linux 6.15.4... tomorrow I will re-test with linux 6.16.8 and again with labwc (wayland) UPDATE: with labwc-0.8.3-1 (from Trixie repo), 720p playback is fine, and 1080p playback drops 220 frames over 10 seconds. However it seems that it activates an X11 renderer, and XWayland appears in the htop list. <-- only if started from SSH session, with "DISPLAY=:0" How can I ensure that pure wayland is used? <-- answer: start mpv from within a terminal in labwc, like foot mpv log: When I try mpv-0.3.9 (from the source folder, so I dont need to install it), I get the same result: v4l2request works perfectly in 720p, but choppy in 1080p

ARM CPU running Linux 2GB RAM NPU for AI (maybe as little as CV) ARM MPU running Sketch (Arduino) https://store-usa.arduino.cc/products/uno-q Closed source

Anyone trying to compile mpv 0.3.9, is it possible to do it with Linux 6.15? With the libraries in Debian Trixie? (considering mpv 0.3.9 is from sept 2024, and Trixie came with mpv-0.4.0) https://github.com/mpv-player/mpv/releases I think I am failing the compilation's linking stage, because I had a different mpv and its libraries already installed. Probably I need to format my microSD and re-image.

I am not sure if I am using the git command correctly to get mpv-0.3.9 with PR14690.. Please help roberto@orangepizero3:~$ mkdir mpv-official roberto@orangepizero3:~$ cd mpv-official/ roberto@orangepizero3:~/mpv-official$ git clone https://github.com/mpv-player/mpv roberto@orangepizero3:~/mpv-official$ cd mpv roberto@orangepizero3:~/mpv-official/mpv$ git checkout -b release/0.39 roberto@orangepizero3:~/mpv-official/mpv$ gh pr checkout 14690 <- downloads and applies the v4l2request changes roberto@orangepizero3:~/mpv-official/mpv$ nano video/out/gpu/hwdec.c <-- I see the added changes in the hwdec.c file roberto@orangepizero3:~/mpv-official/mpv$ meson setup build <-- everything configures ok, but at the end, it shows that I got mpv-0.40 I asked in the mpv github and a contributor said they are waiting for ffmpeg first incorporate v4l2request, then they will add the feature in mpv Ref: https://github.com/mpv-player/mpv/pull/14690#issuecomment-3369829206 Applying the pr14690 manually on top of mpv 0.3.9 is something that i could do, if there’s no choice For later: Use something like https://github.com/foo/bar/commit/${SHA}.patch , to try to get the PR14690 https://stackoverflow.com/questions/21903805/how-to-download-a-single-commit-diff-from-github Patches to apply: https://github.com/mpv-player/mpv/commit/d9bb7241bbc8dfdf1c76293d28cb162c2688e2b6.patch https://github.com/mpv-player/mpv/commit/17a8ef7e8752e39f8c5284127b5d7ba1cce64f48.patch Previous discussions and ffmpeg too: https://github.com/mpv-player/mpv/pull/14511 https://ffmpeg.org/pipermail/ffmpeg-devel/2024-August/332034.html https://ffmpeg.org/pipermail/ffmpeg-devel/2024-August/332035.html How to patch. Finally, I got this error since the first linking action [307/310] Linking target mpv FAILED: mpv cc -o mpv libmpv.so.2.3.0.p/aud... (and over a thousand linking errors)