-
Upcoming Events
-
-
Volunteering positions
-
Code reviewer
Position: Framework maintainerNumber of places: UnlimitedApplicants: 9
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
59
Full root filesystem encryption on an Armbian system (NEW, replaces 2017 tutorial on this topic)
One issue with Debian Trixie and encrypted root file systems is that they made some changes. There's an additional package you now need (in addition to cryptsetup-initramfs) prior to updating your initramfs so it will mount an encrypted root: systemd-cryptsetup Despite what this says, I had to install it manually. https://www.debian.org/releases/trixie/release-notes/issues.en.html#encrypted-filesystems-need-systemd-cryptsetup-package -
15
Separate boot partition and different root partitions → simple man’s A+B update possible?
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.- Helios 4
- Nanopi Neo 3
-
(and 1 more)
Tagged with:
-
4
-
0
RK3568 U-Boot Data Abort during DDR Init - Can't enter MaskROM after adding ilitek9881c MIPI DSI panel to Device Tree
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 -
3
Installing armbian on Yundoo Y8 TV box (RK3399)
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!
-
-
Member Statistics