robertoj

I have an Orange Pi Zero 3, Opi z2w, Opi z LTS, and Banana Pi M2 Zero. If the OS image is not in your download page, does it mean you don't need help with these boards? I didn't have any problems with opiz3 Armbian.com or self built image ever (last time I tried was 2 months ago). The others: haven't used in 1 year.

Yes usermod -aG docker yourusername , then reboot, was what I needed to let the armbian build script continue Warning: if you forget the "a" in -aG, you will get locked out being admin in your own computer Second roadblock: I needed to install qemu as per: https://forum.armbian.com/topic/52127-running-armbian-build-on-x86-64/#findComment-219019 Thank you Werner!

I just upgraded my Linux Mint from 22.2 to 22.3 "Zena" ... CLEAN INSTALL, with "git" installed I started a typical armbian build folder, as per: https://github.com/armbian/build?tab=readme-ov-file#quick-start But then I got this error: [🌱] Build host OS release [ zena ] [🌱] Build host architecture [ amd64 ] [💥] error! [ Unsupported build system: 'zena' ] I know that Mint 22.3 was released just last month, but I needed something in the new Linux kernel. I can use Mint 22.2 in another computer (where armbian is working OK)... but what is the typical delay for a new Linux Mint to become supported? Then I tried with $ sudo apt install docker.io , and got a little further: $ ./compile.sh [🚸] Docker is installed, but not usable [ can't use Docker; check your Docker config / groups / etc ] [💥] Problem detected [ Docker installed but not usable ] [💥] Exiting in 10 seconds [ Press <Ctrl-C> to abort, <Enter> to ignore and continue ] Counting down: 9... 8... 7... 6... 5... 4... 3... 2... 1... 0... [💥] error! [ Exiting due to 'Docker installed but not usable' ] [💥] Exiting with error 43 [ at /home/roberto/armbian-2026-feb/build/lib/functions/logging/traps.sh:1 exit_with_error() --> lib/functions/logging/traps.sh:1 exit_if_countdown_not_aborted() --> lib/functions/general/countdown.sh:41 cli_standard_relaunch_docker_or_sudo() --> lib/functions/cli/utils-cli.sh:261 cli_standard_build_pre_run() --> lib/functions/cli/cli-build.sh:14 armbian_cli_pre_run_command() --> lib/functions/cli/utils-cli.sh:122 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:79 main() --> ./compile.sh:50 More info: my docker is version 28.2.2 $ apt list docker.io Listing... Done docker.io/noble-updates,now 28.2.2-0ubuntu1~24.04.1 amd64 [installed] docker v17.6 needed. Reference: https://docs.armbian.com/Developer-Guide_Building-with-Docker/

Hello Orima, Thank you for asking. I am doing well. I've been mainly distracted by an online drawing class. I will try to make a complete written guide in the weekend. It will be a new project in my github, and I will make a new thread here.

JFL, can you check the Ubuntu gnome is running under wayland? ($ echo $XDG_SESSION_TYPE) Can you check the labwc availability in Ubuntu Noble? ($ apt list labwc) I never tested H265... I am glad it is working

Oh so I stand corrected... I was going from information on the website: I don't see a Linux client, and in other sites: emby was open source but now it's not

You can't use emby and the h618 acceleration with ffmpeg-v4l2request... you need to make emby work under Debian, and tell emby to use mpv.

Thank you for the comment Jock Yes, I know that Trixie's mpv made some changes that made it incompatible with your ffmpeg+v4lrequest package. I tried to compile mpv, and I wasn't sure of how to do it. I asked for help in the mpv github, and someone told me to wait for ffmpeg to merge this function. https://github.com/mpv-player/mpv/pull/14690#issuecomment-3369553163 Recently, I got more suggestions to build ffmpeg for Trixie https://github.com/mpv-player/mpv/pull/14690#issuecomment-3828170966 Boringname... can you specify which Debian version, Linux kernel and graphical desktop (kde, xfce, gnome, plasma, labwc, sway)?

There was a successful test with Debian Forky in RK3566 I saw some progress and success in the last 2 days. Someone made compiled ffmpeg 8.0+v4l2request and made it work in Debian Forky... which also carries ffmpeg 8.0 https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427 Does this mean that I need to use Debian Forky too? (I was staying with Debian Bookworm because H264 hwaccel only worked there) References: https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3 https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 https://tracker.debian.org/pkg/ffmpeg

Yes. Please wait. I was busy with other personal projects, so I haven't been doing armbian stuff for a few weeks.

I don't know what you could improve right now... But I know that LCD only receives data. My LCD works the same, with its MISO pin connected or disconnected.

Yes, that's a typo. The dc (data/command) should be PC7, and the MOSI (LCD's SDI) is PH7

Yes. Probably this week.

Is your LCD at least turning white on powerup? Did you connect the "LED" pin in the LCD, to 3.3V? Send a drawing of how you are connecting the LCD to the orange pi zero 3.

Thank you Pearo, What does "S/N" mean? I just ended up using my orange pi zero 3 gpio without the additional DTS, which made connector numbering available in the gpioinfo command... There were comments that made it sound not really necessary, and it was more work than I wanted to take on. The solution for me was: https://forum.armbian.com/topic/33800-orange-pi-zero-3-gpio/#findComment-181191 This was 2 years ago, and I haven't even thought about it, all this time.

I really hope that Orange Pi engineers learn to make Armbian patches, enter the community and give funding accordingly

Great I thought RiscV was still much slower than ARMs of similar prices.

I got surprised by "GPU: Mesa llvmpipe" ... but then I searched, and it means CPU rendering. But still very nice!

While it didn't give an solution, 👆 this is a good answer. It matches my concept of what armbian-build does, as I learned it 3 years ago (from reading the documentation and experimentation)

I just thought that a inserting a cpio file would be accepted, just like inserting a c file into the linux source code. I have never done a source file insertion myself, with neither C or cpio file... but I assumed it would work, since it is a common need for linux patches. In this page, they talk about the "--new-file" feature of the diff command https://unix.stackexchange.com/questions/37287/how-to-include-a-new-file-into-a-patch

Thank you guys for the work toward this RiscV SBC The website http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-RV2.html claims 130% faster than ARM A55 (which is 25% slower than my H618)... have you tested that? Are the USB, GPIO, SPI and MIPI DSI working? Are there any NPU examples provided by Orange Pi?

I missed the fact that you have an orange pi zero 2w... I think there's a success experience with that orange pi in this thread or in this Allwinner section. Please share if you have success

Hi Pami, I haven't had time to check your connection list and DTS. The LCD you showed is exactly the same I have I have both ili9486 and ili9488, and they work with the same connections, same DTS, same bin, same driver You should be able to copy all the wiring I describe in the DTS, the DTS, bin/txt and armbianEnv.txt line, and it should work. Start from a fresh self-built armbian OS, with the panel-mipi-dbi driver activated in the linux config phase.

A long time ago, I made an armbian guide, which included adding a kernel patch. Can you try this method? "Move them* to ~/armbian-2023.05/build/userpatches/kernel/archives/sunxi-6.1 (using the scp command or sshfs)" * would mean the cpio file (use diff3 to convert to patch file**) and any linux configuration patches needed to make your initramfs. ** diff3 linux_orig_source_folder linux_source_folder_with_cpio_file https://github.com/robertojguerra/orangepi-zero-full-setup/blob/main/README2.md#73-add-the-tv-encoder-driver-to-the-linux-kernel-source

If you don't have X11 or Wayland, try using the linux command "fbi" (frame buffer image). I think I put an example in this trhead or in the Banana Pi ili9341 thread (in this allwinner forum section).