From: Sebastian Bachmann <hello@reox.at>
To: ath10k@lists.infradead.org
Subject: Compex WLE200NX: regdomain sanitized regression
Date: Sat, 27 Nov 2021 09:17:00 +0100 [thread overview]
Message-ID: <1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at> (raw)
Hello,
I recently upgraded my Debian based AP from buster to bullseye, just to
find out that hostapd does not work any more, because all 5GHz channels
are marked as No-IR. This regression was already discussed on this ML
here: https://www.mail-archive.com/ath10k@lists.infradead.org/msg12018.html
and there is also an entry in Debian's bug tracker for the same issue:
https://bugs.debian.org/959821
I have a slightly different card (branded Compex WLE200NX):
04:00.0 Network controller: Qualcomm Atheros AR928X Wireless Network
Adapter (PCI-Express) (rev 01)
Subsystem: Qualcomm Atheros AR928X Wireless Network Adapter
(PCI-Express)
Kernel driver in use: ath9k
Kernel modules: ath9k
But as you can see, also the EEPROM gets sanitized:
[ 15.461755] ath9k 0000:04:00.0: enabling device (0000 -> 0002)
[ 15.911600] ath: EEPROM regdomain sanitized
[ 15.911612] ath: EEPROM regdomain: 0x64
[ 15.911615] ath: EEPROM indicates we should expect a direct regpair map
[ 15.911625] ath: Country alpha2 being used: 00
[ 15.911628] ath: Regpair used: 0x64
I read in the other thread, that this is a regression, but the actual
commit causing it was never reverted.
I tried to search for newer messages explaining the issue, however as
far as I can tell, the thread ends in June 2020 with no solution available.
Therefore, I kindly want to ask if there is any workaround available to
re-enable 5GHz channels in AP mode for my card? (expect sticking to a
pre-5.6 kernel or manually patching and recompiling ath)
Best,
Sebastian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next reply other threads:[~2021-11-27 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 8:17 Sebastian Bachmann [this message]
2021-11-27 11:28 ` Compex WLE200NX: regdomain sanitized regression Thorsten Leemhuis
2021-11-27 12:21 ` Nuno Oliveira
2021-11-27 13:25 ` Sebastian Bachmann
2021-12-01 9:06 ` Thorsten Leemhuis
2021-12-06 7:18 ` Sebastian Bachmann
2021-12-20 10:37 ` Kalle Valo
2021-12-20 18:31 ` Nuno Oliveira
2022-02-18 11:47 ` Thorsten Leemhuis
2022-02-24 16:22 ` Kalle Valo
2022-02-24 16:38 ` Thorsten Leemhuis
2022-02-24 16:47 ` Kalle Valo
2021-11-27 16:35 ` Bryce Allen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c160dfb-6ccc-b4d6-76f6-4364e0adb6dd@reox.at \
--to=hello@reox.at \
--cc=ath10k@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).