All Activity

Ah yes indeed. I meant laibsch. Sorry. I made an autoRevert.sh POC that hooks into the initramfs system. Assuming the partition layout described above the following script will revert to the other partition. It is assumed that if an update happened the updater will place a testBoot1 file inside the new boot directory and reboots. During initrd time the script will check for that file and rename it to testBoot2. If the script already detects a testBoot2 it will change the symlink of /boot to the other partition and reboots. Otherwise it is assumed that once the system is up testBoot2 is deleted from the running system if everything works. The script needs to be placed into /etc/initramfs-tools/scripts/init-premount/ and busybox needs to be installed as the script needs the more sophisticated basic commands. Then rebuild initrd. #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" if ! dpkg -s busybox>/dev/null 2>&1; then >&2 echo "Busybox not installed." exit 1 fi } case $1 in prereqs) prereqs exit 0 ;; esac reboot=0 echo mkdir /run/bootRevert mount /dev/mmcblk0p1 /run/bootRevert if [ -L "/run/bootRevert/boot" ]; then echo "/boot is a symlink. OK." cd /run/bootRevert currentTarget=$(readlink "boot") if [ -f "boot/testBoot2" ]; then echo -n "Reverting " if [ $currentTarget = "bootA" ]; then echo "to bootB." if [ -f "bootB/armbianEnv.txt" ]; then rm boot/testBoot2 ln -snf bootB boot reboot=1 else echo "Aborting revert. bootB seems to be empty." fi fi if [ $currentTarget = "bootB" ]; then echo "to bootA." if [ -f "bootA/armbianEnv.txt" ]; then rm boot/testBoot2 ln -snf bootA boot reboot=1 else echo "Aborting revert. bootA seems to be empty." fi fi else if [ -f "boot/testBoot1" ]; then echo "Going to testboot stage 2." mv boot/testBoot1 boot/testBoot2 else echo "No revert/testboot detected. Booting $currentTarget normally." fi fi fi cd / umount /run/bootRevert if [ $reboot = "1" ]; then sync echo "Rebooting..." reboot -f fi It seems then this concept works. As the script checks if /boot in the boot partition is a symlink and then does nothing if not it can also be placed in an unchanged armbian system without interfering. Perfect for creating new images. Still missing are the management scripts for: - converting an initially downloaded armbian image into an AB boot partition scheme - creating an image/update package from a running and well prepared or updated local armbian installation - a cronable management script to call a more specific download script and for switching partitions and rebooting - the download script that will attach to any distribution system that downloads the new update package places it into the other partition and adjusts machine identity; this download script could also just implement a backup of the running partition to the other partition so that switching back is possible if OTA is done using apt All of these can be done in shell.

Board say Orange Pi 5 V1.2

Hi , I am unable to boot my RK3568 board and cannot get it into MaskROM mode for recovery. The boot process fails with a "Synchronous Abort" in U-Boot SPL during DDR initialization. The device gets stuck in a boot loop. It starts DDR training (`ddrconfig:0`) but fails with a Data Abort exception. Standard methods to enter MaskROM /Loader have not worked. I have attached the full serial log (Boot_log.txt). Any guidance would be greatly appreciated. Thank you. Boot_log.txt

ohh I see. Anyways I can't seem to make it detectable by the Windows RKDevTool, I turn the maskrom mode correctly but then all of the commands fail. It really sucks to have a device this powerful and not being able to do anything because of those crappy dtb files. Thank you anyways!

@fabiobassa Not work, I did wrongly or something. The rk322x image didn't have this ap6330 dtb overlay, so I pull it from another armbian image

No, the support for rk3399 is quite good. The problem is that each box/board needs someone to develop a device tree (dtb) for that box/board and each is different depending on the specifics of that box/board. That is what is lacking to support your box. (and if your box has obscure hardware on it, then those drivers may also be lacking)

I have the same Android TV, and I've been trying to boot Armbian but I don't seem to successfully accomplish it. I believe we are all alone with this, and nobody will ever help us. Maybe RK3399 SoC is still problematic after 9 years.

