Active threads

I've read that page and I can't seem to get it working with the image both jock and Victor Picinin recommended yet it doesn't boot off the eMMC nor the SD. I'm at the end of my rope!

I have burned the image "Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz" using Balena Etcher to an SD card, then put it in the box and the light is blue, but the screen is black. please help, thank you this is a photo of the board I used

I have experienced something similar in the past and it made me very puzzled until I figured out what was wrong in that situation. Make sure the clock on both systems are synchronized to an NTP server. IIRC SSH just threw a fit exactly like this without logging why, and it turned out to be a security feature where the ssh server suspected the communication to be intercepted by man-in-the-middle due to clocks not being synchronized. And if logging in physically to the system, apt refused to work as-well until clock was synced. Could be worth to check next time... As for dhcp and systemd. Check if systemd-resolved.service is messing something up for you, maybe try to disable it?

Actually not really strange but a measure for spam prevention.

We don't have intention to support this board without funding. However anyone from the community can step up and add support for it.

Hi, does this version of the S805 have HDMI and Wi-Fi? Could you explain more about this backup? Thank you.

So.... I am the winner of a Inovato Quadra4K from a drawing at my amateur radio club meeting. Yeah! Cool! It runs a software called HamClock automagically.... BUT WAIT! There is MORE! You can exit that app and run other applications... Providing you have a mouse & keyboard (because I am a native WinWeenie) or keyboard if you are a Linux forever personage. It also has a wireless interface that I would like to configure so it doesn't have to have an Ethernet tail tied to a port on our ISP router. I would rather it was mounted to a HDMI TV or monitor. So, I need the keyboard (and because I am a longtime WinWeenie and rodent dependent) mouse to reconfigure it. I would like to have it use a USB Logitech Unifier Nano dongle with wireless keyboard/mouse. By the way, the brilliant man that came up with this computer is trudging the same path I am, fighting cancer. His fight has gotten so tough he has shut down his company. I hope he gets better. Is there already a compiled binary for this with directions,,. or do I have to master the dark arts of programming routines, subroutines, interrupts, memory fetches, writes, threads and all that then compile it into something the machine understands? Please understand I didn't even take typing in high school, so college was a real bear.... When I was in high school Jobs and Wozniak were still dumpster diving behind Xerox-Park Corporation and Radio Shack. Any takers on this one? Thanks in advance, Dave, The-Other-One

Hi, I learnt how to customize the image, and also found a simpler way to achieve the bootstrapping alsaloop. Here is the forked repository and a pre-built image for you to try. Supposedly, you just need to flash the image, and it should work out of the box. As the radxa zero 3w does not have the Ethernet port, so you will not accenditally connect it to some networking, I think it is fine to leave the root password as the default. However, if you plan to connect the device to some networking, remember to set up the root password. The Wifi is also working with the latest kernel release (my wifi module is broken, but I do see dmesg is trying to interact with that module).

Hi, how are you? Well, I don't know English very well, so this text will be translated using Google Translate since I'm Brazilian. Anyway. I found a way to boot the SD card with Linux on the Allwinner H3 chip, using a Chinese MXQ 4K 5G TV box. I booted Android normally and, using the remote control, pressed the power button and then confirmed. After shutting down, I booted with the remote control and Linux started normally. After that, every time I booted with the SD card, it booted perfectly. Another thing I did before, but I believe it doesn't affect this, was to enable USB0 device mode in developer mode. I hope this information helps with your Linux projects!

your sbc has only 100mbit nic

