Active threads

I assume OPi02w has no on-board storage, so it only is the bootcode in ROM, and that reads U-Boot binary blob from fixed sector offset location on the SD-card. It does not even need a MBR-table or GPT and it is not in a partition, so you won't see it. Only if you use dd to read (or write/wipe) that data you will know. See how U-Boot needs to be written for your OPi02w, then you will understand. If the U-Boot is build to initialize the USB and HDD, you do not need /boot partition on the SD-card. But I do not know that. Not all USB-SATA chipset drivers are in U-Boot, so if not, you indeed need a boot partition on de SD-card where kernel initrd DTB are, those should understand USB-SATA chips and so see the rootfs on HDD.

The bootlog-OK.txt shows: [ 10.796728] Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read which is not good at all. I also think you think you still not have set verbosity=7 in armbianEnv.txt, else the both the OK and NOK logs would show more and that is needed as a start for further investigation.

I'm using armbian trixie/BSP 6.6.98 by @Nick A with thermal throttling disabled (`step_wise` policy) and with the performance governor (shouldn't matter that much).

rk3588-pcie_bifurcation_2x2-uboot.patchrk3588-pcie_bifurcation_2x2.patch Attached are two patches I've prepared. One for uBoot (to correctly recognize split pcie3x4 to two independent controllers, pcie3x4 and pcie3x2), and one for DT of NanoPC T6. This basically allows you to use trimmed-down bifurcation adapter. The adapter in question must be trimmed down/cut to fit on the back of the board. Tested with 2x NVME, and 1xNVME and QCNFA765 wireless card. I'll post photos later once I'll disconnect the board again from my setup. BEWARE!!! If you'd plan to use more than one ath11k wireless card, you'd need QRTR patch. Since the SBL enums changed in recent kernel 6.18.18+, I am also preparing modified kernel patch (originally for OpenWRT by Hauke Mehrtens and Robert Marko) to allow for more than one ath11k wireless to be installed. Will post later with new patch for it. root@ap-voyager:~# lspci -nn 0000:00:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0000:01:00.0 Network controller [0280]: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103] (rev 01) 0001:10:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0001:11:00.0 Non-Volatile memory controller [0108]: Shenzhen Longsys Electronics Co., Ltd. Lexar NM610 PRO NVME SSD (DRAM-less) [1d97:1202] (rev 01) 0002:20:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0002:21:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) 0003:30:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0003:31:00.0 Network controller [0280]: Qualcomm Technologies, Inc QCNFA765 Wireless Network Adapter [17cb:1103] (rev 01) 0004:40:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd RK3588 [1d87:3588] (rev 01) 0004:41:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) root@ap-voyager:~#

thanks, it is settled now, apt-get update behaves normally.

Hello @VBB, those log snippets show no reason why system can freeze. Recompling bcmdhd internal SDIO Wifi driver on kernel updates works as intended. Disabling lightdm and enabling gdm3 is part of the spacemit-gpu-addon.sh you run - gdm3 is the display-manager to use if you want a DM with Wayland (b/c only Wayland works with those closed source GPU stuff). If it's stuck, just rise the loglevel= in /boot/extlinux/extlinux.conf for more output or simply download one of my images and retry running that script (Image -> https://privat-in.de under "Downloads"). HTH // Sven-Ola

meco any update on this? dual NVME also does not work on non vendor kernels as well as second HDMI port.

@Sergioclr I remember someone was able to get Ethernet working by changing 16 to 0. There's two locations ethernet-phy@16 and reg = <16>; +&mdio1 { + rmii_phy: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +};

45mbps Down / 4.5mbps UP with device more closer to the router root@rk322x-box:~# speedtest Retrieving speedtest.net configuration... Testing from Vivo (REDACTED)... Retrieving speedtest.net server list... Selecting best server based on ping... Hosted by Redel Internet (Balneário Camboriu) [424.68 km]: 23.94 ms Testing download speed................................................................................ Download: 45.84 Mbit/s Testing upload speed...................................................................................................... Upload: 4.46 Mbit/s

This likely means the I2S overlay doesn’t exist yet. Someone would need to implement it and add it upstream (or just here to Armbian build framework). You can try enabling it manually via the Device Tree editor: https://docs.armbian.com/User-Guide_Armbian-Config/System/#device-tree-editor No guarantees it will work — hardware descriptions are often incomplete or inaccurate, and that’s outside our control.

The board works well with Armbian, but currently it is not possible to use USB audio interfaces (sound cards, modems exposing audio functions, VoIP devices, etc.) because the snd-usb-audio module is missing from the kernel and not available as a loadable module. If needed, I can provide logs, test kernels, or help verify the changes. Thanks for maintaining support for this board.

