Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

ebin-dev

Members
  • Joined

  • Last visited

Everything posted by ebin-dev

  1. SPI now contains U-Boot SPL 2026.01 and it boots the current kernel 6.18.63 off emmc: So in order to make sure there is 'only one captain on the ship' I erased the boodloader on emmc, extracted u-boot-rock-5b-edge and flashed it to SPI: # erase bootloader on emmc sudo dd if=/dev/zero of=/dev/mmcblk0 bs=512 seek=64 count=8128 conv=notrunc sudo dd if=/dev/zero of=/dev/mmcblk0 bs=512 seek=16384 count=16384 conv=notrunc # erase bootloader on SPI sudo dd if=zero.img of=/dev/mtdblock0 #zero.img from radxa # install u-boot 2026.01 to SPI # the name of the linux-u-boot-rock-5b-edge_*.deb package changes frequently wget https://fi.mirror.armbian.de/beta/pool/main/l/linux-u-boot-rock-5b-edge/linux-u-boot-rock-5b-edge_26.11.0-trunk.129_arm64__2026.01-S127a-Pec93-H9409-Vc955-B3ba1-R448a.deb mkdir bootloader dpkg-deb --extract linux-u-boot-rock-5b-edge_26.11.0-trunk.129_arm64__2026.01-S127a-Pec93-H9409-Vc955-B3ba1-R448a.deb ./bootloader cd ./bootloader/usr/lib/linux-u-boot-edge-rock-5b sudo dd if=u-boot-rockchip-spi.bin of=/dev/mtdblock0 strings /dev/mtd0 | grep 'U-Boot SPL 20' U-Boot SPL 2026.01_armbian-2026.01-S127a-Pec93-H9409-Vc955-B3ba1-R448a (Nov 10 2026 - 12:25:38 +0000)Edit: I tried to switch the kernel from current to edge using armbian-config, but the 7.3 branch wasn't installed at all. Manual installation using the linux-edge deb packages (7.3.4) downloaded from beta.armbian.com renders my system non-bootable (cold reboot, tested on SD).
  2. You were right. The system did not update to the latest os-release, since Armbian updates were commented in armbian.list. I fixed that and updated to the latest release. The linux-u-boot-current-rock-5b still includes 2017.09, so I have to switch to edge. # apt list -i | grep linux-u-boot-rock-5b linux-u-boot-rock-5b-current/now 26.11.0-trunk.129 arm64 [installed,local] # cat /etc/os-release PRETTY_NAME="Armbian 26.11.1 trixie" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.7 ID=debian HOME_URL="https://www.armbian.com" SUPPORT_URL="https://forum.armbian.com" BUG_REPORT_URL="https://www.armbian.com/bugs" ARMBIAN_PRETTY_NAME="Armbian 26.11.1 trixie" # strings /usr/lib/linux-u-boot-current-rock-5b/idbloader.img | grep "U-Boot SPL 20" U-Boot SPL 2017.09_armbian-2017.09-S39cd-P3514-H411a-V172f-B3ba1-R448a (Nov 09 2026 - 13:44:51)
  3. Both Armbian current and edge U-Boot versions (for rock5b) are based on 2017.09, just like the current Radxa bootloader and like the one inside the EDK2 UEFI v1.1 binary (probably dangerous to operate if accessible from the internet). According to the recent Armbian newsletter an updated bootloader for rockchip64 boards based on U-Boot 2026.10 is on its way. It is probably a good idea to use that one, once available.
  4. Very interesting - thanks for the reply! The boot loader in SPI flash is the current one from radxa (outdated). To zero an extra one on emmc is not so difficult. But I am not sure how to flash something like EDK2 EUFIv1.1 to SPI. Could you describe the steps of obtaining and flashing the boot loader you use ? (or a recent u-boot version) If booting off emmc goes wrong I would boot from SD and revert back the boot loader to the current one.
  5. I am using the latest linux-image-current-rockchip64 kernels from beta.armbian.com (branch 6.18) and there are no issues booting off emmc on a headless rock5b (data on nvme). However, I would like to switch to linux-image-edge-rockchip64 (branch 7.3; for security reasons), but my system does not boot from emmc anymore once the new 7.3 kernel image (incl dtb and headers) is installed. What might be the issue here ? Should I first update the boot loader on SPI to a more recent version ? Currently the following version is used: U-Boot SPL 2017.09-gd1cf49135ee-220414 #stephen (May 23 2024 - 18:47:18). # cat /proc/cmdline root=UUID=e0d1f6a8-8612-4976-9917-redacted rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=903a1366-4ff1-449e-8e71-redacted usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x152d:0x0578:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory androidboot.fwver=ddr-v1.16-9fffbe1e78,bl31-v1.45,uboot-d1cf49135e-05/23/2024 Package: linux-image-current-rockchip64 Version: 26.11.0-trunk.126 Source: linux-6.18.62
  6. Thanks for looking into this. As the docker install does not have access to apps it would be quite restricted and not really usable for many. I would certainly not use it. May be you could try to set up the supervised install (I know it is not supported anymore by HA) ? That would bring a lot of attention to Armbian ...
  7. The installation of Home Assistant through armbian-config ends with a reboot in order to enable AppArmor. No modification. If that installation does not work out of the box I will leave it for now as it would not provide a solid basis for the automation of an entire home.
  8. Same here: Installed Home Assistant using armbian-config on a Rock 5b with Armbian Trixie (v26.2.1 for Rock 5B running Armbian Linux 6.18.32-current-rockchip64). I switched from NetworkManager to systemd-networkd. Reboot to enable AppArmor left a system not accessible via ssh after more than 100s. Do we have to wait somewhat longer, or is there currently an issue with the installation of Home Assistant on Armbian Trixie ?
  9. @iav The kobol dtbs (rk3399-kobol-helios64.dtb) linked in the messages before are patched in the following way having the effect that helios64 is finally stable (see here) : The opp-microvolt values in opp-table-1 are just replaced by the ones given below (for all linux kernel versions). opp-table-1 { compatible = "operating-points-v2"; opp-shared; phandle = <0x0d>; opp00 { opp-hz = <0x00 0x18519600>; opp-microvolt = <0xdbba0 0xdbba0 0x1312d0>; clock-latency-ns = <0x9c40>; }; opp01 { opp-hz = <0x00 0x23c34600>; opp-microvolt = <0xdbba0 0xdbba0 0x1312d0>; }; opp02 { opp-hz = <0x00 0x30a32c00>; opp-microvolt = <0xdbba0 0xdbba0 0x1312d0>; }; opp03 { opp-hz = <0x00 0x3c14dc00>; opp-microvolt = <0xe7ef0 0xe7ef0 0x1312d0>; }; opp04 { opp-hz = <0x00 0x47868c00>; opp-microvolt = <0xfa3e8 0xfa3e8 0x1312d0>; }; opp05 { opp-hz = <0x00 0x54667200>; opp-microvolt = <0x10c8e0 0x10c8e0 0x1312d0>; }; opp06 { opp-hz = <0x00 0x5fd82200>; opp-microvolt = <0x11edd8 0x11edd8 0x1312d0>; }; opp07 { opp-hz = <0x00 0x6b49d200>; opp-microvolt = <0x1312d0 0x1312d0 0x1312d0>; }; };
  10. I have attached both the dtbs for linux 6.6 and 6.12 to this message in the forum.
  11. @SymbiosisSystems To get those changes into the mainline build is currently not the solution preferred by the maintainer of this board, because it is some kind of a hot fix. To boot your helios64 to the command line you could try an image from the archive and boot from sd. A system on emmc could then be manipulated using chroot.
  12. This was discussed some time ago. Everybody has the same problem with the 2.5Gb interface. The best you can do is to switch to linux 6.6.xx, replace the dtb, update the firmware in /lib/firmware/rtl_nic and run a script in /etc/rc.local (see here).
  13. The most current download images for Helios64 are now all provided with linux 6.18.xx. I downloaded a minimal image and checked the dtb: it would not appear to contain the opp-microvolt patch that made Helios64 finally stable. So for the ones who have stability issues again on Helios64, I attached the patched dtb compiled for linux 6.18.xx using the exact same opp-microvolt values as in the previous dtb versions I compiled for linux 6.6 and 6.12. The current linux deb files can be downloaded from beta.armbian.com, the linux 6.18.18 deb files I used can be downloaded from here (to be installed with 'dpkg -i linux*'). In order to install the dtb, simply unzip it, copy it into the proper location, update initramfs and reboot: # install the dtb with the opp-microvolt patch: unzip rk3399-kobol-helios64.dtb-6.18.18-opp.zip cp rk3399-kobol-helios64.dtb-6.18.18-opp /boot/dtb/rockchip/rk3399-kobol-helios64.dtb update-initramfs -u reboot rk3399-kobol-helios64.dtb-6.18.18-opp.zip
  14. Thanks for your comments. I did not touch the regulator@40 values at all - only the opp frequencies in line with suggestions from @prahal and some cache settings. cpufreq sampling_rates were changed to about 40000 (depending on the cluster) for kernels 6.6 by a script in /etc/rc.local. The script does not apply anymore in linux 6.12. Instead of disabling the A72 cluster altogether, reducing the burden on the CPUs during data transfers helps to substantially reduce crashes and avoids triggering the watchdog timer. P.S.: I bought a Rock-5B in October 2022 and I finally migrated everything to it.
  15. The rsync instruction copies the files using an exclude list. However that list does not explain why folders other than /var/log/journal are missing in /var/log. # cat /usr/lib/armbian-install/exclude.txt /boot/* /dev/* /proc/* /sys/* /media/* /mnt/* /run/* /tmp/* /ddbr/* /var/log/journal
  16. You just have to create the nginx folder in /var/log with owner www-data (it is not created automatically): mkdir /var/log/nginx chown -R www-data:www-data /var/log/nginx systemctl restart nginx
  17. With linux 6.12 the optimizations in /etc/rc.local do not apply anymore since some configuration options have vanished. So if you like to have a stable 2.5Gbit/s network connection without timeouts, linux-6.6 is still recommended (bookworm and trixie). You can build it yourself using an Armbian snapshot (from Dec. 2024) or download a recent linux-6.6.100 from here.
  18. To troubleshoot this thing I would just boot from another sd card with a fresh bookworm image leaving your system on emmc or on another sd untouched. In 'sudo ethtool -i <interface>' the name of your 2.5G interface has to be inserted - 'ifconfig' will reveal it (I renamed mine to end1). If the rtl_nic firmware is recognized correctly it will display: root@grid:~# sudo ethtool -i end1 driver: r8152 version: v1.12.13 firmware-version: rtl8156a-2 v2 04/27/23 ...
  19. To troubleshoot that you could boot off a fresh Armbian 24.11.1 Bookworm image (6.6.62) and add rtl_nic firmware, replace dtb, setup rc.local. If transfer rates are still low something may be wrong with your client or with your helios64 or with the network itself. Did you launch 'htop' so that you can see what is going on during the data transfer? Are there any cores fully utilized ? Is nic offloading enabled ? etc. 'systemctl disable armbian-hardware-optimize.service' I am automatically calling that shell script while mounting helios64 as a remote drive on macOS clients (using netatalk). The names of the processes (afpd|cnid|iperf3|netatalk) need to be replaced by the processes involved in the data transfer on your helios (iperf3, smb? etc. ). root@grid:~# chmod +x /usr/local/bin/make_nas_processes_faster.sh root@grid:~# sh /usr/local/bin/make_nas_processes_faster.sh pid 21358's current affinity list: 4 pid 21358's new affinity list: 4 pid 21359's current affinity list: 4 pid 21359's new affinity list: 4 pid 21360's current affinity list: 4 pid 21360's new affinity list: 4 pid 21367's current affinity list: 4 pid 21367's new affinity list: 4 pid 21368's current affinity list: 4 pid 21368's new affinity list: 4 pid 21700's current affinity list: 4 pid 21700's new affinity list: 4
  20. Well, the two packages libelf-dev and zlib1g-dev were missing on your installation and 'sudo apt --fix-broken install' resolved it. Reboot should be fine: after the dtb is replaced and 'update-initramfs -u' executed. Cheers
  21. @greg396 You can downgrade linux to 6.6.87: unzip the file debs-6.6.87.zip on your helios, cd into the folder and submit 'dpkg -i linux*'. With linux 6.12. I get some timeouts during data transfer. You need to install the modified dtb for the linux-6.6 branch in /boot/dtb/rockchip/ (do not forget 'update-initramfs -u' after that and reboot). Follow the link load distribution and Install the code displayed ('cd ... exit 0') in /etc/rc.local and reboot. I have disabled any Armbian updates by commenting the text in /etc/apt/sources.list.d/armbian.list but submitting 'apt-mark hold armbian-firmware' may work as well. However, I have no idea whether or not OMV requires a specific kernel branch - but I don't think so. If you need to reinstall linux 6.12. you can collect the three corresponding deb packages (linux-image, linux-dtb and linux-headers) on http://beta.armbian.com/ (currently 6.12.25). P.S.: Alternatively you can also download the Armbian 24.11.1 Bookworm image (6.6.62) and start from the fresh image (add rtl_nic firmware, replace dtb, setup rc.local). If transfer rates are still low something may be wrong with your client or with your helios64 or with the network itself.
  22. Hi greg396, solutions for your issue were discussed in the parallel thread: You need to update the rtl_nic firmware in /lib/firmware/rtl_nic and use the modified dtb for stability reasons. If there are any remaining problems, check the load distribution on your helios64 and the connection to your client. The iperf3 transfer speeds from helios64 to macos clients in our network are 280MByte/s without any dropouts (linux 6.6.87 is recommended), upload speed is around 230MByte/s and we are using it 24/7 without any issues.
  23. Thanks for testing. I think that the load distribution is indeed essential to get good transfer speeds and it seems that the scheduler needs some help to do it right. With the settings posted before the load on cpus0-3 is below 20% and the load on cpus4-5 is between 60% and 80% while downloading a 2GB file from Helios64 to a client with effectively 280MByte/s (on linux 6.6.74, ondemand governor, ext4 FS, transfer with netatalk 4.1.1). But Helios64 only has to access a single 4TB SSD formatted to ext4 in this case. You could try to move your sata load to cpu5 ('echo 20' for the ahci interrupt) and the network load to cpu4 ('echo 10' for the xhci interrupt) and see if that helps (cpu5 is usually less frequently occupied compared to cpu4). # cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=600000 MAX_SPEED=1800000 GOVERNOR=ondemand
  24. I have only checked the performance of the 2.5G interface with linux 6.12.10 - not the 1G interface. Could you check if the issue remains if you use linux 6.6.74 ? (install with 'dpkg -i linux*'; replace the dtb with the one attached; execute 'update-initramfs -u'; reboot) Edit: The 2.5G interface needs the hardware fix in order to operate reliably in mode 2500baseT/Full too: during ethernet handshaking 1G speeds could be established transiently. I think that this might have happened during the test with odroid h4+. Edit: You mentioned that helios went to 1.2GHz during the transfer. If the load is handled by a little core that may be the reason for the reduced transfer speed. A big core should be assigned to it. Therefore, the following code in /etc/rc.local is very helpful in this context (it also configures the ondemand governor and makes it responsive) [armbian-hardware-optimization is disabled on my system]: cd /sys/devices/system/cpu/cpufreq for cpufreqpolicy in 0 4 ; do echo 1 > policy${cpufreqpolicy}/ondemand/io_is_busy echo 25 > policy${cpufreqpolicy}/ondemand/up_threshold echo 10 > policy${cpufreqpolicy}/ondemand/sampling_down_factor echo $(cat policy${cpufreqpolicy}/cpuinfo_transition_latency) > policy${cpufreqpolicy}/ondemand/sampling_rate done for i in $(awk -F":" "/ahci/ {print \$1}" < /proc/interrupts | sed 's/\ //g'); do echo 10 > /proc/irq/$i/smp_affinity done for i in $(awk -F":" "/xhci/ {print \$1}" < /proc/interrupts | sed 's/\ //g'); do echo 20 > /proc/irq/$i/smp_affinity done exit 0 While transferring data to/from Helios64 some processes are involved such as iperf3 - or netatalk in my case. Those processes should also be executed on a big core. If iperf3 tests are performed or if helios64 is mounted as a remote drive I call the following script that assigns a big core and a preferred io scheduling class to those processes (to be adapted to your needs). This helps to make your nas_processes faster (kudos to @tkaiser) . # cat /usr/local/bin/make_nas_processes_faster.sh #!/bin/sh -e for i in `pgrep "afpd|cnid|iperf3|netatalk"` ; do ionice -c1 -p $i ; taskset -c -p 4 $i; done # >/dev/null 2>&1 rk3399-kobol-helios64.dtb-6.6.xx-L2-hs400-opp

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.