[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
@vicamo
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=6f8c8bf4c7c9be1c42088689fd4370e06b46608a
"ath10k: fix module load regression with iram-recovery feature"
new patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Triaged
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[7.047910] ath10k_pci :03:00.0: failed to copy target iram contents:
-12
[7.103260] ath10k_pci :03:00.0: could not init core (-12)
[7.103267] ath10k_pci :03:00.0: could not probe fw (-12)
[7.108570] ath10k_pci :04:00.0: failed to copy target iram contents:
-12
[7.163247]
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
@vicamo
yes this is the right patch and thank you!
I have updated the link in comment #12
and tested your PPA
5.11.0-2037-generic #41~20.04.2+lp1939937.2.ath10k.iram-Ubuntu SMP Mon
Sep 27 06:29: x86_64 x86_64 x86_64 GNU/Linux
[3.521734] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[3.579723] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[3.639858] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100
chip_id 0x sub 168c:cafe
[3.639862] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[3.640195] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 723f9771
[3.688745] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100
chip_id 0x sub 168c:cafe
[3.688749] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[3.689089] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 723f9771
[4.875609] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.918482] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[7.578121] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.598799] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.640829] ath: EEPROM regdomain sanitized
[7.640831] ath: EEPROM regdomain: 0x64
[7.640832] ath: EEPROM indicates we should expect a direct regpair map
[7.640833] ath: Country alpha2 being used: 00
[7.640834] ath: Regpair used: 0x64
[7.644614] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0
[7.660776] ath: EEPROM regdomain sanitized
[7.660778] ath: EEPROM regdomain: 0x64
[7.660779] ath: EEPROM indicates we should expect a direct regpair map
[7.660780] ath: Country alpha2 being used: 00
[7.660781] ath: Regpair used: 0x64
[7.675279] ath10k_pci :04:00.0 wlp4s0: renamed from wlan0
works!
i will watch this and let you know as soon as the patch is in linux-next
i think the old (first patch) can be removed then
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Triaged
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
A little update:
a new patch has been released on the ath10k mailing list and has been
merged into the ath git
the patch is currently in "master-pending"
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/commit/?h=master-
pending=973de582639a1e45276e4e3e2f3c2d82a04ad0a6
have applied the patch to my linux-hwe-5.11 kernel and it works
with the patch the error message is completely gone
5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
[3.262867] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[3.322339] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0
reset_mode 0
[3.379884] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100
chip_id 0x sub 168c:cafe
[3.379888] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[3.380218] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 723f9771
[3.438075] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100
chip_id 0x sub 168c:cafe
[3.438079] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[3.438418] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 723f9771
[4.617452] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.671543] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[7.301463] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.362170] ath: EEPROM regdomain sanitized
[7.362172] ath: EEPROM regdomain: 0x6c
[7.362173] ath: EEPROM indicates we should expect a direct regpair map
[7.362174] ath: Country alpha2 being used: 00
[7.362174] ath: Regpair used: 0x6c
[7.362258] ath: EEPROM regdomain: 0x8114
[7.362259] ath: EEPROM indicates we should expect a country code
[7.362259] ath: doing EEPROM country->regdmn map search
[7.362260] ath: country maps to regdmn code: 0x37
[7.362260] ath: Country alpha2 being used: DE
[7.362261] ath: Regpair used: 0x37
..
best regards
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
5.13.0-1011-oem #15-Ubuntu SMP Fri Aug 27 09:45:09 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux
[6.954194] ath10k_pci :03:00.0: No hardware memory
[6.954197] ath10k_pci :03:00.0: failed to copy target iram contents: -12
[6.985209] ath10k_pci :04:00.0: No hardware memory
[6.985213] ath10k_pci :04:00.0: failed to copy target iram contents: -12
[7.060527] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
[7.106011] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp
max-sta 512 raw 0 hwcrypto 1
works
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[4.463156]
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
So "focal-proposed" offers me the update "linux-image-5.11.0-34-generic"
5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
[7.234159] ath10k_pci :03:00.0: failed to copy target iram contents: -12
[7.242923] ath10k_pci :04:00.0: failed to copy target iram contents: -12
[7.291070] ath10k_pci :03:00.0: could not init core (-12)
[7.291076] ath10k_pci :03:00.0: could not probe fw (-12)
[7.299146] ath10k_pci :04:00.0: could not init core (-12)
[7.299169] ath10k_pci :04:00.0: could not probe fw (-12)
it was clear that the patch is not in the kernel and thanks for wasting my time.
Without concrete information I test nothing at all.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
Which kernel should I test?
Please be more precise.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[7.047910] ath10k_pci :03:00.0: failed to copy target iram contents:
-12
[7.103260] ath10k_pci :03:00.0: could not init core (-12)
[7.103267] ath10k_pci :03:00.0: could not probe fw (-12)
[7.108570] ath10k_pci :04:00.0: failed to copy target iram contents:
-12
[7.163247] ath10k_pci :04:00.0: could not init core (-12)
[7.163268] ath10k_pci :04:00.0: could not probe fw (-12)
In the ath10k mailing list I
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
"Acked-by: Tim Gardner
I think for Hirsute this could wait until its at least in linux-next."
I have looked into the Hirsute Linux firmware package
linux-firmware_1.197_all.deb
The header of the QCA9984 firmware file says:
QCA-ATH10K 10.4-3.9.0.2-00131
This means that QCA9984 cards are not functional under Hirsute for the
time being.
so users have only the possibility to downgrade the firmware to 70 to 91
to get a working card
With the packages from Hirsute alone, the cards are definitely not
functional.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load capability
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
In Progress
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Commit 9af7c32ceca8 ("ath10k: add target IRAM recovery feature support")
in v5.11 fails firmware loading without IRAM recovery feature. However,
the latest firmware from
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
doesn't support IRAM, it follows new official ath10k firmwares may no
longer be loadable for kernel newer than v5.11.
[Fix]
A fix is proposed to
http://lists.infradead.org/pipermail/ath10k/2021-July/012729.html that
turns the lack/failure of IRAM recovery support a warning instead.
[Test Case]
With this fix, kernel gives errors about the IRAM supportness, but
proceeds to remaining procedures as before.
ath10k_pci :04:00.0: No hardware memory
ath10k_pci :04:00.0: failed to copy target iram contents: -12
ath10k_pci :07:00.0: No hardware memory
ath10k_pci :07:00.0: failed to copy target iram contents: -12
[Where problems could occur]
So the IRAM recovery feature may or may not be supported in the
officially released firmware, and people meet problems when using
non-IRAM supported firmware may still have a fallback to use older, but
IRAM recovery supported ones.
== original bug report ==
Hello, I use Ubuntu 20.04.2 LTS.
The kernel was recently updated to 5.11
5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
Since then the ath10k_core driver for my QCA9984 card is broken and
only loads ~3 firmware versions from the 3.9.0.2 branch
https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2
The firmware versions 70 / 86 / 91 are functional (but these firmware
versions are already 2 years old)
Responsible for this is the defective patch "ath10k: add target IRAM
recovery feature support"
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8
If I understand the patch correctly then the driver tries to load
firmware with the feature "iram recovery" into the memory of the host
(for recvovery purposes).
If this fails, the firmware is discarded and the network controller
remains unusable.
Of course, this is not a desirable behavior for optional firmware
features.
dmesg:
[3.074952] ath: loading out-of-tree module taints kernel.
[3.090522] ath: module verification failed: signature and/or required key
missing - tainting kernel
[3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5
features
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery
crc32 5f41acd7
[4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.163247] ath10k_pci :04:00.0: could not init core (-12) [7.163268] ath10k_pci :04:00.0: could not probe fw (-12) In the ath10k mailing list I found a second patch which makes it possible to load the latest firmware on the card again. https://www.mail-archive.com/ath10k@lists.infradead.org/msg13655.html I have tested the patch and it works. dmesg: [18245.610112] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.674800] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.731606] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.731620] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.733172] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18245.790380] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.790383] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.790703] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18246.963760] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
$ sudo apt-get install \ > linux-image-unsigned-5.11.0-2033-generic \ > linux-modules-extra-5.11.0-2033-generic \ > linux-headers-5.11.0-2033-generic Holen:1 http://ppa.launchpad.net/vicamo/ppa-1939937/ubuntu focal/main amd64 linux-hwe-5.11-headers-5.11.0-2033 all 5.11.0-2033.35~20.04.1+lp1939937.1.ath10k.iram [12,0 MB] Holen:2 http://ppa.launchpad.net/vicamo/ppa-1939937/ubuntu focal/main amd64 linux-headers-5.11.0-2033-generic amd64 5.11.0-2033.35~20.04.1+lp1939937.1.ath10k.iram [1.863 kB] Holen:3 http://ppa.launchpad.net/vicamo/ppa-1939937/ubuntu focal/main amd64 linux-modules-5.11.0-2033-generic amd64 5.11.0-2033.35~20.04.1+lp1939937.1.ath10k.iram [16,2 MB] Holen:4 http://ppa.launchpad.net/vicamo/ppa-1939937/ubuntu focal/main amd64 linux-image-unsigned-5.11.0-2033-generic amd64 5.11.0-2033.35~20.04.1+lp1939937.1.ath10k.iram [10,3 MB] Holen:5 http://ppa.launchpad.net/vicamo/ppa-1939937/ubuntu focal/main amd64 linux-modules-extra-5.11.0-2033-generic amd64 5.11.0-2033.35~20.04.1+lp1939937.1.ath10k.iram [42,4 MB] Es wurden 82,8 MB in 8 s geholt (10,2 MB/s). uname -a ... 5.11.0-2033-generic #35~20.04.1+lp1939937.1.ath10k.iram-Ubuntu SMP Thu Aug 19 16:37: x86_64 x86_64 x86_64 GNU/Linux dmesg | grep ath [3.279110] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.355016] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.393327] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.393330] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.393655] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [3.475304] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.475308] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.475639] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [4.624937] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.704618] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.202830] ath10k_pci :03:00.0: No hardware memory [7.202833] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.309047] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp max-sta 512 raw 0 hwcrypto 1 [7.371208] ath: EEPROM regdomain sanitized [7.371210] ath: EEPROM regdomain: 0x64 [7.371211] ath: EEPROM indicates we should expect a direct regpair map [7.371212] ath: Country alpha2 being used: 00 [7.371213] ath: Regpair used: 0x64 [7.373346] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0 [7.382821] ath10k_pci :04:00.0: No hardware memory [7.382824] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.501740] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp max-sta 512 raw 0 hwcrypto 1 [7.563210] ath: EEPROM regdomain sanitized [7.563211] ath: EEPROM regdomain: 0x64 [7.563212] ath: EEPROM indicates we should expect a direct regpair map [7.563213] ath: Country alpha2 being used: 00 [7.563214] ath: Regpair used: 0x64 [ 10.009210] ath10k_pci :03:00.0: No hardware memory [ 10.009213] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [ 10.207585] ath10k_pci :03:00.0: Unknown eventid: 36933 [ 10.215774] ath10k_pci :04:00.0 wlp4s0: renamed from wlan0 [ 12.941647] ath10k_pci :04:00.0: No hardware memory [ 12.941650] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [ 13.166283] ath10k_pci :04:00.0: Unknown eventid: 36933 the kernel works but I don't really understand why you set "linux (Ubuntu Focal)" to invalid as said the patch should be back ported to all 5.11 kernels i use the HWE kernel in Focal and it was recently pushed to 5.11 but according to the ticket description you added the linux-oem-5.13 kernel - i honestly don't understand that - but anyway -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: Triaged Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Hirsute: New Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Triaged Status in
[Kernel-packages] [Bug 1939937] Re: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
** Tags removed: ath10k ** Tags added: amd64 ** Tags removed: amd64 ** Tags added: ath10k ** Tags removed: ath10k ** Tags added: ath10k linux ** Tags added: amd64 ** Tags added: qca9984 -- 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/1939937 Title: ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability Status in linux package in Ubuntu: New Bug description: Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.163247] ath10k_pci :04:00.0: could not init core (-12) [7.163268] ath10k_pci :04:00.0: could not probe fw (-12) In the ath10k mailing list I found a second patch which makes it possible to load the latest firmware on the card again. https://www.mail-archive.com/ath10k@lists.infradead.org/msg13655.html I have tested the patch and it works. dmesg: [18245.610112] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.674800] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.731606] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.731620] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.733172] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18245.790380] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.790383] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.790703] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18246.963760] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [18247.019699] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [18249.514054] ath10k_pci :03:00.0: No hardware memory [18249.514057] ath10k_pci :03:00.0: failed to copy target iram contents: -12
[Kernel-packages] [Bug 1939937] [NEW] ath10k: "add target IRAM recovery feature support" breaks QCA9984 Firmware load capability
Public bug reported: Hello, I use Ubuntu 20.04.2 LTS. The kernel was recently updated to 5.11 5.11.0-25-generic #27~20.04.1-Ubuntu SMP Tue Jul 13 17:41:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Since then the ath10k_core driver for my QCA9984 card is broken and only loads ~3 firmware versions from the 3.9.0.2 branch https://github.com/kvalo/ath10k-firmware/tree/master/QCA9984/hw1.0/3.9.0.2 The firmware versions 70 / 86 / 91 are functional (but these firmware versions are already 2 years old) Responsible for this is the defective patch "ath10k: add target IRAM recovery feature support" https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.11=9af7c32ceca85da27867dd863697d2aafc80a3f8 If I understand the patch correctly then the driver tries to load firmware with the feature "iram recovery" into the memory of the host (for recvovery purposes). If this fails, the firmware is discarded and the network controller remains unusable. Of course, this is not a desirable behavior for optional firmware features. dmesg: [3.074952] ath: loading out-of-tree module taints kernel. [3.090522] ath: module verification failed: signature and/or required key missing - tainting kernel [3.110879] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.178741] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [3.229944] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.229948] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.230274] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [3.291329] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [3.291333] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [3.291678] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00149 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 5f41acd7 [4.463156] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.520649] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [7.047910] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [7.103260] ath10k_pci :03:00.0: could not init core (-12) [7.103267] ath10k_pci :03:00.0: could not probe fw (-12) [7.108570] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [7.163247] ath10k_pci :04:00.0: could not init core (-12) [7.163268] ath10k_pci :04:00.0: could not probe fw (-12) In the ath10k mailing list I found a second patch which makes it possible to load the latest firmware on the card again. https://www.mail-archive.com/ath10k@lists.infradead.org/msg13655.html I have tested the patch and it works. dmesg: [18245.610112] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.674800] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [18245.731606] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.731620] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.733172] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18245.790380] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [18245.790383] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [18245.790703] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00152 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate,iram-recovery crc32 723f9771 [18246.963760] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [18247.019699] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [18249.514054] ath10k_pci :03:00.0: No hardware memory [18249.514057] ath10k_pci :03:00.0: failed to copy target iram contents: -12 [18249.570423] ath10k_pci :04:00.0: No hardware memory [18249.570426] ath10k_pci :04:00.0: failed to copy target iram contents: -12 [18249.620637] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp max-sta 512 raw 0 hwcrypto 1 [18249.678035] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp max-sta 512 raw 0 hwcrypto 1 Please include this patch in Ubuntu so that we can load current firmware versions on our QCA9984 cards again. additional reference: https://lists.infradead.org/pipermail/ath10k/2021-May/012626.html best regards ** Affects: linux (Ubuntu) Importance:
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
is a bit OT but..
QCA9984 (QNAP QWA-AC2600)
https://www.qnap.com/i/_attach_file/product/photo/800_500
/338_1524021711_QWA-AC2600_Front.png
QCA9984 (Netgear R7800)
https://www.netgear.de/images/Products/Networking/WirelessRouters/R7800/R7800_Hero_Transparent.png
The R7800 is running DD-WRT (v3.0-r44719) with kvalo Firmware
VHT80 4x4
1 Stream Download
[ 5] 63.00-63.36 sec 36.1 MBytes 843 Mbits/sec
2 Stream Download
[ 5] 0.00-60.03 sec 3.24 GBytes 464 Mbits/sec
[ 8] 0.00-60.03 sec 3.15 GBytes 451 Mbits/sec
[SUM] 0.00-60.03 sec 6.40 GBytes 915 Mbits/sec
1 Stream Upload
[ 5] 0.00-60.00 sec 6.52 GBytes 933 Mbits/sec
2 Stream Upload
[ 5] 0.00-60.00 sec 3.28 GBytes 469 Mbits/sec
[ 7] 0.00-60.00 sec 3.29 GBytes 470 Mbits/sec
[SUM] 0.00-60.00 sec 6.56 GBytes 939 Mbits/sec
all direct WLAN <--> LAN throughput
https://ibb.co/2sw3FDh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware 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:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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 -
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
I have already tested, I prefer to stay with the QCA firmware and
drivers that run for me stable and have for me fewer bugs
have 1Gbit throughput in both directions (stable)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware 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:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
so we have something to do and have to rebuild our kernel all the time
:-)
only a small joke, I wish of course also that it is somehow fixed for
all
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware 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:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
i have also already asked the ubuntu-devs
they only take upstream patches and leave the users in the rain
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware 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:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
there are other ways
- reg->current_rd = 0x64;
+ reg->current_rd = 0x6c;
0x64 is the most restrictive domain and there the complete midband is missing
0x6c means world wide regdomain
and if you really want to use the cards without any restrictions then
the openwrt patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware 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:
Confirmed
Status in linux-firmware package in Ubuntu:
Confirmed
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
as a short feedback i have solved the problem for me as follows i have patched the ath driver and set the eeprom to germany and additionally i have applied an openwrt patch then I have rebuild the module with the option "Do not enforce EEPROM regulatory restrictions" link to the patch (must be adjusted depending on kernel version) https://github.com/openwrt/openwrt/blob/master/package/kernel/mac80211/patches/ath/402-ath_regd_optional.patch Result [2.717027] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [2.775040] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [2.831174] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [2.831175] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [2.831504] ath10k_pci :03:00.0: firmware ver 10.4-3.9.0.2-00130 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate crc32 123ff35a [2.889062] ath10k_pci :04:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [2.889063] ath10k_pci :04:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [2.889410] ath10k_pci :04:00.0: firmware ver 10.4-3.9.0.2-00130 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps,peer-fixed-rate crc32 123ff35a [4.064069] ath10k_pci :03:00.0: board_file api 2 bmi_id 0:1 crc32 85498734 [4.120218] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32 85498734 [6.732655] ath10k_pci :03:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp max-sta 512 raw 0 hwcrypto 1 [6.796992] ath10k_pci :04:00.0: htt-ver 2.2 wmi-op 6 htt-op 4 cal otp max-sta 512 raw 0 hwcrypto 1 [6.805002] ath: EEPROM regdomain sanitized [6.805004] ath: EEPROM regdomain: 0x8114 [6.805004] ath: EEPROM indicates we should expect a country code [6.805004] ath: doing EEPROM country->regdmn map search [6.805005] ath: country maps to regdmn code: 0x37 [6.805005] ath: Country alpha2 being used: DE [6.805005] ath: Regpair used: 0x37 [6.805096] ath: EEPROM regdomain: 0x8114 [6.805096] ath: EEPROM indicates we should expect a country code [6.805096] ath: doing EEPROM country->regdmn map search [6.805097] ath: country maps to regdmn code: 0x37 [6.805097] ath: Country alpha2 being used: DE [6.805097] ath: Regpair used: 0x37 [6.805098] ath: regdomain 0x8114 dynamically updated by user [6.807137] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0 [6.869077] ath: EEPROM regdomain sanitized [6.869079] ath: EEPROM regdomain: 0x8114 [6.869079] ath: EEPROM indicates we should expect a country code [6.869080] ath: doing EEPROM country->regdmn map search [6.869080] ath: country maps to regdmn code: 0x37 [6.869080] ath: Country alpha2 being used: DE [6.869081] ath: Regpair used: 0x37 [9.640029] ath10k_pci :03:00.0: Unknown eventid: 36933 [9.644566] ath10k_pci :04:00.0 wlp4s0: renamed from wlan0 phy#1 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#0 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) Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) * 2472 MHz [13] (20.0 dBm) * 2484 MHz [14] (disabled) Frequencies: * 5180 MHz [36] (20.0 dBm) * 5200 MHz [40] (20.0 dBm) * 5220 MHz [44] (20.0 dBm) * 5240 MHz [48] (20.0 dBm) * 5260 MHz [52] (20.0 dBm) (radar detection) * 5280 MHz [56] (20.0 dBm) (radar detection) * 5300 MHz [60] (20.0 dBm) (radar
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
** Tags added: hwe-networking-wifi
--
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:
Confirmed
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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 -
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
** Attachment removed: "AlsaInfo.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895333/+attachment/5410701/+files/AlsaInfo.txt
** Attachment removed: "CRDA.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895333/+attachment/5410702/+files/CRDA.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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:
Confirmed
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410711/+files/ProcCpuinfoMinimal.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410705/+files/Lspci.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410710/+files/ProcCpuinfo.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] PulseList.txt
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410714/+files/PulseList.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410712/+files/ProcInterrupts.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
apport information
** Tags added: apport-collected
** Description changed:
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410713/+files/ProcModules.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410703/+files/CurrentDmesg.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Lsusb-v.txt
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410709/+files/Lsusb-v.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410707/+files/Lsusb.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410715/+files/RfKill.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] Lsusb-t.txt
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410708/+files/Lsusb-t.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410704/+files/IwConfig.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Lspci-vt.txt
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410706/+files/Lspci-vt.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410702/+files/CRDA.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410716/+files/UdevDb.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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
[Kernel-packages] [Bug 1895333] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1895333/+attachment/5410717/+files/WifiSyslog.txt
--
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
[Kernel-packages] [Bug 1895333] Re: cannot change the regulatory domain ath10k, QCA9984 (QNAP QWA-AC2600)
** No longer affects: ubuntu
** Package changed: linux-hwe-5.4 (Ubuntu) => linux (Ubuntu)
--
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:
New
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 :03:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[2.960023] ath10k_pci :04:00.0: pci irq msi oper_irq_mode 2 irq_mode
0 reset_mode 0
[3.015612] ath10k_pci :03:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.015613] ath10k_pci :03:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.015934] ath10k_pci :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 :04:00.0: qca9984/qca9994 hw1.0 target
0x0100 chip_id 0x sub 168c:cafe
[3.069594] ath10k_pci :04:00.0: kconfig debug 0 debugfs 1 tracing 1
dfs 0 testmode 0
[3.069933] ath10k_pci :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 :03:00.0: board_file api 2 bmi_id 0:1 crc32
85498734
[4.298899] ath10k_pci :04:00.0: board_file api 2 bmi_id 0:2 crc32
85498734
[6.980756] ath10k_pci :03:00.0: unsupported HTC service id: 1536
[7.087506] ath10k_pci :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 :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 :03:00.0 wlp3s0: renamed from wlan0
[7.235146] ath10k_pci :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,
