knuxyl

They do something different, intel card works fine. It ended up being a lack of proper PCIe support. I'm not sure if the issue will ever be fixed because radxa sells their own wifi cards that are "special" (don't require full pcie implementation) and they implemented just enough to get the ax210 working, which is a very popular card. I see this a lot with Chinese board makers, even in x86.

I am unable to boot Armbian via ventoy and I do not have the space to backup nor another USB to put Armbian on. I don't have a PC to install Armbian on to test anyways, assuming the x86 doesn't have live cd function. The closest I can find mention of the PCIe interupts with this CPU is on the kernel mailing lists [PATCH v5 4/5] arm64: dts: rockchip: rk3568: Add PCIe v3 nodes And the latest mention of the Rock 3a in the kernel is here from Nov 23. This suggests the possibility of the 6.2 kernel having proper support for PCIe 3.0, but I do not know if it is relevant to my card. [GIT PULL] Rockchip dts64 changes for 6.2 #1 I am not a kernel developer so I do not understand most of it, but it seems as though PCIe might be corrected in the 6.2 kernel, currently in 6.1-rc1. A better interpretation of what is happening in these emails would be great so I and others can know what to expect.

I don't know where else to share this so I'm putting this here. The board recognizes and tries to the load the driver for an AR9462 QCNA222 M.2 WiFi card, but fails. I tried a custom build found on Radxa forum/github, built Armbian myself, and tried an official build. All resulted in the same error. Card was tested and working correctly on 2 different Debian x86 machines. lspci 0000:00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01) 0000:01:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter (rev 01) 0002:20:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd Device 3566 (rev 01) dmesg ath9k 0000:01:00.0: enabling device (0000 -> 0002) ath9k 0000:01:00.0: request_irq failed ath9k: probe of 0000:01:00.0 failed with error -22