This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1895333
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1895333
Title:
cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
Status in linux package in Ubuntu:
Incomplete
Bug description:
linux-image-generic-hwe-20.04
hello,
since the update to Ubuntu 20.04.1 I can no longer change the
regulatory domain of my QCA9984 cards.
This works fine with Ubuntu 16.04.7 / DD-WRT / OpenWrt.
Or if I build the kernel modules myself .. ("Atheros dynamic user
regulatory testing")
The card has "World" in the EEPROM and is sold worldwide.
[ 2.896628] ath10k_pci 0000:03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[ 2.960023] ath10k_pci 0000:04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[ 3.015612] ath10k_pci 0000:03:00.0: qca9984/qca9994 hw1.0 target
0x01000000 chip_id 0x00000000 sub 168c:cafe
[ 3.015613] ath10k_pci 0000:03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 3.015934] ath10k_pci 0000:03:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[ 3.069593] ath10k_pci 0000:04:00.0: qca9984/qca9994 hw1.0 target
0x01000000 chip_id 0x00000000 sub 168c:cafe
[ 3.069594] ath10k_pci 0000:04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[ 3.069933] ath10k_pci 0000:04:00.0: firmware ver 10.4-3.9.0.2-00124 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate
crc32 ea4c0777
[ 4.247469] ath10k_pci 0000:03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[ 4.298899] ath10k_pci 0000:04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[ 6.980756] ath10k_pci 0000:03:00.0: unsupported HTC service id: 1536
[ 7.087506] ath10k_pci 0000:03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[ 7.125981] ath10k_pci 0000:04:00.0: unsupported HTC service id: 1536
[ 7.149519] ath: EEPROM regdomain: 0x0
[ 7.149520] ath: EEPROM indicates default country code should be used
[ 7.149520] ath: doing EEPROM country->regdmn map search
[ 7.149521] ath: country maps to regdmn code: 0x3a
[ 7.149521] ath: Country alpha2 being used: US
[ 7.149521] ath: Regpair used: 0x3a
[ 7.152614] ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
[ 7.235146] ath10k_pci 0000:04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[ 7.297494] ath: EEPROM regdomain: 0x0
[ 7.297495] ath: EEPROM indicates default country code should be used
[ 7.297495] ath: doing EEPROM country->regdmn map search
[ 7.297496] ath: country maps to regdmn code: 0x3a
[ 7.297496] ath: Country alpha2 being used: US
[ 7.297497] ath: Regpair used: 0x3a
The ath driver incorrectly sets the card to "US" ( phy0 + phy1 )
global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 20), (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)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)
phy#1
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#0
country US: DFS-FCC
(2402 - 2472 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 23), (N/A), AUTO-BW
(5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS, AUTO-BW
(5490 - 5730 @ 160), (N/A, 23), (0 ms), DFS
(5735 - 5835 @ 80), (N/A, 30), (N/A)
(57240 - 63720 @ 2160), (N/A, 40), (N/A)
phy#2 (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 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5190 - 5210 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5210 - 5230 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40MINUS, NO-160MHZ, PASSIVE-SCAN
(5230 - 5250 @ 80), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT,
NO-HT40PLUS, NO-160MHZ, PASSIVE-SCAN
(5250 - 5270 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5270 - 5290 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5290 - 5310 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5310 - 5330 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5490 - 5510 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5510 - 5530 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5530 - 5550 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5550 - 5570 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5570 - 5590 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5590 - 5610 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5610 - 5630 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40MINUS, NO-160MHZ,
PASSIVE-SCAN
(5630 - 5650 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
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
(5710 - 5730 @ 80), (6, 22), (0 ms), DFS, AUTO-BW, NO-HT40PLUS, NO-160MHZ,
PASSIVE-SCAN
(5735 - 5755 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ
(5755 - 5775 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ
(5775 - 5795 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-160MHZ
(5795 - 5815 @ 80), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-160MHZ
(5815 - 5835 @ 20), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-HT40PLUS,
NO-80MHZ, NO-160MHZ
This means that the card works on various channels with a transmission
power that is far too high
country US: DFS-FCC
(5735 - 5835 @ 80), (N/A, 30), (N/A)
30dB = 1W
while in Germany only 25mW are allowed
DE: DFS-ETSI
(5725 - 5875 @ 80), (N/A, 13), (N/A)
So please patch out this eeprom nonsense or activate "Atheros dynamic user
regulatory testing"
- it is also questionable whether the users need individual regdb settings
for each NIC
So that we ubuntu users can operate our Qualcomm WLAN cards with the
correct regdb settings!
5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
03:00.0 Network controller: Qualcomm Atheros QCA9984 802.11ac Wave 2 Wireless
Network Adapter
04:00.0 Network controller: Qualcomm Atheros QCA9984 802.11ac Wave 2 Wireless
Network Adapter
08:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
best regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895333/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
