robertoj

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 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

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)

I thought that v4l2request was exclusively in this github project and branch: https://github.com/philipl/mpv/tree/v4l2request Which github project and branch/release are you trying? I successfully compiled and installed the mpv from https://github.com/philipl/mpv/tree/v4l2request I made the /etc/mpv.conf as per the original post Result: 50% cpu in 4 cores, about half dropped frames: I don't see any mention of hwdec=drm in the mpv log I used the libplacebo from Trixie, not compiled on my own... I can try that next. <- final update for this post: libplacebo downloaded and built by myself did not help... but now I will try mpv 0.3.9

Ok the problem is that I didn't download the correct source code: This: wget https://github.com/philipl/mpv/archive/refs/heads/v4l2request.zip Gets me a hwdec.c without the lines: extern const struct ra_hwdec_driver ra_hwdec_v4l2request; extern const struct ra_hwdec_driver ra_hwdec_v4l2request_overlay; And possibly more missing stuff New try for source download: $ git clone https://github.com/philipl/mpv.git $ cd mpv $ git checkout -b v4l2request origin/v4l2request $ nano video/out/gpu/hwdec.c <-- contains the changes for v4l2 request, then exit nano without changes $ meson setup build <-- shows the same warnings as before $ meson compile -C build ... I still get this build error Can anybody suggest, how I use these instuctions: https://gist.github.com/linguisticmind/d765a12e121bfdef2e8878b38d11b5ef But use this repo's specific branch: https://github.com/philipl/mpv/tree/v4l2request ? UPDATE: I followed the first step of https://gist.github.com/linguisticmind/d765a12e121bfdef2e8878b38d11b5ef and it installed many more dependencies than I did by myself manually. I returned to the git folder source from philipl, and tried again: Now "meson setup build" shows x11 and wayland support... all the options are enabled, except d3d11

Yep... that looks like the method I had thought about: get the source from https://github.com/philipl/mpv.git#branch=v4l2request and compile it with the v4l2request option I have old experience making redhat rpms, but I need to learn how to make debian debs UPDATE: I wrote my self built debian trixie xfce image with 6.15.4 from July (need 6.13+ for v4l2 kernel functions)... then Install the apt.undo.it repo and ffmpeg, as per the first post of this thread (Following guide from https://github.com/philipl/mpv/tree/v4l2request) $ sudo apt install libavcodec-dev (installs libavutil-dev libswresample-dev automatically) $ sudo apt install libavdevice-dev (installs libavfilter-dev libavformat-dev libpostproc-dev libswscale-dev automatically) $ sudo apt install meson cmake pkg-config Download code: $ wget https://github.com/philipl/mpv/archive/refs/heads/v4l2request.zip $ unzip v4l2request.zip $ cd mpv-4l2request Install libplacebo source $ mkdir -p subprojects $ git clone https://code.videolan.org/videolan/libplacebo.git --depth=1 --recursive subprojects/libplacebo $ sudo apt install libplacebo-dev libass-dev Build: $ meson setup build ^ Finally all the essential dependencies were found, and the disabled features are with a RED "NO"... but v4l2request is ENABLED Compile: $ meson compile -C build FAILED /usr/bin/ld: libmpv.so.2.5.0.p/video_out_gpu_hwdec.c.o:/home/roberto/mpv-4l2request/build/../video/out/gpu/hwdec.c:284: more undefined references to `ra_hwdec_v4l2request' follow /usr/bin/ld: libmpv.so.2.5.0.p/video_out_gpu_hwdec.c.o:(.data.rel.ro+0x8): undefined reference to `ra_hwdec_v4l2request_overlay' Does anybody have any idea how to fix this? What to check? I ran out of time again to research Maybe its the libplacebo (which is a very bad name for GPU libraries)... Debian Trixie=7.349 (mid 2024), VLC repo=7.351 (mid 2025) Repeating the mpv compilation, with libplacebo from VLC There's no wayland or X11 support... someone please please tell me what to do Build... failed Same ra_hwdec_v4l2request and ra_hwdec_v4l2request_request missing error for next try: install wayland-protocols-dev, libx11-dev, libgl-dev, libwayland-dev

Did you mean that you had success getting HW acceleration in Arch Linux+mpv-0.40.0? Which github page did you use, and did you use the standard official instructions in that github page, to build?

