Wireless
Participate in insightful discussions regarding issues related to Intel® Wireless Adapters and technologies
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
8599 Discussions

Intel AX101 WRDD/DFS issues on Debian 13 Trixie

RicoBelo
Beginner
‎10-22-2025 08:40 AM
245 Views

I have a chinese Mini-PC with an Intel N150 CPU and a soldered Intel AX101 wireless card running Linux Debian 13 (Trixie)

want to use the wireless card as an AP, which is supported by AX101 chip and driver, in 802.11ax mode on the 5GHz band.

As I live in France, I forced cfg80211 module to load WRDD for France with the kernel parameter 

cfg80211.ieee80211_regdom=FR

The global registration is then correctly globally set to FR, but the wireless card is kept unconfigured with no country and no DFS information:

# iw reg get
global
country FR: DFS-ETSI
	(2400 - 2483 @ 40), (N/A, 20), (N/A)
	(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
	(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
	(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
	(5725 - 5875 @ 80), (N/A, 13), (N/A)
	(5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR
	(57000 - 71000 @ 2160), (N/A, 40), (N/A)

phy#0 (self-managed)
country 00: DFS-UNSET
	(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ
	(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
	(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
	(5170 - 5190 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5530 - 5550 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5550 - 5570 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5570 - 5590 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5590 - 5610 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5610 - 5630 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5630 - 5650 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN
	(5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, NO-HT40PLUS, NO-80MHZ, NO-160MHZ, NO-320MHZ, PASSIVE-SCAN

At least I can see many channels in the 5GHz band available for DFS. So I try a minimalistic hostapd.conf file to start an AP centered on channel 100 with 802.11ax, but it fail : hostapd enumerates all channels in the 5GHz band with "No IR" flag :

nl80211: 2402-2437 @ 40 MHz 22 mBm
nl80211: 2422-2462 @ 40 MHz 22 mBm
nl80211: 2447-2482 @ 40 MHz 22 mBm
nl80211: 5170-5190 @ 80 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5190-5210 @ 80 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5210-5230 @ 80 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5230-5250 @ 80 MHz 22 mBm (no outdoor) (no IR)
nl80211: 5250-5270 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5270-5290 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5290-5310 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5310-5330 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5490-5510 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5510-5530 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5530-5550 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5550-5570 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5570-5590 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5590-5610 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5610-5630 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5630-5650 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5650-5670 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5670-5690 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5690-5710 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5710-5730 @ 80 MHz 22 mBm (DFS) (no IR)
nl80211: 5735-5755 @ 80 MHz 22 mBm (no IR)
nl80211: 5755-5775 @ 80 MHz 22 mBm (no IR)
nl80211: 5775-5795 @ 80 MHz 22 mBm (no IR)
nl80211: 5795-5815 @ 80 MHz 22 mBm (no IR)
nl80211: 5815-5835 @ 20 MHz 22 mBm (no IR)
nl80211: Added 802.11b mode based on 802.11g information
nl80211: Mode IEEE 802.11g: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED]
nl80211: Mode IEEE 802.11a: 5180[NO_IR] 5200[NO_IR] 5220[NO_IR] 5240[NO_IR] 5260[NO_IR][RADAR] 5280[NO_IR][RADAR] 5300[NO_IR][RADAR] 5320[NO_IR][RADAR] 5340[DISABLED] 5360[DISABLED] 5380[DISABLED] 5400[DISABLED] 5420[DISABLED]
nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484[DISABLED]
Frequency 5500 (primary) not allowed for AP mode, flags: 0x15b NO-IR RADAR
Primary frequency not allowed
wlo1: IEEE 802.11 Configured channel (100) or frequency (5500) (secondary_channel=0) not found from the channel list of the current mode (2) IEEE 802.11a
wlo1: IEEE 802.11 Hardware does not support configured channel
Could not select hw_mode and channel. (-3)
wlo1: interface state COUNTRY_UPDATE->DISABLED
wlo1: AP-DISABLED

 So I tried to enable DFS and force 80MHz band centering between channel 100 and 106 with a more elaborated hostapd config. Bu once again, hostapd fails to start because it fails to start DFS scan.

I was able to start hostapd in 802.11ax on the 2.4GHz band as there is no DFS gotchas on the band, but at the price of terrific bandwidth of less than 90Mbps.

I join my dmesg, config files, and iw outputs in attachements

So at this point I assume the firmware forbid me to use the card in AP mode on 5Ghz band because of DFS, I don't really understand how and why. So can you help me to fix this ?

Preview file
1 KB
Preview file
2 KB
hostapd_minimal_80211ax_24GHz.log
Preview file
73 KB
Preview file
1 KB
hostapd_minimal_80211ax_nodfs.log
Preview file
4 KB
Preview file
2 KB
hostapd_80211ax_dfs.log
Preview file
15 KB
0 Kudos

Link Copied

5 Replies
JedG_Intel
Moderator
‎10-22-2025 11:32 PM
164 Views

Hello RicoBelo,

 

Thank you for posting on Intel Community Forum. I appreciate your effort for sharing as much information as you could. This will definitely help with the investigation moving forward.

 

To address the issue properly, kindly share the information below.

 

1. What is the make and model of your Mini-PC? If possible, kindly share the direct link to it.

2. Were you previously able to configure and use the wireless card according to your preferred settings?

3. What is the Kernel and firmware version?

 

I look forward to your response.

 

Best regards

Jed G.

Intel Customer Support Technician


0 Kudos
Copy link
RicoBelo
Beginner
‎10-23-2025 12:06 AM
126 Views
In response to JedG_Intel

Hello Jed, thanks for your support

 

1. I brought this mini-pc on a French second hand market website called "leboncoin.fr" which will obviously not your :D, but the miniPC is branded "SOAYAN N2" and I found references on Alibaba and also Amazon :

https://www.amazon.fr/SOAYAN-Lake-N150-Computer-Business-Heimkino/dp/B0DTF11ZFT

https://www.alibaba.com/product-detail/SOAYAN-2025-Factory-Direct-N2-Mini_1601390125662.html?spm=a2700.details-description.0.0.79eeM2XVM2XVqW

This is obviously a generic product sold to many distributors, and unfortunately I was not able to find the manufacturer or any support.

 

2. Initially I didn't used the wireless at all : I use this server to share and transcode media files with Jellyfin over Ethernet, thanks to it great CPU and IGP (the N1xx series are really great and green products !)

 But as I recently added a new FireTV 4K with a weak wireless connection because my "real AP" is too far, and the mini-pc is just next to the FireTV stick, I through bridging the wireless card would be an far more elegant option than adding another AP !

The FireTV 4K is the reason why I want 802.11ax over 5Ghz : I want to archieve at least 500Mbps bandwidth with low latency

 

3. You can find kernel and firmware details in dmesg.txt output. For reference :

# uname -a
Linux jellyfin 6.12.48+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64 GNU/Linux

# dmesg |grep -P 'iwl|80211'
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.12.48+deb13-amd64 root=/dev/mapper/vg_sys-root ro cfg80211.ieee80211_regdom=FR
[    0.021764] Kernel command line: BOOT_IMAGE=/vmlinuz-6.12.48+deb13-amd64 root=/dev/mapper/vg_sys-root ro cfg80211.ieee80211_regdom=FR
[    3.414369] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.510206] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    3.519644] iwlwifi 0000:00:14.3: Detected crf-id 0x501, cnv-id 0x80400 wfpm id 0x80000030
[    3.520291] iwlwifi 0000:00:14.3: PCI dev 54f0/0244, rev=0x370, rfid=0x10c000
[    3.520940] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX101
[    3.526646] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.42
[    3.527662] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    3.528420] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    3.529024] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    3.529612] iwlwifi 0000:00:14.3: loaded firmware version 89.4d42c933.0 so-a0-hr-b0-89.ucode op_mode iwlmvm
[    4.058973] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[    4.059024] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    4.059032] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    4.059041] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    4.059802] iwlwifi 0000:00:14.3: Detected RF HR1 B3, rfid=0x10c000
[    4.060202] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[    4.101019] iwlwifi 0000:00:14.3: base HW address: 94:b6:09:42:1d:b9
[    4.150719] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0

