Seems there are problems to query and change the regulatory domain using 'iw
reg get' and 'iw reg set'. A proposed fix to wireless-regdb is available for
testing for Xenial and later, and work is in progress for Precise and Trusty.
See
Ubuntu 18.04 still does not set the regulatory domain during install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280636
Title:
14e4:4365 [Dell Inspiron 15 3521] Regulatory domain is not set by
@zebul666
The wl kernel module seems not to honor the crda setting. It doesn't connect to
high channels at all.
See https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1574196
Nevertheless, Ubuntu still doesn't set the regulatory domain automatically.
I'm using 17.10.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: crda (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280636
Title:
** Also affects: crda (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280636
Title:
14e4:4365 [Dell Inspiron 15 3521] Regulatory domain is not
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280636
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
