Arch Linux

Kamikadze

Member

From: London

Registered: 2018-04-22

Posts: 16

platform regulatory.0: Direct firmware load for regulatory.db failed

Log in dmesg:

[   26.804790] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   26.895516] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   26.942588] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   26.976779] cfg80211: failed to load regulatory.db

I install package wireless-regdb and rebooted the computer, but the problem still remains exactly! Package wireless-regdb does not require any settings, so I do not know what to do!!!

dockland

Member

From: Sweden

Registered: 2015-06-06

Posts: 861

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

I see wireless-regdb is flagged out of date

---

I possess a device, in my pocket, that is capable of accessing the entirety of information known to man.
I use it to look at funny pictures of cats and to argue with strangers.

loqs

Member

Registered: 2014-03-06

Posts: 17,325

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

https://bugs.archlinux.org/task/57563
Edit:
It should be harmless as long as you have crda installed which will perform the database load later in userspace.

Last edited by loqs (2018-04-22 17:18:32)

Kamikadze

Member

From: London

Registered: 2018-04-22

Posts: 16

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

I see wireless-regdb is flagged out of date

How is this possible? Here is the latest version: https://www.archlinux.org/packages/core … ess-regdb/

loqs

Member

Registered: 2014-03-06

Posts: 17,325

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

I see wireless-regdb is flagged out of date

How is this possible? Here is the latest version: https://www.archlinux.org/packages/core … ess-regdb/

Someone clicked the flag out of data link (the link will not appear on that page as the package has been flagged out of date already)
https://www.kernel.org/pub/software/net … ess-regdb/ see the 2017.12.23 release that arch has not updated to?

Kamikadze

Member

From: London

Registered: 2018-04-22

Posts: 16

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

https://bugs.archlinux.org/task/57563
Edit:
It should be harmless as long as you have crda installed which will perform the database load later in userspace.

When you compile a package using the command, makepkg produces the following error:

==> Build the wireless-regdb package 2017.12.23-1 (Mon Apr 23 06:45:32 MSK 2018)
==> Checking the dependencies to start ...
==> Checking Dependencies for Build ...
==> Getting the source files ...
  -> Download wireless-regdb-2017.12.23.tar.xz ...
  % Total% Received% Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 178 100 178 0 0 427 0 -: -: - -: -: - -: -: - 426
100 21444 100 21444 0 0 3375 0 0:00:06 0:00:06 - - - - - - 6268
  -> Download wireless-regdb-2017.12.23.tar.sign ...
  % Total% Received% Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 178 100 178 0 0 626 0 -: -: - -: -: - -: -: - 626
100 801 100 801 0 0 130 0 0:00:06 0:00:06 -: -: - 184
  -> Found crda.conf.d
==> Checking source files using sha256sums ...
    wireless-regdb-2017.12.23.tar.xz ... Finish
    wireless-regdb-2017.12.23.tar.sign ... Skipped
    crda.conf.d ... Finish
==> Verifying the signatures of the source files with 'gpg' ...
FAILURE (unknown public key AB4800A62DB9F73A)
==> ERROR: One or more PGP signatures can not be verified!

I do not know what to do, all the keys on my computer are updated!

Kamikadze

Member

From: London

Registered: 2018-04-22

Posts: 16

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

I see wireless-regdb is flagged out of date

How is this possible? Here is the latest version: https://www.archlinux.org/packages/core … ess-regdb/

Someone clicked the flag out of data link (the link will not appear on that page as the package has been flagged out of date already)
https://www.kernel.org/pub/software/net … ess-regdb/ see the 2017.12.23 release that arch has not updated to?

I have recently noticed this.

loqs

Member

Registered: 2014-03-06

Posts: 17,325

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

I do not know what to do, all the keys on my computer are updated!

Makepkg#Signature_checking
Edit:
You did change the PKGBUILD as noted in the bug report I linked beyond just updating the package version?

Last edited by loqs (2018-04-22 23:58:13)

Kamikadze

Member

From: London

Registered: 2018-04-22

Posts: 16

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

I do not know what to do, all the keys on my computer are updated!

Makepkg#Signature_checking
Edit:
You did change the PKGBUILD as noted in the bug report I linked beyond just updating the package version?

Naturally, I did this with the patch command.

I generated a new key for this help https://wiki.archlinux.org/index.php/Gn … e_key_pair.
Command gpg --list-secret-keys:

/home/user/.gnupg/pubring.kbx
-----------------------------
sec   rsa2048 2018-04-23 [SC]
      6D5690722AEAE9DD76ABA9095729C603B25C12CC
uid         [  absolutely ] MikeN <no-email@email.net>

But when you create a package, everything is exactly the error. I understand the documentation is very complicated and I just can not figure it out.
It is necessary as something to podpist that all worked!

loqs

Member

Registered: 2014-03-06

Posts: 17,325

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

You do not need to have a key.  The public key for AB4800A62DB9F73A needs to be in the keyring of the user trying to build the package.
GnuPG#Use_a_keyserver  import the key with the ID from error produced by makepkg then try the build again.

Kamikadze

Member

From: London

Registered: 2018-04-22

Posts: 16

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

You do not need to have a key.  The public key for AB4800A62DB9F73A needs to be in the keyring of the user trying to build the package.
GnuPG#Use_a_keyserver  import the key with the ID from error produced by makepkg then try the build again.

I figured it all out and it worked. Thank you, the topic is closed!

loqs

Member

Registered: 2014-03-06

Posts: 17,325

Re: platform regulatory.0: Direct firmware load for regulatory.db failed

I figured it all out and it worked. Thank you, the topic is closed!

Code_of_conduct#How_to_post

Finally, when a solution is found, mark your thread as solved by editing the first post and prepending the tag [SOLVED] to the title in the "Subject" field.
Note that you should avoid using [CLOSED], which is instead used by the system to mark a thread which is no longer accessible for new posts.

If you really want the thread to be deleted please report this thread using the report link to contact a moderator so it can be closed and deleed.