@tofamus30 You said box Is 322x You said wifi Is 6330 But then you tried dtbo from 3318 board Not sure if is gonna work

Are u kidding me? This is freaking awesome Thanks guys, I will be patiently waiting..

R76S will be supported, but its too early at this stage. We setup download page https://www.armbian.com/nanopi-r76s/ but no images yet.

Thank you for the advice @MattWestB, But I already tried all available LED-config options, booting fine, but none working

Oh right, I forgot about that. Luckily the rk3576 is already maturing in the Linux kernel. In that case we will just hope for the best. Thank you for your time. edit: Could this topic be moved to https://forum.armbian.com/forum/176-other-families/

Try different LED-config then its also changing the hardware for the SD-Card interfaces = WiFi module but prepare that it can ending with not booteball system.

Probably marking on the board is the only what really matters.

Armbian does not accept new boards for official support unless there is funding involved. However anyone from the community can step up and add it as community-supported.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Hi guys, I would like to make a support request for the: NanoPi-R76S ($49): https://www.friendlyelec.com/index.php?route=product/product&product_id=308 Thank you for considering. Dantes

Finally there is a proper tor-browser available for arm64/aarch64: 1. Goto https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds/ 2. Navigate into: tbb-nightly.<date>/nightly-linux-aarch64/ 3. Download tor-browser-linux-aarch64-tbb-nightly.<date>.tar.xz 4. Unpack with tar -Jxvf and run tor-browser/start-tor-browser.desktop Yay! (I'm sure you can compile it too from their github page)

Hey, has anyone tried using the BPI-3C1-27? Just wondering about price and if it’s really in stock.

I made a configuration via armbian-config, but the camera does not work, here are the messages /sys/bus/i2c/drivers/ov13855 3-0036 bind uevent unbind sudo i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- UU -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- 58 -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- dmesg | grep ov13855 [ 14.074752] platform csi2-dphy0: Fixed dependency cycle(s) with /i2c@feab0000/ov13855-1@36 [ 14.338234] ov13855 3-0036: driver version: 00.01.04 [ 14.338301] ov13855 3-0036: Failed to get power-gpios, maybe no use [ 14.338330] ov13855 3-0036: Looking up avdd-supply from device tree [ 14.338336] ov13855 3-0036: Looking up avdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338365] ov13855 3-0036: supply avdd not found, using dummy regulator [ 14.338418] ov13855 3-0036: Looking up dovdd-supply from device tree [ 14.338424] ov13855 3-0036: Looking up dovdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338434] ov13855 3-0036: supply dovdd not found, using dummy regulator [ 14.338454] ov13855 3-0036: Looking up dvdd-supply from device tree [ 14.338459] ov13855 3-0036: Looking up dvdd-supply property in node /i2c@feab0000/ov13855-1@36 failed [ 14.338468] ov13855 3-0036: supply dvdd not found, using dummy regulator [ 14.338484] ov13855 3-0036: could not get default pinstate [ 14.338487] ov13855 3-0036: could not get sleep pinstate [ 14.348869] ov13855 3-0036: Detected OV00d855 sensor, REVISION 0xb0 [ 14.863602] ov13855 3-0036: Consider updating driver ov13855 to match on endpoints [ 14.863609] rockchip-csi2-dphy csi2-dphy0: dphy0 matches m00_b_ov13855 3-0036:bus type 5 with the original distribution the camera works

I checked armbianEnv.txt and it says rockchip5, to triple check, I checked the site I bought it from, also says 5. So I believe I mislabeled the post as 5b, but it is a 5.

Search my threads with keyword "ili9341". Post a photo of your wiring, a schematic, and what did you try within armbian... in this thread.

This is similar to physical damage to the SD card

Those are standard kernel patches. Do you mean Armbian build system does not support multiple patches in a single file? If so, you can download each of the 14 patches individually and then apply them. Or you can try reformatting the combined patch file as a single patch.

I gave this a try but no success. The structure of original source code doesn't match the one for armbian. It would be great if you could make a patch as in this link