0004697: platform regulatory.0: firmware: failed to load regulatory.db (-2) after update to kernel 4.15

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0004697

Kali Linux

[All Projects] General Bug

public

2018-04-12 20:40

2018-04-13 21:05

Reporter

neminem

Assigned To

rhertzog

Priority

normal

Severity

minor

Reproducibility

always

Status

assigned

Resolution

open

Product Version

2018.1

Target Version

Fixed in Version

Summary

0004697: platform regulatory.0: firmware: failed to load regulatory.db (-2) after update to kernel 4.15

Description

Looks like after i upgraded to the kernel 4.15 i started having this error at boot.
Dig some digging and looks like it's been reported for several other distros as well. My own findings show that it could have something to do with my internal wi-fi card which is a broadcom.
Before updating the kernel i was able to use the broadcom-sta-dkms driver instead of the b43 one. After upgrading the kernel to 4.15 the broadcom-sta-dkms driver does not work anymore and i was forced to go back to b43.

Steps To Reproduce

possibly any internal broadcom wireless card and a Kali linux version updated to the 4.15 kernel

Attached Files

Relationships

has duplicate

0004711

closed

rhertzog

problem in the startup

Relationships

Notes
~0009035 rhertzog (administrator) 2018-04-13 13:35	This message is probably unrelated to your issue. The regulatory.db issue is described here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892229 I have prepared an updated wireless-regdb package if you want to test it out: https://people.debian.org/~hertzog/packages/wireless-regdb_2017.12.23-1_amd64.deb But if you want to understand why broadcom-sta-dkms no longer works with your card, then you should probably try to provide more information like concrete error messages, logs, etc.

~0009036 rhertzog (administrator) 2018-04-13 21:05	The package that I prepared is likely not working (kernel will likely complain that it can't verify the signature) but an updated (and fixed) one should land soonish in Debian unstable.

Notes

Date Modified	Username	Field	Change
Issue History
2018-04-12 20:40	neminem	New Issue
2018-04-13 13:35	rhertzog	Note Added: 0009035
2018-04-13 13:35	rhertzog	Assigned To	=> rhertzog
2018-04-13 13:35	rhertzog	Status	new => assigned
2018-04-13 21:05	rhertzog	Note Added: 0009036
2018-04-22 18:22	rhertzog	Relationship added	has duplicate 0004711

Issue History