@jockNow, I've finally solved this problem. Successfully flashed the latest version of armbian, https://github.com/armbian/community/releases/download/26.2.0-trunk.151/Armbian_community_26.2.0-trunk.151_Rk3318-box_noble_current_6.12.63_gnome_ desktop.img.xz Next, I will share my problem-solving journey. I found that I couldn't enter maskrom/loader mode anyway, and when I accidentally inserted the USB flash drive into the multitool.img into the TV box and powered it directly on, I found that it actually started the system directly in the USB flash drive. So I guess that it may have changed the boot order after flashing the loader.bin before, and the armbian system I flashed in before it continued to toss before it could be configured, probably because the system files of the root partition were corrupted, causing it to not boot normally. Therefore, I simply tried to flash the firmware of the rk3188-box in the official community directly into the USB flash drive, because after these images are flashed into the USB flash drive, there is only the root partition, that is, the system. And there is no boot partition. I guess the boot partition may have been written somewhere else, and I don't need to worry about it anymore. So, I plugged the USB flash drive into the latest rk3318 firmware into the box and waited for a few minutes after powering on it directly and starting it, it obtained the IP address assigned by my router DHCP, I was so excited, I quickly connected to the rk3318-box through SSH, and made the preliminary configuration. Quickly enter the command armbian-install and select item 2, and immediately write the system on the USB flash drive to emmc. After the writing is completed, turn it off, unplug the USB flash drive, power on, wait for a few minutes, and the startup is successful. It means that I have successfully flashed the phone this time. Thank you very much for your help. @jockand @fabiobassa, You're passionate and highly skilled.

I found the reason. (Different function of Pin 100) cm5-io: PCIe_PWR_EN rpi-cm4-io: nEXTRST used for USB hub reset With rpi-cm4-io and no pcie device, linux sets PCIe_PWR_EN=0 (turn off pcie) But rpi-cm4-io thinks that nEXTRST=0 (always reset usb hub) The temporary solution is: For the pause of compile, please turn on kernel config When kernel config appears, sudo vi ./cache/sources/linux-kernel-worktree/6.1__rk35xx__arm64/arch/arm64/boot/dts/rockchip/rk3576-armsom-cm5-rpi-cm4-io.dts Add the following fix in order to always turn on pcie vcc3v3_pcie0: vcc3v3-pcie0 { ... regulator-boot-on; regulator-always-on; enable-active-high; ... }; Because "sudo apt dist-upgrade" overwrites .dtb, make sure backup and restore. I do not know how the .dts is generated, so the patch can be made by an expert of Armbian.

To be honest I don't know how to do this and even more I am not sure in correctness of of my code in term of conventions. I mean that for example I add #define-s with names ES8388_xxx to header file ES8228 and so on.

URGENT: Kernel update already applied, bootloader points to 6.12.58! Current state: - Running: 6.12.44 - Boot configured for: 6.12.58 (symlinks updated) - usr-merge still broken (duplicate files in /bin, /sbin) Questions: 1. Should I revert boot symlinks to 6.12.44 immediately? 2. ODROID HC4 specific: Which file actually boots (Image vs vmlinuz)? 3. Will 6.12.58 boot with broken usr-merge? 4. Emergency procedure if forced to reboot? NOTE: I'm NOT taking any action until getting community advice.

