@Nick A this is updated patch for x98h that enables wifi after warm reboot. 2001-arm64-dts-allwinner-h618-add-x98h.patch

Armbian 25.8.1 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + wine-10.15-staging-tkg-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.15) + DXVK-stripped v2.7.1 ~20fps@720p (low settings) Skyrim SE

I have a working img that boots fine from sd card. However the dtb is not perfectly working. Below are dts from android and linux (partial working). I hope that someone can help me with rewriting device tree source for it. Thank you! rk3399-emb3531.dts.txtrk3399-emb3531-android.dts.txt

Armbian current: It seems that the N2+ is [i]immune[/i] to Chrony and systemd-timesyncd. The only way I can set the date/time is manually through date -s. # systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: enabled) Active: active (running) since Mon 2025-11-24 13:06:59 PST; 31min ago Invocation: 50da85c1116348dbbd83cca270da6ff8 Docs: man:systemd-timesyncd.service(8) Main PID: 1185 (systemd-timesyn) Status: "Idle." Tasks: 2 (limit: 4227) Memory: 1.6M (peak: 2.3M) CPU: 79ms CGroup: /system.slice/systemd-timesyncd.service └─1185 /usr/lib/systemd/systemd-timesyncd Nov 24 13:06:59 lab systemd-timesyncd[1185]: System clock time advanced to recorded timestamp: Mon 2025-11-24 13:06:59 PST Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection. Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection. Nov 24 13:06:57 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection. Nov 24 13:07:01 lab systemd-timesyncd[1185]: Network configuration changed, trying to establish connection. Nov 24 13:07:11 lab systemd-timesyncd[1185]: Timed out waiting for reply from 10.2.1.10:123 (10.2.1.10). No, the network configuration has na-ha-hot, changed, Spastic. I see via tcpdump, the request going out 123/udp and the response, coming back. The information arrives at the destination. But it hits a hard rock head and disintegrates. Of course if it can't set the system clock, there's no sense trying to make it set the RTC. How is this possible in the 21st Century? Does time, no longer matter to Gen Z? Is this the precursor to the Apocalypse? Should I convert to religion and start praying?

If you are using the radxa-pkg github "which is the most up-to-date" know that its hardcoded to point to specific firmware. To get around this you need to create a file: This example is for an SDIO variant using the radxa dkms package cat > /etc/modprobe.d/aic8800-wireless.conf <<- EOT options aic8800_fdrv_sdio aicwf_dbg_level=0 custregd=0 ps_on=0 options aic8800_bsp_sdio aic_fw_path=/lib/firmware/aic8800_fw/SDIO/aic8800 EOT Also note that the AIC8800 firmware located in armbian-firmware is kind of old and probs not compat with the radxa builds.