[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#49611: Despite wireless-regdb being installed in my operating-system
bug#49611: Despite wireless-regdb being installed in my operating-system, dmesg indicates it can't find `regulatory.db`
Sun, 18 Jul 2021 19:47:54 +0200
Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
TL;DR: “iw reg set US” correctly set the regulatory region from userland
but Guix can't set it just from the kernel.
Katherine Cox-Buday <email@example.com> writes:
> [ 8.280462] cfg80211: Loading compiled-in X.509 certificates for
> regulatory database
> [ 8.282686] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
> [ 8.284394] platform regulatory.0: Direct firmware load for
> regulatory.db failed with error -2
> [ 8.284415] cfg80211: failed to load regulatory.db
There is three way to make the module cfg80211 load a regulatory
1. Baking the DB into the kernel at build time by replacing the kernel's
limited DB with the one from 'wireless-regdb' via the option
2. Loading the DB at boot time as a signed firmware file
(lib/firmware/regulatory.db from 'wirerless-regdb') via the module
3. Doing it in userland with the helper 'crda' trough the utility
'iwd' or its predecesor 'wpa_supplicant'.²
>From what I understand and what I tested, only the third method works in
Guix System ATM. It could be usefull to also support the first or
second method to not depend on the userland setting the wireless
The error you are experiencing come from the second method failing to
load the signed firmware file. The issue is that Guix's 'wireless-regdb'
is build from source and not just copied as other distribution do, where
the provided binary also has a signature which the kernel accept through
a built in public key. Our build version isn't signed at all, the
commentaries in the definition for the package say Guix don't want to
maintain its own key for signing this package, which is understable and
state that Guix architecture already provide a similar level of
authenticity (I'm not so sure of that part).
So this error message should be harmless expected in some less common
context, such as having the rootfs on an NFS and using a wireless
connection to connect to the NFS server. We could fix that without
maintaining keys by baking the DB into the kernel (first method).
> $ find -L /run/current-system -name regulatory.db
We don't need the regulatory.db from 'wirelress-regdb' to be in the
system profile, instead it should be added to the operating-system's
firmware field. And the kernel will find it the directory contained in