Can someone help, other than with the Radxa debian os the wifi adapter in fedora or ubuntu is hardlocked and not accessible. How can i resolve this. If the orion is an open linux system there should be a solution.
regards
Hardblocked A8 Wifi-card
1 Like
Agreed. Got the same issue on Ubuntu. The module appears in LSPCI as 61:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller. The driver exists in the kernel drivers files as rtw89_8852be.ko.zst. There definitely is something weird going on here.
my ax210 is meeting same program
So is mine. Hardblocked in rfkill list
Are you all running the firmware in ACPI mode? I am experiencing the same issue on Ubuntu 25.04 with a custom built 6.15-rc5 kernel (commit 0d8d44db295ccad20052d6301ef49ff01fb8ae2d to be precise, with some amdgpu fixes on top). I am using UEFI version 0.3.0-1 in ACPI mode.
The kernel module that is responsible for the card is rtw89_8852be, so after I played with the command sudo rmmod rtw89_8852be && sudo modprobe rtw89_8852be a bit I noticed that the following messages appeared pretty consistently in the kernel log:
[ 5536.901534] rtw89_8852be 0000:61:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin
[ 5536.913475] rtw89_8852be 0000:61:00.0: Firmware version 0.29.29.8 (39dbf50f), cmd version 0, type 5
[ 5536.913487] rtw89_8852be 0000:61:00.0: Firmware version 0.29.29.8 (39dbf50f), cmd version 0, type 3
[ 5537.199747] rtw89_8852be 0000:61:00.0: chip rfe_type is 1
[ 5537.228665] ACPI: \: failed to evaluate _DSM e8c3a8d2-694b-004f-82bd-fe8607803aa7 rev:0 func:6 (0x1001)
[ 5537.229392] rtw89_8852be 0000:61:00.0: rfkill hardware state changed to disable
[ 5537.234066] rtw89_8852be 0000:61:00.0 wlp97s0: renamed from wlan0
I am really out of my depth here, but perhaps the failure to evaluate an entry in one of the ACPI tables forces the kernel to disable the hardware, which would point to a firmware issue.
I am running in ACPI mode, Ubuntu won’t boot in DT on my board.
Just updated to 0.3.0-1, AX210 still hardblocked for me.
My log looks like so (yeah I called my Orion Hyatt as it keeps dying again and again x) ) :
2025-05-12T22:41:11.995595+02:00 HYATT kernel: Intel(R) Wireless WiFi driver for Linux
2025-05-12T22:41:11.995597+02:00 HYATT kernel: cma: __cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12
2025-05-12T22:41:11.995600+02:00 HYATT kernel: cma: number of available pages: => 0 free of 8192 total pages
2025-05-12T22:41:11.995602+02:00 HYATT kernel: iwlwifi 0000:61:00.0: Adding to iommu group 2
2025-05-12T22:41:11.995606+02:00 HYATT kernel: iwlwifi 0000:61:00.0: enabling device (0000 -> 0002)
2025-05-12T22:41:11.995609+02:00 HYATT kernel: ACPI: \: failed to evaluate _DSM 2c176672-0b22-294b-814f-75e4dd26b5fd rev:0 func:0 (0x1001)
2025-05-12T22:41:11.995739+02:00 HYATT kernel: ACPI: \: failed to evaluate _DSM 2c176672-0b22-294b-814f-75e4dd26b5fd rev:0 func:0 (0x1001)
2025-05-12T22:41:11.995756+02:00 HYATT kernel: iwlwifi 0000:61:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
2025-05-12T22:41:11.995763+02:00 HYATT kernel: iwlwifi 0000:61:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
2025-05-12T22:41:11.995777+02:00 HYATT kernel: iwlwifi 0000:61:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz
2025-05-12T22:41:11.995781+02:00 HYATT kernel: iwlwifi 0000:61:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.42
2025-05-12T22:41:11.995785+02:00 HYATT kernel: iwlwifi 0000:61:00.0: loaded firmware version 89.4d42c933.0 ty-a0-gf-a0-89.ucode op_mode iwlmvm
2025-05-12T22:41:11.995791+02:00 HYATT kernel: optee: probing for conduit method.
2025-05-12T22:41:11.995802+02:00 HYATT kernel: optee: revision 3.17 (000000000af95526)
2025-05-12T22:41:11.995807+02:00 HYATT kernel: optee: initialized driver
2025-05-12T22:41:11.995817+02:00 HYATT kernel: input: Microsoft X-Box One Elite 2 pad as /devices/platform/PNP0D10:00/usb1/1-1/1-1.1/1-1.1:1.0/input/input8
2025-05-12T22:41:11.995825+02:00 HYATT kernel: usbcore: registered new interface driver xpad
2025-05-12T22:41:11.995830+02:00 HYATT kernel: cma: __cma_alloc: reserved: alloc failed, req-size: 4 pages, ret: -12
2025-05-12T22:41:11.995849+02:00 HYATT kernel: cma: number of available pages: => 0 free of 8192 total pages
2025-05-12T22:41:11.995855+02:00 HYATT kernel: snd_hda_intel 0000:c1:00.1: Adding to iommu group 0
2025-05-12T22:41:11.995859+02:00 HYATT kernel: snd_hda_intel 0000:c1:00.1: enabling device (0000 -> 0002)
2025-05-12T22:41:11.995863+02:00 HYATT kernel: snd_hda_intel 0000:c1:00.1: Disabling MSI
2025-05-12T22:41:11.995868+02:00 HYATT kernel: snd_hda_intel 0000:c1:00.1: Force to snoop mode by module option
2025-05-12T22:41:11.995885+02:00 HYATT kernel: iwlwifi 0000:61:00.0: reporting RF_KILL (radio disabled)
2025-05-12T22:41:11.995909+02:00 HYATT kernel: nvidia: loading out-of-tree module taints kernel.
2025-05-12T22:41:11.995917+02:00 HYATT kernel: nvidia: module license 'NVIDIA' taints kernel.
2025-05-12T22:41:11.995922+02:00 HYATT kernel: Disabling lock debugging due to kernel taint
2025-05-12T22:41:11.995927+02:00 HYATT kernel: nvidia: module license taints kernel.
2025-05-12T22:41:11.995933+02:00 HYATT kernel: elecom 0003:056E:010C.0001: Fixing up Elecom mouse button count
2025-05-12T22:41:11.995939+02:00 HYATT kernel: iwlwifi 0000:61:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
2025-05-12T22:41:11.995943+02:00 HYATT kernel: iwlwifi 0000:61:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
2025-05-12T22:41:11.995948+02:00 HYATT kernel: iwlwifi 0000:61:00.0: WFPM_AUTH_KEY_0: 0x90
2025-05-12T22:41:11.995952+02:00 HYATT kernel: iwlwifi 0000:61:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
2025-05-12T22:41:11.995957+02:00 HYATT kernel: iwlwifi 0000:61:00.0: Detected RF GF, rfid=0x10d000
2025-05-12T22:41:11.995968+02:00 HYATT kernel: iwlwifi 0000:61:00.0: loaded PNVM version 581d4936
I might be mistaken by a lot but it seems to me that the BIOS does not exchange properly with the mainline kernel yet so as long as the orion o6 is not in mainline, this might work only with radxa’s kernel
Could you try reposting the kernel messages without the noise (e.g. CMA, the Nvidia driver, etc.)? The kernel module that you use is probably iwlwifi, but you can verify it by running sudo lspci -vvv, finding the section that corresponds to the wireless card, and checking the Kernel driver in use entry. Then, assuming that iwlwifi is indeed the correct value, simply execute sudo rmmod iwlwifi && sudo modprobe iwlwifi, and everything should appear right at the end of the kernel log, without any unrelated messages.
I voluntarily left all the so called noise in order not to remove anything that could make sense for knowers.
Also, the issue remains the same, it fails at evaluating _DSM exactly like it does for rtw89