Bug 1594902 - platform regulatory.0: Direct firmware load for regulatory.db failed with error -2; cfg80211: failed to load regulatory.db
Summary: platform regulatory.0: Direct firmware load for regulatory.db failed with err...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: crda
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-25 16:16 UTC by Flo H.
Modified: 2018-07-17 18:37 UTC (History)
1 user (show)

Fixed In Version: crda-3.18_2018.05.31-2.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-17 15:17:03 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Flo H. 2018-06-25 16:16:04 UTC 
Description of problem:
I am seeing those two messages in dmesg

[] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[] cfg80211: failed to load regulatory.db

What does it mean? Should I actually report it against kernel?

Version-Release number of selected component (if applicable):
kernel: kernel-4.17.2-200.fc28.x86_64
crda: crda-3.18_2016.02.08-7.fc28.x86_64


How reproducible:
100%

Steps to Reproduce:
1.boot Fedora 28 on my Thinkpad T440s
2.run dmesg | grep failed
3.

Actual results:
[   31.448102] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   31.448105] cfg80211: failed to load regulatory.db


Expected results:
Not seeing such message

Additional info:
Comment 1 Fedora Update System 2018-06-25 17:07:18 UTC 
crda-3.18_2018.05.31-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-831e14317d
Comment 2 Flo H. 2018-06-25 17:17:06 UTC 
I should probably give this update a try...
https://koji.fedoraproject.org/koji/buildinfo?buildID=1097239
Comment 3 Flo H. 2018-06-25 18:24:15 UTC 
above mentioned updates fixes the bug reported here.
Comment 4 Fedora Update System 2018-06-26 18:24:08 UTC 
crda-3.18_2018.05.31-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-831e14317d
Comment 5 Fedora Update System 2018-07-05 18:07:56 UTC 
crda-3.18_2018.05.31-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0c97f09931
Comment 6 Fedora Update System 2018-07-06 17:53:09 UTC 
crda-3.18_2018.05.31-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0c97f09931
Comment 7 Fedora Update System 2018-07-17 15:17:03 UTC 
crda-3.18_2018.05.31-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
Comment 8 Flo H. 2018-07-17 18:37:58 UTC 
Fixed In Version: crda-3.18_2018.05.31-2.fc28
Note You need to log in before you can comment on or make changes to this bug.