The boot partition presence doesn't depend directly on the Armbian version—it's determined by the board configuration. Some configs enable an extra boot partition, especially for boards using older U-Boot versions that can't boot directly from ext4. As a result, even for the same board and Armbian version, different branches (e.g., legacy, vendor, current, edge) may behave differently. Vendor branch might use an old BSP U-Boot requiring the extra partition while mainline branch uses newer U-Boot that boots straight from ext4.

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 2eb2fd9cd (https://ryanfortner.github.io/box64-debs/) + proton-10.0-3-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/download/proton-10.0-3/wine-proton-10.0-3-amd64-wow64.tar.xz) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v2.4.1 30~60fps@720p (medium settings) box64 environment variables: Batman Arkham Asylum GOTY

I've never used any other method. I'd suggest using a search engine to search for other methods to "enable multi boot on amlogic TV box"

Hi @ff255, Can you try with the following changes/additions to armbianEnv.txt: # previous load addresses # fdt_addr_r=0x01f00000 # kernel_addr_r=0x02000000 # ramdisk_addr_r=0x04000000 # new load addresses fdt_addr_r=0x01f00000 kernel_addr_r=0x02000000 ramdisk_addr_r=0x04400000 # new kernel_addr_r is aligned to 2MiB boundary # new ramdisk_addr_r is aligned to 2MiB boundary - not really neccessary afaik but "why not both?" Quick calculation below: edit: updated the sheet and put the correct numbers here Groetjes,

Heya, Of interest to anyone encountering the 2025 AIC8800 WiFi and Bluetooth hardware, and who is using Buildroot; this is the package that builds and installs everything into a Home Assistant image. Of academic interest in the present discussion also, offering minor suggestions in dts and service file. The build process may be portable? 👽 aic8800.zip

Hello Everyone, I've seen a few threads on these boards but wanted to create a centralized source for information. It's my understanding there are multiple variants of these boards, the one I have and used is IK316Q-EMCP_V4.1 I know there are other versions without UART ports, mine was lucky enough to have them. To build this image (adjust the compile command to your liking) git clone https://github.com/sicXnull/armbian-build cd armbian-build git checkout MXQ-PRO ./compile.sh build BOARD=mxqpro-h313 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED= DESKTOP_ENVIRONMENT=cinnamon DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base EXPERT=yes KERNEL_BTF=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm Prebuilt Images Armbian-unofficial_26.02.0-trunk_Mxqpro_bookworm_current_6.12.65_cinnamon_desktop.img Armbian-unofficial_26.02.0-trunk_Mxqpro_bookworm_current_6.12.65_minimal.img Unfortunately this board was already flashed with MiniArch by the time i got it, so i was unable to get the original DTB. Therefore, wifi does not work Is someone able to get the DTB from this board so we can get wifi working?

Bit late to the thread, but just a heads up. Been reading this thread and saw the DTS with the connector numbering. So I went to the manual to check the pinout and the pin number is listed as GPIO S/N. Just thought I would add to the thread.

Have uploaded a new "edge" image for RV2 for testing. This time, wifi works. "current" image is the same. If you want to test, go to https://privat-in.de and grab Downloads. If you want to compile, clone https://github.com/sven-ola/armbian-build/tree/orangepi-rv2 and run Edit: forget to activate Mediatek wifi drivers as well. Also merged current Armbian/main. Uploaded again. LG // Sven-Ola

ah yes, you're right. Well homassistant seems to depend on docker, so if the docker issue is resolved, hass will probably work too. Though no clue what the issue with docker is. Since it is an issue with configng, I suggest to report directly here: https://github.com/armbian/configng/issues Don't forgot to be as verbose as possible when reporting. Will raise chances getting it addressed sooner

How to get this working on your Raspberry Pi (5) Hello all. Thanks again, @MMGen, for offering this fantastic tutorial. As mentioned before, it was the foundation for me to encrypt my Raspi 5, although the tutorial wasn't intended for that. I hat to make the some adjustments to get it working. But first some reasoning. What's the difference? The Armbian image for Raspi comes with two partitions: FAT32 for booting ext4 as a root Out of the box it already resembles the result that we try to achieve. I assume that this is due to the different booting process of a Raspi compared to other sige-board computers. Download the desired image from: https://www.armbian.com/rpi4b/ https://mirrors.dotsrc.org/armbian-dl/rpi4b/archive/ → more images (I only tested my approach with the minimal Trixie image, kernel version 6.12.41 to .58, and would be delighted to know if somebody also got it working with other derrivates.) Changes to the original tutorial: Basically I followed the tutorial (versions Oct 25 to Jan 26) except for the steps below where I had to make some adjustments. If the original tutorial receives major updates (e.g. in its structure) please consider that, as I might not keep this post up to date. Step 6: As the type of the boot partition needs to be FAT32 instead of ext4, in fdisk change the partition type (hit t) to FAT32 (0b or just b in the partition list l). I also adjusted the size of this partition to +1G, just in case, but that shouldn't make a difference. Here's final partition table: Device Boot Start End Sectors Size Id Type /dev/<your-drive>p1 8192 2105343 2097152 1G b W95 FAT32 /dev/<your-drive>p2 2105344 3907029167 3904923824 1.8T 83 Linux I'm using an NVME drive instead of a SD card. I guess that won't make a difference. I always repaced sda with nvme0n1 when I followed the tutorial. I also increased p1's size to a whole GB, just to be sure. Step 7: mkfs -t vfat /dev/<your-drive>p1 # NOT: mkfs.ext4 /dev/<your-drive>p1 # e2label /dev/sda1 CRYPTO_BOOT won't work on FAT32 partitions Step 8: Because there is no label on the FAT32 partition, just link it manually: BOOT_PART=/dev/<your-device>p1 In my image, the resolv.conf was already present and symlinked to /run/systemd/resolve/stub-resolv.conf. I had to rename it to etc/resolv.conf.old and only then did: cat /etc/resolv.conf > etc/resolv.conf Step 9: Now it gets a bit hairy. As already explained, the Armbian Raspi image works a bit differently. It holds the following partitions: P1: is the boot partition. During (or after?) the boot process it will be mounted to P2:/boot/firmware. P2 contains a cmdline.txt (content covered below) which is the config file to make the adjustments from Step 9.1 for the boot partition. P2: is our root partition. P1:/boot does contain an armbianEnv.txt but that is not the config file used during the initial boot process for the unlocking system . Step 9.1: At this point in the tutorial P2 is mounted to root/boot, so you can nano boot/cmdline.txt and change its content to: console=serial0,115200 console=tty1 loglevel=1 root=/dev/mapper/<custom-name-or-rootfs> rootdev=/dev/mapper/<custom-name-or-rootfs> rootfstype=ext4 fsck.repair=yes rootwait logo.nologo cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory I was hesitant to make further changes besides the root and rootdev entries or break the line but probably that's also feasible. Step 9.2: Skipped. Step 9.7: As the boot partition is FAT32, etc/fstab has to know about it too. Also notice that commit=600 results in a failure to mount it to /boot/firmware after unlocking and rebooting (took me days before I could plug a display to my Raspi, read the boot log and figure out that line as the source of failure). Therefore I deleted the commit declaration. /dev/mapper/<custom-name-or-rootfs> / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 UUID=<BOOT_UUID> /boot/firmware vfat defaults,noatime,nodiratime,errors=remount-ro 0 2 tmpfs /tmp tmpfs defaults,nosuid 0 0 Step 10: Add systemd-cryptsetup (when using Trixie or higher) to the install list in the chroot (thanks to @The Tall Man for mentioning; automatic install worked for me btw). apt --yes install systemd cryptsetup cryptsetup-initramfs dropbear-initramfs In principle that should be it and i just followed the rest of the tutorial. But after the initrd.img got generated I always had to make adjustments, after which I had to recreate it. update-initramfs is always suspiciously fast so I just used the approach from this tutorial: KERNEL_VERSION=ls /lib/modules/ echo "CONFIG_RD_ZSTD=y" > /boot/config-$KERNEL_VERSION # to use the right decompression method mkinitramfs -o /boot/initrd.img $KERNEL_VERSION rm /boot/config-$KERNEL_VERSION # remove the config If you want to keep the original initrd.img as a backup you can just copy it before running the above commands but of course it won't be work with our encrypted boot. You can give the .img output file a different name. Don't forget to change the line initramfs initrd.img followkernel in boot/config.txt accordingly. Don't forget ssh-keygen -A. That's it Please let me know how if it worked for your Raspi. Good luck. @MMGen: If you find this sub-tutorial helpful enough, please consider to link it in your original post or feel free to incorporate it. It took me quite some days to figure out all the necessary changes and borow from other sources. Would be nice to spare others and this thread is a top rank in search engines. As you can see I used a name other than rootfs as my device name – the ability to change that could be a nice feature for the next version of your script Cheers!