WCN7851: Wifi 6E support in Azerbaijan/Serbia

Bug #2127965 reported by AceLan Kao
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
HWE Next
New
Undecided
Unassigned
linux-firmware (Ubuntu)
Fix Released
Undecided
Unassigned
Noble
Confirmed
Undecided
AceLan Kao
Plucky
Confirmed
Undecided
AceLan Kao
Questing
Confirmed
Undecided
AceLan Kao

Bug Description

[Impact]
To support wifi 6GHz in Azerbaijan and Serbia for WCN7851

[Fix]
The WCN7850 firmware need to be updated
1d588f106 ath12k: WCN7850 hw2.0: update board-2.bin
99720d022 ath12k: WCN7850 hw2.0: update board-2.bin

[Test]
1. sudo iw reg set AZ
2. sudo iw reg get
There are 6GHz @ 160 under "country AZ"

[Where problems could occur]
The firmware affects WCN7850/WCN7851 cards.

AceLan Kao (acelankao)
Changed in linux-firmware (Ubuntu Noble):
status: New → In Progress
Changed in linux-firmware (Ubuntu Plucky):
status: New → In Progress
Changed in linux-firmware (Ubuntu Questing):
status: New → In Progress
Changed in linux-firmware (Ubuntu Noble):
assignee: nobody → AceLan Kao (acelankao)
Changed in linux-firmware (Ubuntu Plucky):
assignee: nobody → AceLan Kao (acelankao)
Changed in linux-firmware (Ubuntu Questing):
assignee: nobody → AceLan Kao (acelankao)
AceLan Kao (acelankao)
tags: added: jira-somerville-2728 oem-priority somerville
Changed in linux-firmware (Ubuntu):
status: New → Invalid
tags: added: kernel-daily-bug
Juerg Haefliger (juergh)
Changed in linux-firmware (Ubuntu Questing):
status: In Progress → Fix Committed
Juerg Haefliger (juergh)
Changed in linux-firmware (Ubuntu Plucky):
status: In Progress → Fix Committed
Changed in linux-firmware (Ubuntu Noble):
status: In Progress → Fix Committed
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello AceLan, or anyone else affected,

Accepted linux-firmware into questing-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20250901.git993ff19b-0ubuntu1.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-questing to verification-done-questing. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-questing. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello AceLan, or anyone else affected,

Accepted linux-firmware into plucky-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20250317.git1d4c88ee-0ubuntu1.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-plucky to verification-done-plucky. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-plucky. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello AceLan, or anyone else affected,

Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/20240318.git3b128b60-0ubuntu2.20 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Timo Aaltonen (tjaalton)
tags: added: verification-needed-noble verification-needed-plucky verification-needed-questing
Revision history for this message
David Perry (davidperry) wrote :

I attempted to validate this on Noble using a Lenovo Thinkpad machine containing the WCN7850 card.

From my testing, I wasn't able to see the "6GHz @ 160" band visible under the AZ region once set.

this is my output:
country AZ: DFS-ETSI
        (2402 - 2482 @ 40), (N/A, 20), (N/A)
        (5170 - 5250 @ 80), (N/A, 18), (N/A), AUTO-BW
        (5250 - 5330 @ 80), (N/A, 18), (0 ms), DFS, AUTO-BW

Could I get have more context on what to expect here to clarify that I'm understanding/testing this correctly?

OS: Noble 24.04
Kernel: 6.14.0-1015-oem
Linux-firmware version : 20240318.git3b128b60-0ubuntu2.20

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

did you reboot after installing the firmware update?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

also, this needs to be tested on plucky and questing too

Revision history for this message
David Perry (davidperry) wrote :

I tried rebooting as well as restarting the module with "modprobe -r ath12k" & "modprobe ath12k".

I also tried manually replacing the firmware .bin files but didn't find success.

I'll cross reference with plucky and questing next

Revision history for this message
Mario Limonciello (superm1) wrote :

AFAICT we only have "US" cards; I would expect the hardware doesn't allow picking non-US frequencies while in the "US". If this really needs to be validated that it works in those regions, I don't expect that hardware to be readily available to the general public.

Maybe for the purposes of this SRU can we have a "no-regressions found" test instead of "can pick the new frequencies test"?

Revision history for this message
David Perry (davidperry) wrote :

Thanks for the information Mario,

In the event that "no regressions found" testing is acceptable, I've gone ahead and validated the remaining firmware packages with no regressions seen. If this is okay, please go ahead and move all 3 to verification-complete

Lenovo Thinkpad w/WCN7850 device
________________________________
OS: Questing 25.10
linux-firmware version : 20250901.git993ff19b-0ubuntu1.3
Kernel: 6.17.0-6-generic

OS: Plucky 25.04
linux-firmware version: 20250317.git1d4c88ee-0ubuntu1.10
Kernel : 6.14.0-35-generic

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Based on comment #4, the country was set to AZ. Are we sure this is not a failed verification?

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I played with different countries with my local wifi card (which is not the one for this bug), and I do see different outputs under the country section in the "iw reg get" command, so switching to different countries is making that output change at least.