I also forced regulatory information database from upstream instead of Debian DB:

# update-alternatives --get-selections | grep regulatory
regulatory.db                  manual   /lib/firmware/regulatory.db-upstream
In response to JedG_Intel
0 Kudos
Copy link
RicoBelo
Beginner
‎10-23-2025 08:49 AM
126 Views
In response to JedG_Intel

Hello Jed,

 

1. This is a generic chinese mini-pc, branded as "SOAYAN N2 Mini PC N150". You can find it on AliBaba as well as Amazon :

https://french.alibaba.com/product-detail/SOAYAN-2025-Factory-Direct-N2-Mini-1601390125662.html

https://www.amazon.fr/SOAYAN-Lake-N150-Computer-Business-Heimkino/dp/B0DTF11ZFT

I search for an eventual official website but didn't found anything suitable to request any support from the manufacturer.

 

2. Not really : I usually prefers Ethernet connection when possible so wireless was disabled. The reason why I need to activate it as AP is this host is exclusively used for transcoding media content using Jellyfin, and I just added an Amazon FireTV 4K stick with a weak Wifi connection because my "real" AP is to far away, so as the Mini-PC is just next to the FireTV stick, I thought far more elegant bridging its connection as an AP than installing another "real" AP for just one device.

 

3. I think you already have these information on the dmesg.txt attached file. FYI:

