Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update wireless-regdb #2999

Closed
ab932 opened this issue Sep 22, 2018 · 8 comments
Closed

Update wireless-regdb #2999

ab932 opened this issue Sep 22, 2018 · 8 comments
Assignees
Labels
bug Something isn't working question Further information is requested request Package request

Comments

@ab932
Copy link

ab932 commented Sep 22, 2018

_dbversion=2016.06.10

This is causes recent kernels to fail to find /lib/firmware/regulations.db when loading cfg80211

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

See here: https://patchwork.kernel.org/patch/10128825/

@maxice8
Copy link
Contributor

maxice8 commented Sep 22, 2018

@thypon seems like Arch uses snapshots of crda from https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/crda.git/

@ab932
Copy link
Author

ab932 commented Sep 22, 2018

I think it might make sense to connect crda and wireless-regdb as two packages.
I'm not sure what you are referring to by mentioning Arch but this is the wireless-regdb package in Arch:
https://www.archlinux.org/packages/core/any/wireless-regdb/

@maxice8
Copy link
Contributor

maxice8 commented Sep 22, 2018

I think it might make sense to connect crda and wireless-regdb as two packages.

wireless-regdb is fetched during building of the crda package, see distfiles=

@ab932
Copy link
Author

ab932 commented Sep 22, 2018

OK. I am aware of that. I guess a git check in with the new _dbversion is necessary.

@maxice8
Copy link
Contributor

maxice8 commented Sep 22, 2018 via email

@thypon
Copy link
Member

thypon commented Sep 22, 2018

@ab932 I would like to wait for a stable release of the new crda before updating both. The error shown are non fatal and the wifi will continue to work even without the newer crda.

@thypon thypon self-assigned this Sep 22, 2018
@thypon thypon added bug Something isn't working question Further information is requested request Package request labels Sep 22, 2018
@ghost
Copy link

ghost commented Sep 23, 2018

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892229

It looks like Debian takes care of this by applying some pacthes for 4.18.8 and 4.19-rc4.

@maxice8
Copy link
Contributor

maxice8 commented Jan 26, 2019

The maintainer of the package is aware and has answered

@maxice8 maxice8 closed this as completed Jan 26, 2019
@edersohe edersohe mentioned this issue Feb 8, 2021
3 tasks
edersohe pushed a commit to edersohe/void-packages that referenced this issue Feb 9, 2021
* crda-4.14
* wireless-regdb-2020.12.20

fix error messages like

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

registered also in the issue void-linux#2999
edersohe pushed a commit to edersohe/void-packages that referenced this issue Feb 10, 2021
* crda-4.14
* wireless-regdb-2020.12.20

fix error messages like

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

registered also in the issue void-linux#2999 and

```
[    6.917367] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.920611] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
```
edersohe pushed a commit to edersohe/void-packages that referenced this issue Feb 10, 2021
* crda-4.14
* wireless-regdb-2020.12.20

fix error messages like

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

registered also in the issue void-linux#2999 and

```
[    6.917367] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.920611] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
```
ericonr pushed a commit that referenced this issue Feb 25, 2021
* crda-4.14
* wireless-regdb-2020.12.20

fix error messages like

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

registered also in the issue #2999 and

```
[    6.917367] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.920611] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
```
atweiden added a commit to atweiden/voidpkgs that referenced this issue Feb 26, 2021
* crda-4.14
* wireless-regdb-2020.12.20

fix error messages like

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

registered also in the issue void-linux/void-packages#2999 and

```
[    6.917367] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.920611] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
```

void-linux/void-packages@bffda1d
hazayan pushed a commit to hazayan/void-packages that referenced this issue Feb 28, 2021
* crda-4.14
* wireless-regdb-2020.12.20

fix error messages like

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

registered also in the issue void-linux#2999 and

```
[    6.917367] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.920611] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working question Further information is requested request Package request
Projects
None yet
Development

No branches or pull requests

3 participants