robertoj

Advanced users - Development · Tuesday at 06:28 PM

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.

Tuesday at 03:39 AM

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!

February 9

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/

February 5

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.

February 5

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

February 3

14 hours ago, BoringName said:

I got emby installed and working. Made it launch with the ir remote, it was all perfect until I tried to play a video

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

February 3

16 hours ago, BoringName said:

edit: Ok the instructions in that post did actually work, I just didn't notice one of the commands had not run properly when I first tried it. Video playback in mpv is buttery smooth, now I just need to figure out how to get emby to do the same.

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.

February 2

On 1/31/2026 at 3:45 AM, jock said:

the problem is not ffmpeg, which already is works totally fine on debian Trixie (and backwards), the problem is within mpv that changed in v0.4.0 carried by debian Trixie, and at the moment I don't have enough motivation to carry on a custom mpv package for Debian Trixie.

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

January 30

There was a successful test with Debian Forky in RK3566

On 11/18/2025 at 2:36 AM, usual user said:

Backporting is possible, but you will have to deal with the consequences yourself that arise from your outdated versions lacking the functions required for your backport, and you may need to backport those as well.

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

January 22

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

January 22

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.

January 22

Yes, that's a typo.

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

January 21

Yes. Probably this week.

January 21

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.

January 19

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.

January 19

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

January 16

23 hours ago, sven-ola said:

I operate an Odroid HC4, that has 4 x A55@1.8 and the board discussed here has 8 x X60@1.?. A fast sysbench says: single thread on OpiRv2 is slower (792 vs 1034) , multithreaded is faster (6342 vs 4151). Compiling a current kernel on RV2 needs 3 hours, nothing one would do do regularly. If you really need speed buy a Radxa Rock 5 (see platinum support devices on this site).

Edit1: NPU -> Opi Wiki, USB and SPI yes, for MIPI DSI/CSI you need to test yourself.

Edit2: Just remembered that I have a H618 (Opiz3). Single=708, Multi=2828 with the same Trixie sysbench.

HTH + LG // Sven-Ola

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

January 16

:thumbup:

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

Advanced users - Development · January 16

On 1/8/2026 at 8:19 AM, Andrew Routley said:

Armbian’s build process is designed to be "clean." When you run it inside Docker, it follows a strict sequence:

Step A: It prepares the environment.
Step B: It runs a "cleanup" on the kernel source to ensure no "junk" from previous builds exists (this deletes your .cpio file).
Step 😄 It checks your .config and starts the make command.

Because Step B happens every time you start the build, any file you manually copy into the kernel tree gets deleted seconds before the compiler actually looks for it. That is why you kept seeing No rule to make target.

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) :thumbup:

Advanced users - Development · January 16

13 hours ago, Andrew Routley said:

Nevertheless, if you think I can create a patch from the cpio file, please give me detailed instructions and I'll try it again--- maybe I did something wrong?

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

January 15

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?

January 14

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

January 14

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.

Advanced users - Development · January 13

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

January 12

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

Sign In

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by robertoj

Important Information