going

Can you explain what these numbers mean? And what alternative can they be compared with? It seems to me that this is probably a wrong translation.

In fact, I found a lot of problems, these two were not on my list. The build system does some steps more correctly, but this utility lags behind. I think we need to teach her how to split empty space into sections and mount it the way the user wanted. The work is slow, but it is progressing.

Thank you very much. I collect in a notebook all possible bugs when using this utility. I want to redo it.

Can you describe the selection scenario (order) in the "armbian-install" interface?

I wonder if the source codes for this loader exist?

There are several ways to force a WIFI-USB device to be detected in the OS. You can write and add a node to the DTS. That is, to use an overlay. You can write a rule and add it to the initialization scripts. Or a combination of these methods. Please reach out to people who have already succeeded in this. There are publications on this topic here on the forum.

Everything is set.

These three packages must be installed. Then reboot.

Just this command. You have already install the headers.

@JOHAN VAN DER MERWE Today, when I reread what I wrote for you, I realized that I was wrong. I did not understand your level of knowledge of Linux commands and the ability to use the system help. I apologize. Now again and in order: filename.gz - The gzip archive and the command of the same name for operations with files of this archiver. Team Help: gzip --help Extract files from the archive: gzip -dk filename.img.gz Unzip, that is, the files will be extracted from the archive and the archive will be deleted: gzip -d filename.img.gz zcat - Uncompress FILEs to standard output. The output of this command is used as the input for another command: zcat filename.img.gz | another-program For some reason, I thought that's what you need. filename.img.gz - This always implies the path to the file. You seem to have figured out the dpkg command. You don't have to install this file: linux-libc-dev-edge-rockchip_24.11.0-trunk_armhf__6.11.4-S1736-D29ea-P86b9-C85f2H5c21-HK01ba-V014b-Ba3b7-R448a.deb For you, the difference between the system package and this one doesn't matter. With respect

NOT sudo

The download commands are executed on behalf of a regular user. wget -r -l 1 --accept=deb -np https://fi.mirror.armbian.de/.testing/rk322x-box mkdir debs mv fi.mirror.armbian.de/.testing/rk322x-box/* debs/ rm -rf fi.mirror.armbian.de ls debs Execute sequentially line by line.

And you try to do it and see the result !!! Download packages directly on the board: wget -r -l 1 --accept=deb -np https://fi.mirror.armbian.de/.testing/rk322x-box .... mkdir debs mv fi.mirror.armbian.de/.testing/rk322x-box/* debs/ rm -rf fi.mirror.armbian.de ls debs There will be 4 files in the directory: linux-dtb-edge-rockchip_24.11.0-trunk_armhf__6.11.4-S1736-D29ea-P86b9-C85f2H5c21-HK01ba-V014b-Ba3b7-R448a.deb linux-headers-edge-rockchip_24.11.0-trunk_armhf__6.11.4-S1736-D29ea-P86b9-C85f2H5c21-HK01ba-V014b-Ba3b7-R448a.deb linux-image-edge-rockchip_24.11.0-trunk_armhf__6.11.4-S1736-D29ea-P86b9-C85f2H5c21-HK01ba-V014b-Ba3b7-R448a.deb linux-libc-dev-edge-rockchip_24.11.0-trunk_armhf__6.11.4-S1736-D29ea-P86b9-C85f2H5c21-HK01ba-V014b-Ba3b7-R448a.deb sudo dpkg -i filename.deb

Yes of course! You can also redirect the output of a command to the input of another command.

zcat --help zcat file-name.img.gz

This is an incorrect package name. Valid: linux-image-${BRANCH}-${LINUXFAMALY} BRANCH -> legacy,current or edge LINUXFAMALY -> sunxi,sunxi64,rockcip-rk3588 ... Example: leo@bananapif3:~$ echo "$(LC_ALL=C apt search linux-image | grep install)" ... linux-image-legacy-spacemit/now 24.11.0-trunk riscv64 [installed,local] And search headers: leo@bananapif3:~$ echo "$(LC_ALL=C apt search linux-headers-legacy-spacemit)" ... linux-headers-legacy-spacemit/noble 24.8.2 riscv64 Armbian Linux legacy headers 6.1.15-legacy-spacemit Please note that the version of the installed kernel and the version of the headers available from the repository do not match. That's because I built the core myself. And now the headlines are my problem.

This trace is intended mainly for developers of the build system itself. There is no information about the compilation error itself. Use the command to view: grep -Ei 'warn|err|\|' output/logs/log*.log.ans | batcat Or a black and white version for printing: grep -Ei 'warn|err|\|' output/logs/log*.log And publish only the lines that relate to the error.

I have a similar situation with bananapi-m3. When I connect the hdd using a USB-SATA adapter, the disk is first detected, and when accessing it, it suddenly disappears. But I know exactly the reason for this behavior, since I worked with a soldering iron with this device. The disk consumes 2.5 amps, and USB can give much less. I do not know if this message of mine can help you.

If you do on this device: fdisk -l Will the kernel see a block device for SPI flash? Do I understand correctly that the OS is running a common core from the OS vendor?

I think I've misled you. For some reason I thought you wanted to add the whole node. But you want to replace it with the same one but without the PI16 pin. It's not in my power. I don't have this board to check. I apologize.

Everything is right. It is this partition (from a USB drive) that the script is trying to mount into the future root file system. There's something wrong here.

Simply insert the USB drive from which the installation was performed into the connector on the running device and output the command: echo "$(fdisk -l | grep 'EFI')" That's all for now.

Don't rush to a conclusion. If you check your first configuration before installation, you should see for the echo "$(fdisk -l | grep 'EFI')" command: /dev/sda1 8192 532479 524288 256M EFI System And after installation: (Or just insert the USB flash drive from which the installation was done) /dev/sda1 8192 532479 524288 256M EFI System /dev/nvme0n1p1 2048 411647 409600 200M ef EFI (FAT-12/16/32)

Can you expand on this? I have it working on another opi5+ running armbian right now: @ozacas If it doesn't bother you, could you post the output of the "fdisk -l" command under the spoiler for your device? I have a suspicion that the script does not analyze correctly if EDK2 is used.

Just stay tuned. Will be included in the kernel version v6.6.54 or later