Not sure if this change was intentional, but since Jetpack 6.0, the 5.15 kernel has those config flags set, which were disabled before, in Jetpack 5:
$ zgrep CONFIG_CFG80211_ /proc/config.gz
# CONFIG_CFG80211_DEVELOPER_WARNINGS is not set
CONFIG_CFG80211_REQUIRE_SIGNED_REGDB=y
CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y
CONFIG_CFG80211_DEFAULT_PS=y
# CONFIG_CFG80211_DEBUGFS is not set
CONFIG_CFG80211_CRDA_SUPPORT=y
# CONFIG_CFG80211_WEXT is not set
So during development in 5.x, we could load our own regulatory.db for testing.
Not only this, but the key used for signing the kernel db is from nvidia, which prevents the official db from being loaded externally as well:
$ sudo apt install wireless-regdb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
wireless-regdb
0 upgraded, 1 newly installed, 0 to remove and 317 not upgraded.
Need to get 10.0 kB of archives.
After this operation, 36.9 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 wireless-regdb all 2024.07.04-0ubuntu1~22.04.1 [10.0 kB]
Fetched 10.0 kB in 0s (69.4 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package wireless-regdb.
(Reading database ... 221634 files and directories currently installed.)
Preparing to unpack .../wireless-regdb_2024.07.04-0ubuntu1~22.04.1_all.deb ...
Unpacking wireless-regdb (2024.07.04-0ubuntu1~22.04.1) ...
Setting up wireless-regdb (2024.07.04-0ubuntu1~22.04.1) ...
Processing triggers for man-db (2.10.2-1) ...
$ sudo reboot
$ sudo dmesg |grep regu
[ 8.366730] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 8.375977] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
$
Is this intended? Can you please revert it if there is no strong reason for this to be hardcoded in the kernel?
PS: maintainer private key was changed in the kernel since Dec. 1, 2023 from sforshee to wens, see here: wireless-regdb: Update keys and maintainer information - Patchwork
Downgrading the regdb works:
$ sudo apt install wireless-regdb=2022.06.06-0ubuntu1~22.04.1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be DOWNGRADED:
wireless-regdb
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 317 not upgraded.
Need to get 10.3 kB of archives.
After this operation, 2,048 B disk space will be freed.
Do you want to continue? [Y/n] y
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 wireless-regdb all 2022.06.06-0ubuntu1~22.04.1 [10.3 kB]
Fetched 10.3 kB in 0s (53.3 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
dpkg: warning: downgrading wireless-regdb from 2024.07.04-0ubuntu1~22.04.1 to 2022.06.06-0ubuntu1~22.04.1
(Reading database ... 221643 files and directories currently installed.)
Preparing to unpack .../wireless-regdb_2022.06.06-0ubuntu1~22.04.1_all.deb ...
Unpacking wireless-regdb (2022.06.06-0ubuntu1~22.04.1) over (2024.07.04-0ubuntu1~22.04.1) ...
Setting up wireless-regdb (2022.06.06-0ubuntu1~22.04.1) ...
Processing triggers for man-db (2.10.2-1) ...
$ sudo reboot
$ sudo dmesg |grep cfg80211
[ 831.901394] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 831.905216] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
The reason why this is important is that WiFi 6E power limits changed in most regions, so we need the newer version for us to have a stable connection in 6 GHz.
Cheers,
R