I downloaded the image. And yes, of course, I needed to set up the wifi connection when armbian asked me to.

@Nick A I re-tested v0.6.4 on the A7S several times. It turns out that if you unplug and replug the DP cable before the GUI loads, you won't get a signal back. The only fix is to restart the device. Additionally, the restart button on the A7S is not functional with this image.

Hi there. I just got my hands on a brand new 5T with 24GB of RAM and installed Armbian 26.04 minimal on it (on an SD card - no eMMC on this board). I immediately put it to use running CI jobs, however started seeing segfaults and things almost straight away. Current power source is the Radxa 60W power supply. Currently passively cooled (with the Radxa heat sink). Hasn't gone over 70º in the last 24 hours, even when maxxed out compiling rust packages. Here's information about the board: james@kassandra:~$ cat /proc/device-tree/model Radxa ROCK 5Tjames@kassandra:~$ james@kassandra:~$ dpkg -l | grep '^ii linux-' ii linux-base 4.15ubuntu5 all Linux image base package ii linux-dtb-current-rockchip64 26.2.5 arm64 Armbian Linux current DTBs in /boot/dtb-6.18.24-current-rockchip64 ii linux-image-current-rockchip64 26.2.5 arm64 Armbian Linux current kernel image 6.18.24-current-rockchip64 ii linux-libc-dev:arm64 7.0.0-15.15 arm64 Linux Kernel Headers for development ii linux-u-boot-rock-5t-current 26.2.5 arm64 Das U-Boot for rock-5t james@kassandra:~$ sudo dd if=/dev/mmcblk1 bs=512 count=8192 2> /dev/null | strings | grep '^DDR' DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 I can reliably recreate the segfault by running `claude`: Bun v1.3.14 (0a466a11) Linux arm64 Linux Kernel v6.18.24 | glibc v2.43 CPU: neon fp aes crc32 atomics Args: "claude" Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(5) fetch(35) jsc spawn(8) standalone_executable yaml_parse claude_code Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:dns" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:readline" "node:stream" "node:stream/consumers" "node:string_decoder" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:vm" "node:zlib" "ws" "node:http2" Elapsed: 9886ms | User: 3200ms | Sys: 775ms RSS: 72.61MB | Peak: 0.32GB | Commit: 72.61MB | Faults: 993 | Machine: 24.72GB panic(main thread): Segmentation fault at address 0x7300A749AD00 dmesg output: [54442.949901] 2.1.128: claude: potentially unexpected fatal signal 5. [54442.949933] CPU: 5 UID: 1000 PID: 540517 Comm: claude Not tainted 6.18.24-current-rockchip64 #2 PREEMPT [54442.949952] Hardware name: Radxa ROCK 5T (DT) [54442.949959] pstate: 00001000 (nzcv daif -PAN -UAO -TCO -DIT +SSBS BTYPE=--) [54442.949973] pc : 00000000031cb264 [54442.949980] lr : 00000000031cb264 [54442.949986] sp : 0000ffffece87fd0 [54442.949992] x29: 0000ffffece88070 x28: 000000000059aabe x27: 0000ffffb267f740 [54442.950016] x26: 0000000000000004 x25: 0000ffffece884c8 x24: 0000ffffece887b8 [54442.950035] x23: 0000ffffece88850 x22: 000000000691c000 x21: 0000ffffece88540 [54442.950055] x20: 000000000691c000 x19: 0000ffffece886d0 x18: 0000000000000000 [54442.950073] x17: 0000ffffb28386a0 x16: 0000000006a12ff0 x15: 0000000000000034 [54442.950092] x14: 0000000000000032 x13: 0000000000000003 x12: aaaaaaaaaaaaaaaa [54442.950111] x11: 0101010101010101 x10: 0000000000000000 x9 : 0000000000000000 [54442.950130] x8 : 0000000000000086 x7 : 0000000000000000 x6 : 0000000000000000 [54442.950148] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [54442.950165] x2 : 0000000000000000 x1 : 0000ffffb2a3bc90 x0 : 0000000000000000 I tried running stress-ng and saw thousands of failures leading to a hard lockup: stress-ng: info: [542138] setting to a 10 mins run per stressor stress-ng: info: [542138] dispatching hogs: 8 vm stress-ng: info: [542139] vm: using 1.35GB per stressor instance (total 10.79GB of 13.48GB available memory) stress-ng: fail: [542153] checkerboard: detected 4 memory errors stress-ng: fail: [542149] galpat-one: detected 2437 memory errors stress-ng: fail: [542148] flip: detected 32 memory errors stress-ng: fail: [542147] flip: detected 96 memory errors stress-ng: fail: [542152] galpat-one: detected 5632 memory errors stress-ng: fail: [542148] galpat-one: detected 818 memory errors stress-ng: fail: [542147] fwdrev: detected 48 memory errors stress-ng: fail: [542149] gray code (flip): detected 96 memory errors stress-ng: fail: [542150] flip: detected 96 memory errors stress-ng: fail: [542147] galpat-one: detected 1980 memory errors stress-ng: fail: [542148] gray code: detected 160 memory errors stress-ng: fail: [542150] fwdrev: detected 112 memory errors stress-ng: fail: [542149] incdec code: detected 160 memory errors stress-ng: fail: [542150] galpat-one: detected 1740 memory errors stress-ng: fail: [542149] inc-nybble: detected 32 memory errors stress-ng: fail: [542148] incdec code: detected 16 memory errors stress-ng: fail: [542152] incdec code: detected 16 memory errors stress-ng: fail: [542151] flip: detected 288 memory errors stress-ng: fail: [542154] flip: detected 288 memory errors stress-ng: fail: [542153] flip: detected 144 memory errors stress-ng: fail: [542151] galpat-one: detected 256 memory errors stress-ng: fail: [542153] galpat-one: detected 871 memory errors stress-ng: fail: [542149] modulo X: detected 2 memory errors stress-ng: fail: [542149] info: 5 failures reached, aborting stress process stress-ng: fail: [542144] vm: detected 2727 bit errors while stressing memory stress-ng: error: [542138] vm: [542144] terminated with an error, exit status=2 (stressor failed) stress-ng: fail: [542148] modulo X: detected 4 memory errors stress-ng: fail: [542148] info: 5 failures reached, aborting stress process stress-ng: fail: [542142] vm: detected 1030 bit errors while stressing memory stress-ng: error: [542138] vm: [542142] terminated with an error, exit status=2 (stressor failed) stress-ng: fail: [542152] modulo X: detected 3 memory errors stress-ng: fail: [542150] modulo X: detected 8 memory errors stress-ng: fail: [542147] modulo X: detected 1 memory error stress-ng: fail: [542150] moving inversion: detected 12 memory errors stress-ng: fail: [542150] info: 5 failures reached, aborting stress process stress-ng: fail: [542139] vm: detected 1968 bit errors while stressing memory stress-ng: error: [542138] vm: [542139] terminated with an error, exit status=2 (stressor failed) stress-ng: fail: [542151] modulo X: detected 5 memory errors stress-ng: fail: [542152] one-zero: detected 7881 memory errors stress-ng: fail: [542151] moving inversion: detected 168 memory errors stress-ng: fail: [542153] modulo X: detected 37 memory errors stress-ng: fail: [542146] vm: detected 13532 bit errors while stressing memory stress-ng: error: [542138] vm: [542146] terminated with an error, exit status=2 (stressor failed) stress-ng: fail: [542147] mscan: detected 640 memory errors stress-ng: fail: [542147] info: 5 failures reached, aborting stress process stress-ng: fail: [542143] vm: detected 2765 bit errors while stressing memory stress-ng: error: [542138] vm: [542143] terminated with an error, exit status=2 (stressor failed) stress-ng: fail: [542153] moving inversion: detected 32 memory errors stress-ng: fail: [542153] info: 5 failures reached, aborting stress process stress-ng: fail: [542141] vm: detected 1088 bit errors while stressing memory stress-ng: error: [542138] vm: [542141] terminated with an error, exit status=2 (stressor failed) Anyone have any advice on how to fix this? Is it faulty DDR or a firmware issue?

Has anyone found a working gpiolib implementation for Armbian on Orange Pi 5? I'm aware of wiringPi and it sort of works. However, being able to use the "real stuff" so to speak would make my life easier.

@humanus Did you build it yourself, or did you just download Nick's version? Also, doesn't the WiFi connection need to be set up first? I downloaded Nick's A7S Mineline v0.1 directly, but I can't connect even with a wired NIC, so I can't get the WiFi working either.