# uname -a
Linux jellyfin 6.12.48+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.48-1 (2025-09-20) x86_64 GNU/Linux

# dmesg | grep -P '80211|iwl'
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-6.12.48+deb13-amd64 root=/dev/mapper/vg_sys-root ro cfg80211.ieee80211_regdom=FR
[    0.021764] Kernel command line: BOOT_IMAGE=/vmlinuz-6.12.48+deb13-amd64 root=/dev/mapper/vg_sys-root ro cfg80211.ieee80211_regdom=FR
[    3.414369] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.510206] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    3.519644] iwlwifi 0000:00:14.3: Detected crf-id 0x501, cnv-id 0x80400 wfpm id 0x80000030
[    3.520291] iwlwifi 0000:00:14.3: PCI dev 54f0/0244, rev=0x370, rfid=0x10c000
[    3.520940] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX101
[    3.526646] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.42
[    3.527662] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    3.528420] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    3.529024] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[    3.529612] iwlwifi 0000:00:14.3: loaded firmware version 89.4d42c933.0 so-a0-hr-b0-89.ucode op_mode iwlmvm
[    4.058973] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[    4.059024] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[    4.059032] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[    4.059041] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[    4.059802] iwlwifi 0000:00:14.3: Detected RF HR1 B3, rfid=0x10c000
[    4.060202] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[    4.101019] iwlwifi 0000:00:14.3: base HW address: 94:b6:09:42:1d:b9
[    4.150719] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0

 

 So:

kernel is stock Debian 13 (kernel 6.12.48)

firmware blob is 89.4d42c933.0 so-a0-hr-b0-89.ucode

I also need to precise that I switched to upstream regulatory database instead the the stock Debian provided :

# update-alternatives --get-selections | grep regulatory
regulatory.db                  manual   /lib/firmware/regulatory.db-upstream

 

In response to JedG_Intel
0 Kudos
Copy link
JedG_Intel
Moderator
‎10-24-2025 12:00 AM
114 Views

Hello RicoBelo,

 

Thank you for sharing all this information. I really appreciate that you shared a reference link to your Mini-PC. I'll investigate this matter internally and I'll get back in touch as soon as possible.

 

Best regards

Jed G.

Intel Customer Support Technician


0 Kudos
Copy link
RicoBelo
Beginner
‎10-24-2025 12:27 AM
77 Views
In response to JedG_Intel

Thanks for your help, I really appreciate

Hope you'll be able to find a solution

 

Regards,

 

Eric

In response to JedG_Intel
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.