Has anyone here configured armbian with a Wayland desktop, and completely free of X11? How did you do it? I have compiled labwc and it works great with my orange pi zero 3, with bookworm or trixie... but I can't figure out how to configure a wayland greeter. I need to do this because my LCD driver can't work with X11 (panel-mipi-dbi-spi).

Describe what you did before to make it work. Show the DTS, the wiring you connected and the linux version that worked. If you used spidev before, I don't have experience in that. I only have experience with these drivers: panel-mipi-dbi-spi, ili9431 and adafrui-xy... The threads I showed you require you to stop using spidev, since the Linux kernel will communicate directly to the LCD, without a user program. Using both will just make them interfere with each other. If the LCD remains white and doesn't even flicker, and you made it work in an older kernel, then keep that wiring. If the /dev/fb0 exists, it means that linux has taken one SPI output port for display, but you need to make sure that: * and SPI parameters in the DTS are correct, * the gpio to handle the command/data, reset parameters are pointing to valid orange pi pins which are not used by anything else * the high/low polarity of those gpio * the wiring is correct, * the initialization bytes are correct

quoting JPL: Did you see any announcement by the github's owner, about what we can expect from her/his source code? Looking at the content of the file, it seems like we need to download the code from: https://github.com/philipl/mpv#branch=v4l2request or https://github.com/philipl/mpv/tree/v4l2request And include this build-time configuration -Dv4l2request='enabled' I have posted instructions to build MPV on Sept 26 in this thread Warning: if you try compiling this MPV source package, don't try it in bookworm. You need Trixie to get the required libavcodec60+ dependency (and maybe others).

Instructions to build mpv, for anyone trying it with trixie... I don't see any pre-compilation options related to v4l2request https://forums.raspberrypi.com/viewtopic.php?t=360902#p2172777 https://github.com/mpv-player/mpv-build https://www.youtube.com/watch?v=KdyX3k8vOhw

Has anybody had success with ffmpeg-v4l2request under Debian TRIXIE? I have seen successful reports from Jammy and Noble users... are they still having success?

I think it will run out or RAM... but try it anyway

That change is already merged into Armbian for the orange pi zero LTS. It was such a long time ago, I don't remember how to use it right now. https://github.com/armbian/build/blob/9ef5b99b220c5e77b55514136e025008c16ccbfd/patch/kernel/archive/sunxi-6.12/patches.armbian/enable-TV-Output-on-OrangePi-Zero-LTE.patch#L8 https://github.com/armbian/build/commit/41260ac309b487d241fec97ffbdeced730bc2d04 Partial progress log https://forum.armbian.com/topic/22226-orange-pi-zero-lts-tv-out-in-2022/#findComment-162035

Is it the 128x160 1.8" red screen? Combine the knowledge of https://forums.raspberrypi.com/viewtopic.php?t=380704&hilit=ST7735S#p2275556 and https://forum.armbian.com/topic/47971-driving-the-ili9488-lcd-40-inch-cheap-chinese-clone/ To use the panel-mipi-dbi-spi driver, which is more universal for SPI screens Warning: you will not get the spidev, and the linux OS will handle all the rendering. Also, X11 may have a problem with Linux 6.14, unless someone fixes a bug

Make sure that the octoprint project still supports 32 bit CPUs For low ram sbc's, I suggest doing a classic installation, instead of Docker You can skip the webcam portion installation, and give you no problems. I had my opiz LTS (512MB) running octoprint last year, and the webcam function works well... but I only used octoprint-Docker when I had 2GB of RAM server.

I don't see it as the very latest bleeding edge kernel version. I see it as a newish Linux, which already has the armbian patches updated for. Some CPUs end up with newer or older Linux versions, due to varying levels of development success. For example, sunxi's armbian edge is 6.15.4 today, but the linux trunk is up to 6.17-rc6 ... (not available in Armbian)

Building a rolling release is more than just showing that in the MOTD. If you do "sudo apt upgrade" in an OS image you just built, you probably will have zero or one packages to upgrade. If you start with an image built a long time ago, or with packages defined a long time ago, then "sudo apt upgrade" would take a long time.

I have the same debian as you: 5.1.4-xxx-v4l2request, installed over Debian Bookworm, with Linux 6.15 (OS built by myself). When I tried the ffmpeg-7.x.x-v4l2request for Trixie, I could not get hardware acceleration.