All Activity

Do you perhaps know how we could integrate this into Armbian? I don't know much about Gnome internals - came this far: https://github.com/armbian/build/blob/main/config/desktop/common/environments/gnome/debian/postinst

I was thinking the same. Must soldering the TTY cosolle so can getting the Uboot messages. The eMMC is the flash dead and have one Armbian on the SD-Card for jump starting the USB-SSD but the device used is only the USB-SDD i the demesg and it shall writing other devices if not booting one the USB-SSD and its the right one then HA is current and on the SD-Card is not updated. Shall i rewriting the bootloader on the USB-SSD but it shall being updated for some mouths ago ?

Hi, yes, I agree, but I am only a user of Armbian and I do not have such skills to do this solution you suggest I can check the available Community Releases of Armbian and check how it works. Community editions, which are issued for testing and updated on average every week?

I second btrfs. I second-guess running bittorrent off SD cards.

@TRay Best way to find out is to change and recompile your own image, then you will know. After that, push a PR so everybody can profit from your work.

In addition to what Werner said, I would like to point to the option of not installing recommended packages. "sudo apt install --no-install-recommends lxqt". Personally, i like to use aptitude for package management for more control and transparency.

Yes, followed the guide you linked on the other thread. Here is my dts. sun50iw9.dts

@dale there’s a new patch to fix boards without external 32k clock. I haven’t tested it yet. https://github.com/warpme/minimyth2/commit/728a14a73924e349fe88fb4def7e5f50a79aed5c

@mdidisDid you compile with the secure boot patch? Because it sounds like that’s your issue. If secure boot is not enabled you won’t get any output from your serial interface. post your dts. I’ll tell you the correct gpio for wifi and emmc.

@Ducdanh Nguyen hard to tell. I don’t see any markings for uart. It’s not going to be easy to debug your board.

@MattWestB According to /boot, your box should boot 6.16. I don't know though if you have other eMMC/sd/USB devices which may interfere

https://wiki.debian.org/LXQt

I’m trying to set up a lightweight desktop environment on Armbian Trixie. When I use tasksel, it installs a lot of extra packages, including GNOME. How can I install LXQt manually?

Thanks for the feedback. I'll research the tips further in the future. I'm not familiar with Linux and Armbian. I spent a lot of time in the past understanding the issues that occurred here. I'd like to be able to leave OP2 on 24/7h if necessary, like OP1, without worrying about a power outage. But Open Media Vault, Docker, Bittorrent, must perform frequent reads and writes to the SD card, and I have bad memories of it, with the system failing to boot up several times.