Revision history for this message
Mario Limonciello (superm1) wrote :

As I understand it there will be wireless beacon frames that are advertised by local access points, and the hardware can react to them.

If you receive a beacon for US, then the hardware can limit frequencies to those allowed in the US region no matter what country you've set.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

@AceLan, since you filed the bug, do you have a system where the bug manifests itself, and where you can verify the fix?

Revision history for this message
AceLan Kao (acelankao) wrote :

@Andreas,

No, I don't have h/w on hand, rely on ODM to verify.

Revision history for this message
Juerg Haefliger (juergh) wrote :

This failed verification by the ODM so I'm going to revert the changes.

Timo Aaltonen (tjaalton)
Changed in linux-firmware (Ubuntu Questing):
status: Fix Committed → Triaged
Changed in linux-firmware (Ubuntu Plucky):
status: Fix Committed → Triaged
Changed in linux-firmware (Ubuntu Noble):
status: Fix Committed → Confirmed
Changed in linux-firmware (Ubuntu Plucky):
status: Triaged → Confirmed
Changed in linux-firmware (Ubuntu Questing):
status: Triaged → Confirmed
David Perry (davidperry)
Changed in linux-firmware (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Jan Iversen (janiv) wrote :

Hello,

I think, I have the same problem. After installing the firmware from the proposed-repository, my Thinkpad connects to my wifi with wifi 7, 160 Mhz.

I have an AMD Thinkpad T14 Gen 5 with a qualcomm WCN785x (Fastconnect 7800) card installed.

I am living in Germany.

Revision history for this message
Jan Iversen (janiv) wrote :

There was a new firmware-package in the proposed-updates. After installation, my wifi cannot connect any more to 5 Ghz...

linux-firmware/questing-updates,questing-proposed,now 20250901.git993ff19b-0ubuntu1.4

jan@jupiter:~$ iw dev wlp2s0 link
Connected to 34:e1:a9:73:82:d0 (on wlp2s0)
 SSID: Tatooine
 freq: 2437.0
 RX: 1673664 bytes (3386 packets)
 TX: 607021 bytes (1667 packets)
 signal: -52 dBm
 rx bitrate: 229.4 MBit/s EHT-MCS 9 EHT-NSS 2 EHT-GI 0
 tx bitrate: 286.7 MBit/s EHT-MCS 11 EHT-NSS 2 EHT-GI 0
 bss flags: short-preamble short-slot-time
 dtim period: 1
 beacon int: 100

country 00: DFS-UNSET
 (755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
 (2402 - 2472 @ 40), (N/A, 20), (N/A)
 (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
 (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
 (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
 (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
 (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
 (57240 - 63720 @ 2160), (N/A, 0), (N/A)

phy#0 (self-managed)
country DE: DFS-ETSI
 (2402 - 2482 @ 40), (N/A, 20), (N/A), NO-80MHZ, NO-160MHZ, NO-320MHZ
 (5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW, NO-320MHZ
 (5250 - 5330 @ 80), (N/A, 23), (0 ms), NO-OUTDOOR, DFS, AUTO-BW, NO-320MHZ
 (5490 - 5590 @ 80), (N/A, 30), (0 ms), DFS, AUTO-BW, NO-320MHZ
 (5590 - 5650 @ 40), (N/A, 30), (600000 ms), DFS, AUTO-BW, NO-320MHZ
 (5650 - 5710 @ 40), (N/A, 30), (0 ms), DFS, AUTO-BW, NO-320MHZ
 (5735 - 5855 @ 80), (N/A, 14), (N/A), AUTO-BW, NO-320MHZ
 (5855 - 5875 @ 20), (N/A, 14), (N/A), AUTO-BW, NO-320MHZ
 (5945 - 6425 @ 320), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW

Revision history for this message
Jan Iversen (janiv) wrote :

I installed now the package linux-firmware_20250901.git993ff19b-0ubuntu1.3_all.deb (so the older one). Wifi works now as expected on my machine.

jan@jupiter:~/Downloads$ iw dev wlp2s0 link
Connected to 26:e1:a9:73:82:d0 (on wlp2s0)
 SSID: Tatooine
 Link 0 BSSID 34:e1:a9:73:82:d0
  freq: 2437.0
 Link 1 BSSID 36:e1:a9:73:82:d0
  freq: 5520.0
MLD 26:e1:a9:73:82:d0 stats:
 RX: 6321001 bytes (17703 packets)
 TX: 478239 bytes (1506 packets)
 signal: -53 dBm
 tx bitrate: 1729.6 MBit/s 160MHz EHT-MCS 8 EHT-NSS 2 EHT-GI 0
 bss flags:
 dtim period: 1
 beacon int: 100

I hope this information helps you....

Revision history for this message
Juerg Haefliger (juergh) wrote :

This bug report is about adding Wifi 6E support in Azerbaijan/Serbia, nothing else.

If you encounter problems with the current package from updates, you need to file a separate bug.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

resolute has the changes already, 'invalid' was just as correct for it

Changed in linux-firmware (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.