Does sway eat a lot of RAM? Can it be used fine in a 640x480 display? I've been staying with my labwc setup, because it's known to be minimalistic. Orange Pi Zero3 and Raspberries with 1GB RAM can run it fluidly.

Hi, I upgraded to the stable version of Debian (Trixie) Armbian Linux 6.18.23-current-rockchip64. And the USB 3.0 port stopped working. Other USB 2.0 works fine. orangepi3b:~$ lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub orangepi3b:~$ sudo dmesg|grep usb6 [ 2.474823] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.18 [ 2.474852] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.474867] usb usb6: Product: Generic Platform OHCI controller [ 2.474881] usb usb6: Manufacturer: Linux 6.18.23-current-rockchip64 ohci_hcd [ 2.474893] usb usb6: SerialNumber: fd840000.usb orangepi3b:~$ sudo dmesg|grep usb7 [ 2.416665] usb usb7: We don't know the algorithms for LPM for this host, disabling LPM. [ 2.416917] usb usb7: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.18 [ 2.416940] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.416956] usb usb7: Product: xHCI Host Controller [ 2.416969] usb usb7: Manufacturer: Linux 6.18.23-current-rockchip64 xhci-hcd [ 2.416983] usb usb7: SerialNumber: xhci-hcd.1.auto [ 5.223412] usb usb7-port1: connect-debounce failed

I updated to my self-build 6.6.135 [1] kernel today. I soft-rebooted, and the issue did not reappear. Hopefully it stays this way. [1] https://github.com/armbian/build/pull/9705

Also interested in this. Was able to install using `sudo ./sunxi-fel -p spiflash-write 0 u-boot-sunxi-with-spl.bin`, where the u-boot image came from the Armbian I downloaded (scp'd it off). That makes use of a patch submitted to the sunxi-tools repo (https://github.com/linux-sunxi/sunxi-tools/pull/232), which does actually work. It is quite happy to boot the image from SD card, and runs even when there is no SD card installed, which is great! However, I don't see any SPI or mtdblock messages in dmesg, and naturally, none exist in /dev/. Am I missing something? Or is SPI not enabled currently for some reason?

Native Steam Client For ARM Linux https://interfacinglinux.com/community/sbcsoftware/native-steam-client-for-arm-linux/ I have tested: the Steam client works (+ Proton11-ARM64 works). The memory usage was much reduced. Non-Steam games also work

Upstream support for rk3588 is still wip. For desktop usage I suggest to either try "edge" which may have the feature you want already merged in or try "vendor" kernel which is based on Rockchip BSP.

@DaBo Thanks for sharing this. Are you able to run Armbian on this? Is LAN, HDMI, etc working fine on this?

Hello, good evening. I'll check again tomorrow; I don't remember which version of Armbian I have installed, but the microphone works without any problems in Armbian. I simply installed the Armbian version and didn't have to modify anything.

The problem (Armbian on U9-H requires physical button after power loss) The discovery process (MCU at I2C bus 0, address 0x15, register 0x11) The fix: i2cset -y 0 0x15 0x11 0x00 The systemd service for persistence That 0x01 = button required, 0x00 = auto power on Note it likely applies to the Minix NEO U1 as well since it uses the same MCU

From your logs: Healthy: 6.12.32-current-meson64 Unhealthy: 6.18.15-current-meson64 Certainly sounds like something changed/broke in a major kernel update? For the near term, I would grab a copy of the 6.12 kernel and keep a copy. The apt tool should have saved a copy in /var/cache/apt/archives, so you should be able to pull a copy from the good system, and use "sudo dpkg -i" to downgrade the other two boards for the time being. If the working node has been upgraded, it's fan will probably stop working as intended after a power cycle. In parallel, the next thing to do is to take a look at the .dtb files for both kernels (amlogic/meson-sm1-odroid-hc4.dtb), and see what's changed. If I have a free evening, I'll take a peek. As @Igor as the board maintainer, you can also file a bug at https://github.com/armbian/build/issues, but could be a bit to get addressed.

@BacchusIX Odroid H4 Plus

@Sponzo that image also doesnt work for me, did you have to unlock to bootloader or something else in dev settings?

@Alexander Polko Do you still have stock firmware in eMMC? You should get some output from the serial uart if you have the stock firmware, otherwise your serial is not working correctly. Also, boot from sdcard only works via u-boot from stock firmware on this board, for the reason I stated above.

Collabora is headed to Stuttgart for XR Expo 2026! Visit us in Hall 2, booth 2C22, to experience the latest around Monado and ElectricMaple, and catch our 2 talks! View the full article