Have don apt-get update and grade. Armbian-config disabling firmware update = freeze kernel. apt-mark showhold linux-dtb-current-rockchip64 linux-image-current-rockchip64 dpkg -i on dtb and image. sync and reboot and the box rebooting OK with old kernel (3 times) !! CLI printout from kernel install: root@RK3318-Box-Orange:~# dpkg -i linux-image-edge-rockchip64_25.11.0-trunk_arm64__6.16.0-S038d-D0b5d-Pa674-Cb487H3d80-HK01ba-Vc222-Bd200-R448a.deb (Reading database ... 74668 files and directories currently installed.) Preparing to unpack linux-image-edge-rockchip64_25.11.0-trunk_arm64__6.16.0-S038d-D0b5d-Pa674-Cb487H3d80-HK01ba-Vc222-Bd200-R448a.deb ... Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'prerm' starting. Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'prerm' finishing. Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'preinst' starting. Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'preinst' finishing. Unpacking linux-image-edge-rockchip64 (25.11.0-trunk) over (25.11.0-trunk) ... Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postrm' starting. Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postrm' finishing. Setting up linux-image-edge-rockchip64 (25.11.0-trunk) ... Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postinst' starting. * dkms: autoinstall for kernel 6.16.0-edge-rockchip64 was skipped since the kernel headers for this kernel do not seem to be installed update-initramfs: Generating /boot/initrd.img-6.16.0-edge-rockchip64 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.16.0-edge-rockchip64 Image Name: uInitrd Created: Thu Aug 14 15:40:18 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 25341844 Bytes = 24747.89 KiB = 24.17 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.16.0-edge-rockchip64 to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.16.0-edge-rockchip64' update-initramfs: Armbian: done. Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.16.0-edge-rockchip64' Armbian: Debian compat: linux-update-symlinks install 6.16.0-edge-rockchip64 boot/vmlinuz-6.16.0-edge-rockchip64 Armbian 'linux-image-edge-rockchip64' for '6.16.0-edge-rockchip64': 'postinst' finishing. root@RK3318-Box-Orange:~# sync root@RK3318-Box-Orange:~# reboot Is i doing something wrong then it was i remember how to do offline kernel up and down grade ?? Have double checking its the right USB-SSD and not the SD-Card for all try. fdisk -l Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors Disk model: SSD PLUS 480GB df -h /dev/sda1 436G 19G 414G 5% / List of /boot/ root@RK3318-Box-Orange:~# ls -la /boot/ total 186536 drwxr-xr-x 4 root root 4096 Aug 14 15:40 . drwxr-xr-x 23 root root 4096 Aug 1 16:59 .. -rw-r--r-- 1 1004 1004 365 Aug 14 15:40 armbianEnv.txt -rw-r--r-- 1 root root 1536 Nov 30 2023 armbian_first_run.txt.template -rw-r--r-- 1 root root 38518 Nov 30 2023 boot.bmp -rw-r--r-- 1 1004 1004 3180 Nov 30 2023 boot.cmd -rw-rw-r-- 1 root root 3252 Nov 30 2023 boot.scr -rw-r--r-- 1 root root 258998 Jul 14 17:06 config-6.12.38-current-rockchip64 -rw-r--r-- 1 root root 263963 Aug 13 17:16 config-6.16.0-edge-rockchip64 lrwxrwxrwx 1 root root 26 Aug 14 15:38 dtb -> dtb-6.16.0-edge-rockchip64 drwxr-xr-x 3 root root 4096 Jul 16 14:39 dtb-6.12.38-current-rockchip64 drwxr-xr-x 3 root root 4096 Aug 14 15:38 dtb-6.16.0-edge-rockchip64 lrwxrwxrwx 1 root root 30 Aug 14 15:40 Image -> vmlinuz-6.16.0-edge-rockchip64 lrwxrwxrwx 1 root root 33 Aug 14 15:20 initrd.img -> initrd.img-6.16.0-edge-rockchip64 -rw-r--r-- 1 root root 25352236 Jul 16 14:44 initrd.img-6.12.38-current-rockchip64 -rw-r--r-- 1 root root 25341844 Aug 14 15:40 initrd.img-6.16.0-edge-rockchip64 lrwxrwxrwx 1 root root 37 Jul 16 14:40 initrd.img.old -> initrd.img-6.12.38-current-rockchip64 -rw-r--r-- 1 root root 0 Aug 14 15:40 .next -rw-r--r-- 1 root root 5618205 Jul 14 17:06 System.map-6.12.38-current-rockchip64 -rw-r--r-- 1 root root 5756639 Aug 13 17:16 System.map-6.16.0-edge-rockchip64 lrwxrwxrwx 1 root root 30 Aug 14 15:40 uInitrd -> uInitrd-6.16.0-edge-rockchip64 -rw-r--r-- 1 root root 25352300 Jul 16 14:44 uInitrd-6.12.38-current-rockchip64 -rw-r--r-- 1 root root 25341908 Aug 14 15:40 uInitrd-6.16.0-edge-rockchip64 lrwxrwxrwx 1 root root 30 Aug 14 15:20 vmlinuz -> vmlinuz-6.16.0-edge-rockchip64 -rw-r--r-- 1 root root 38277632 Jul 14 17:06 vmlinuz-6.12.38-current-rockchip64 -rw-r--r-- 1 root root 39352832 Aug 13 17:16 vmlinuz-6.16.0-edge-rockchip64 lrwxrwxrwx 1 root root 34 Jul 16 14:40 vmlinuz.old -> vmlinuz-6.12.38-current-rockchip64 First line in dmesg -T: [Thu Aug 14 15:33:40 2025] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [Thu Aug 14 15:33:40 2025] Linux version 6.12.38-current-rockchip64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #1 SMP PREEMPT Mon Jul 14 14:02:59 UTC 2025 The install is noble: /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.5.1 for RK3318 Box running Armbian Linux 6.12.38-current-rockchip64 Packages: Ubuntu stable (noble) Support: DIY (community maintained) Any creative / constructive thinking ??

@Nick AMay i ask you a question? If yes , why wont my boxtry and boot on that amrbian image? I plugged in and it should detetct and boot to the sd card right?

