Additional observation (kernel 6.14 comparison):
On kernel 6.14.0-37-generic (working), iw reg get shows phy#0 still
self-manages and reports country 00, however the restrictive NO-80MHZ,
NO-160MHZ, NO-320MHZ flags are absent:
phy#0 (self-managed)
country 00: DFS-UNSET
(5170 - 5330 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5735 - 5895 @ 160), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
On kernel 6.17.0-14-generic (broken), those same entries include NO-80MHZ,
NO-160MHZ, NO-320MHZ, and scan start failures occur immediately after boot.
This suggests the regression in 6.17 is causing the firmware to initialize with
overly restrictive channel flags, preventing 5GHz scanning entirely.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2143056
Title:
ath12k/WCN7850 (FastConnect 7800) 5GHz scan failure on kernel 6.17 --
works on 6.14
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2143056/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
