From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 49611@debbugs.gnu.org, Brice Waegeneire <brice@waegenei.re>
Subject: bug#49611: Despite wireless-regdb being installed in my operating-system, dmesg indicates it can't find `regulatory.db`
Date: Mon, 19 Jul 2021 13:21:14 -0500 [thread overview]
Message-ID: <CA+TvSRhLi-Cvffueu8Kh6Ny+MLMVwC0ZZr97sn08jKWt5dcbnw@mail.gmail.com> (raw)
In-Reply-To: <871r7v77pa.fsf@kitej>
Thank you both! I was not aware that this belonged in the firmware
field and not the packages field. This has solved the error message
during boot. Further, adding the kernel argument successfully sets my
region as US on boot.
tags 49611 notabug
close 49611
This is not part of the bug per-say, but a question around this space:
despite all of this, I still cannot broadcast on US approved channels.
I think this is because the EEPROM on the card is set as global. What
am I missing? Do you know how Linux intend for people to notify the
stack that this is an OK thing to do? I know projects like OpenWRT
carry patches to the driver, but I keep thinking surely this is not
the only way.
next prev parent reply other threads:[~2021-07-19 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 21:43 bug#49611: Despite wireless-regdb being installed in my operating-system, dmesg indicates it can't find `regulatory.db` Katherine Cox-Buday
[not found] ` <handler.49611.B.16265582421408.ack@debbugs.gnu.org>
2021-07-17 21:49 ` bug#49611: Acknowledgement (Despite wireless-regdb being installed in my operating-system, dmesg indicates it can't find `regulatory.db`) Katherine Cox-Buday
2021-07-18 17:47 ` bug#49611: Despite wireless-regdb being installed in my operating-system, dmesg indicates it can't find `regulatory.db` Brice Waegeneire
2021-07-18 19:17 ` Guillaume Le Vaillant
2021-07-19 18:21 ` Katherine Cox-Buday [this message]
2021-07-19 21:17 ` Guillaume Le Vaillant
2021-08-09 23:40 ` Tom Fitzhenry
2021-08-09 23:45 ` Tom Fitzhenry
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+TvSRhLi-Cvffueu8Kh6Ny+MLMVwC0ZZr97sn08jKWt5dcbnw@mail.gmail.com \
--to=cox.katherine.e@gmail.com \
--cc=49611@debbugs.gnu.org \
--cc=brice@waegenei.re \
--cc=glv@posteo.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).