I don't know, but what you describe is that OP1 is essentially able to run from RAM (network I/O mainly) so not so much storage I/O which then lowers the change of corruption. For OP2, is quite heavy disk I/O it seems, also torrents writing is tricky for some filesystems. If you want to know more why and how w.r.t. corruption, use Btrfs instead of Ext4. It still can be difficult if HW caches do the wrong thing, but you can make metadata duplicate and also play with commit time. I have a Pi3B running from SD-card and 4T 3.5i HDD via USB attached. It runs Debian Testing (Trixie now) , FAT bootfs and Btrfs rootfs with hourly snapper and also manual extra snapshots if I do upgrades. Also HDD is Btrfs formatted, 'dup' profile for metadata 'single' profile for data. I gets hard power cut every day at least once as solar powered. I do not do any UPS like noticing, also the power loss might be during a btrfs send|receive transfer, that will then fail, but in my script I delete read-write snapshots first as they should be read-only (so were correctly finished). No data loss or corruption during years. I just have a very simple guess about the amount of sunlight, which might be almost zero for days in winter. On a Pi2B that seems to have damaged GPIO pin 4 and was using a bad brand SD-card, I could quite perfectly see when corruption started, which files you see when you do scrub. It was a logfile and some other file that were recently written, but unimportant, so I could still do a btrfs send of a snapshot of the rootfs to my local laptop new SD-card. I know how to create bootfs for Raspberries. For my NanoPi-NEOs running Armbian I changed rootfs Ext4 into bootfs Ext4 + rootfs Btrfs. You can also use Armbian build to generate that off-the-shelf, I would now use FAT for bootfs as that matches how UEFI computers are organized. You also need extra write of U-Boot, that is not needed for RPi or UEFI. An Ext4 filesystem can be turned into Btrfs in-place with tool btrfs-convert. If it is a rootfilesystem where the OS runs from, you still need to create an extra bootfs though and so also change fstab and also as a consequence the partition table and organisation.

Normally not if you have a recent distribution. Beware not to test that kernel in a box that does something useful though!

Thanks @jock i shall trying it later then i have moving some test HA from that box (one of the 2 with faulty eMMC). Is the libc-dev also needed or optional then installing the kernel files ?

@MattWestB@Thiên Thư Lục In this directory I have put an experimental kernel with a kernel patch that should fix some USB3 issues. If may want to try and experiment if it works for you. It is based upon kernel 6.16. You only need to install the image and dtb packages, headers are only if you need to compile some thirdy party drivers.

Thanks. I have tried and compiled image, but when I boot with SD card nothing appears, and Serial interface seems that disconnects. I have tried both with "uboot" button pressed and not. These are, I think, the gpio you asked gpio_encrypt { compatible = "allwinner,gpio_encrypt"; gpio_number_sun = <0x05>; gpio1_value = <0x00>; gpio2_value = <0x01>; gpio3_value = <0x01>; gpio4_value = <0x01>; gpio5_value = <0x01>; gpio1_pin = <0x53 0x08 0x0d 0x01 0xffffffff 0xffffffff 0x00>; gpio2_pin = <0x53 0x08 0x09 0x01 0xffffffff 0xffffffff 0x00>; gpio3_pin = <0x53 0x08 0x01 0x01 0xffffffff 0xffffffff 0x00>; gpio4_pin = <0x53 0x07 0x06 0x01 0xffffffff 0xffffffff 0x00>; gpio5_pin = <0x53 0x07 0x07 0x01 0xffffffff 0xffffffff 0x00>; status = "okay"; linux,phandle = <0x17d>; phandle = <0x17d>; }; or these ones? boot_init_gpio { device_type = "boot_init_gpio"; status = "okay"; gpio0 = <0x53 0x08 0x0b 0x01 0xffffffff 0xffffffff 0x00>; gpio1 = <0x53 0x08 0x0c 0x01 0xffffffff 0xffffffff 0x01>; gpio2 = <0x53 0x08 0x0e 0x01 0xffffffff 0xffffffff 0x00>; };

So maybe it would be enough if the community version of U-Boot were updated to version v2025.07 and it would solve the reboot problem for this SBC, just like it happened for the Orange Pi Zero 3 where updating U-Boot to v2025.04 solved the problem of decoding RAM size on the SBC

Today it is EDGE v6.15 no v6.16.

Recommended to upgrade U-Boot to version v2025.07 This version has big changes for allwinner (sunxi) chips. This concerns the initialization of a non-standard size of RAM (1.5; 2.5 GB), downloads from eMMC.....

Yes, that's right. This is relevant to the issue under discussion.