topic Re: Re:BE200 regulatory information overly restrictive in Wireless

BE200 regulatory information overly restrictive

kai1024 — Sat, 23 Aug 2025 19:36:21 GMT

Hi,

why is Intel Firmware on this HW:

[ 7.289780] iwlwifi 0001:01:00.0: BAR 0 [mem 0x1b00000000-0x1b00003fff 64bit]: assigned [ 7.289889] iwlwifi 0001:01:00.0: enabling device (0000 -> 0002) [ 7.294448] iwlwifi 0001:01:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x80000000 [ 7.294498] iwlwifi 0001:01:00.0: PCI dev 272b/00f4, rev=0x472, rfid=0x112200 [ 7.294502] iwlwifi 0001:01:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [ 7.319000] iwlwifi 0001:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.4.196 [ 7.320156] iwlwifi 0001:01:00.0: loaded firmware version 96.44729d4e.0 gl-c0-fm-c0-96.ucode op_mode iwlmvm [ 7.722092] iwlwifi 0001:01:00.0: Detected RF FM, rfid=0x112200 [ 7.726589] iwlwifi 0001:01:00.0: loaded PNVM version 8af7618d

so overly restrictive? (compared to country=DE regulations)

iw reg get global country DE: 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 @ 160), (N/A, 23), (N/A), NO-OUTDOOR (57000 - 66000 @ 2160), (N/A, 40), (N/A) phy#0 (self-managed) country DE: 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 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN (5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN (5250 - 5270 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5270 - 5290 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5290 - 5310 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5310 - 5330 @ 160), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5490 - 5510 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5510 - 5530 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5530 - 5550 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5550 - 5570 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5570 - 5590 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5590 - 5610 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5610 - 5630 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, PASSIVE-SCAN (5630 - 5650 @ 220), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, PASSIVE-SCAN (5650 - 5670 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5670 - 5690 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN (5690 - 5710 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN (5735 - 5755 @ 140), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS (5755 - 5775 @ 140), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS (5775 - 5795 @ 140), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS (5795 - 5815 @ 140), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS (5815 - 5835 @ 140), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS (5835 - 5855 @ 140), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS (5855 - 5875 @ 140), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS (5945 - 6425 @ 480), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, PASSIVE-SCAN

Why don't firmware regulations match the country regulations?
This way its impossible to setup 5GHZ hotspot

This doesn't make any sense?

Please fix.

Re:BE200 regulatory information overly restrictive

JeanetteC_Intel — Mon, 25 Aug 2025 07:05:33 GMT

Hello kai1024,

Thank you for posting in Intel Communities.

To get a better understanding of the issue and be able to provide an effective recommendation, please provide the missing key information here:

Is your system a desktop PC or a laptop?
Is the Intel® Wi-Fi 7 BE200 a pre-installed component on your system device or is it an upgrade/replacement component?
Which Linux distribution and version are you using?
Is this a first-time setup for 5GHZ hotspot and won't work or has it previously worked then failed?

Additionally, I highly appreciate you sharing your system configuration so I can fully check and provide you with an accurate fix. This could be possible by downloading the Intel® System Support Utility for the Linux* Operating System.

1) Download the Intel® System Support Utility for the Linux* operating system and save the ssu.tar.gz file to your system.

2) Extract the ssu.sh file from ssu.tar.gz and save to your system.

3) To run the ssu.sh script from a Linux* terminal, Open Applications->Accessories->Terminal.

4) From the current directory, navigate to the current folder where the ssu.sh file resides. For example, if you saved the ssu.sh file to a folder called SSU File, the command would be cd SSU File.

5) Run the ssu.sh file using this command: ./ssu.sh <parameter=0|1> where 0 = off and 1 = enabled.

6) Use the parameter definitions included in the readme to determine which parameter to use.

Note:

If no parameter is specified and only ./ssu.sh is run, it captures all system information with the exception of 3rd party logs that must be specified.

If no output file is specified, the Intel System Support Utility writes the output to the <systemname>.txt file.

7) You can view or open the output file in most text editors. However, view the file in a word processing software, such as WordPad*, for better formatted viewing. In addition, the Intel® System Support Utility for Windows can open the output file, which provides you with the capability of viewing the Linux information in an easy-to-view user interface.

I look forward to your response.

Best regards,

JeanetteC.

Intel® Customer Support Technician

Re: Re:BE200 regulatory information overly restrictive

kai1024 — Mon, 25 Aug 2025 16:17:44 GMT

Hi,

its a new Intel BE200NGW M.2 card on Ubuntu 2025.04

But after reading this:

https://bugzilla.kernel.org/show_bug.cgi?id=206469#c2

https://superuser.com/questions/1645797/using-hostapd-on-ubuntu-20-04-to-create-5ghz-access-point-channel-153-primary/1809751#1809751

I came to the conclusion that this is an intentional restriction so I have replaced the card already, so I'm afraid I can't run support utility anymore.

Re:BE200 regulatory information overly restrictive

JeanetteC_Intel — Tue, 26 Aug 2025 08:08:44 GMT

Hello kai1024,

Thank you for researching this thoroughly. I understand your decision to replace the card given the restrictions you discovered - that's completely reasonable.

Since you've found an alternative solution, I'll close this case. If you need future assistance with Intel products, please submit a new question as this thread will no longer be monitored.

Sincerely,

JeanetteC.

Intel Customer Support Technician