I implemented this from the forum @kris777 mentioned, and IT WORKED: Now, I flashed this image, and it didn't even boot. Anyway, thanks to everyone involved for helping me with this issue, and big thanks to every maintainer and contributor for keeping this distro alive, as its contribution deserves to be appreciated.

Private Girls In Your Town - No Verify - Anonymous Sex Dating https://PrivateLadyEscorts.com [url=https://PrivateLadyEscorts.com/girls.html] Private Lady In Your Town [/url] - Anonymous Sex Dating - No Selfie

Been looking at getting my Helios64 back up and running after experiencing a lot of instability a few years ago. Stumbled across this thread and things look somewhat promising, but after reading through I'm unsure what I should actually do to get things running! Lots of different posts with lots of different .dtb files, seemingly PR's in to the armbian repo etc. As of today, what is the best approach to get things up and running? Do the PR's mean I should be able to just use Armbian direct from the site and have a stable NAS?

Hello, sorry for late answer, but I had no time to experiment with my rock64 board. Maybe this issue is already resolved, if so please let me know. I'm still using kernel 6.6.63 and holding kernel packages in order not to break a working home server. So I managed to temporary switch kernel to 6.12.9 again for testing (copied old /boot and corrected symlinks) and enter UART console: Here is output of U-Boot commands you asked: Hit any key to stop autoboot: 0 => setenv b => setenv c => setenv a "a/b" => setexpr b sub "a/" "" a Unknown command 'setexpr' - try 'help' => echo ${b} => setexpr c 1 + 1 Unknown command 'setexpr' - try 'help' => echo ${c} => fdt fdt - flattened device tree utility commands Usage: fdt addr [-c] <addr> [<length>] - Set the [control] fdt location to <addr> fdt move <fdt> <newaddr> <length> - Copy the fdt to <addr> and make it active fdt resize [<extrasize>] - Resize fdt to size + padding to 4k addr + some optional <extrd fdt print <path> [<prop>] - Recursive print starting at <path> fdt list <path> [<prop>] - Print one level starting at <path> fdt get value <var> <path> <prop> - Get <property> and store in <var> fdt get name <var> <path> <index> - Get name of node <index> and store in <var> fdt get addr <var> <path> <prop> - Get start address of <property> and store in <var> fdt get size <var> <path> [<prop>] - Get size of [<property>] or num nodes and store in <var> fdt set <path> <prop> [<val>] - Set <property> [to <val>] fdt mknode <path> <node> - Create a new node after <path> fdt rm <path> [<prop>] - Delete the node or <property> fdt header - Display header info fdt bootcpu <id> - Set boot cpuid fdt memory <addr> <size> - Add/Update memory node fdt rsvmem print - Show current mem reserves fdt rsvmem add <addr> <size> - Add a mem reserve fdt rsvmem delete <index> - Delete a mem reserves fdt chosen [<start> <end>] - Add/update the /chosen branch in the tree <start>/<end> - initrd start/end addr NOTE: Dereference aliases by omitting the leading '/', e.g. fdt print ethernet0. => echo ${fdtfile} rockchip/rk3328-rock64.dtb => echo ${fdt_addr_r} 0x01f00000 => echo ${kernel_addr_r} 0x02000000 => echo ${ramdisk_addr_r} 0x04000000 => ver U-Boot 2017.09-rockchip-ayufan-1065-g95f6152134 (Apr 06 2020 - 08:10:39 +0000) aarch64-linux-gnu-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0 GNU ld (GNU Binutils for Ubuntu) 2.30 => CTRL-A Z for help | 1500000 8N1 | NOR | Minicom 2.10 | VT102 | Offline | ttyUSB0 I have set up rock64 to boot from SSD connected over USB3-SATA adapter (bought from pine64 store) without SD-card. To make it work I flashed latest U-Boot from ayufan to SPI by this tutorial. Maybe this error because of old U-Boot, and you're right, looks like it doesn't support setexpr command djurny, thank you for looking into this. And one question I don't understand, if I should upgrade U-Boot in SPI or I should erase SPI and wirte U-boot somewhere else? And will I be able to boot directly from USB-SSD without SD-card after that?

I don’t know about Odroid n2 but all the 2025.11 builds with graphical ui get stuck when the initial setup is completed and message appears “now booting to graphical session” and never boots 2024 builds do boot and stay normal I am using mainline uboot via spi boot.