View Issue Details

IDProjectCategoryView StatusLast Update
0004697Kali Linux[All Projects] General Bugpublic2018-10-30 11:14
ReporterneminemAssigned Torhertzog 
Status closedResolutionsuspended 
Product Version2018.1 
Target VersionFixed in Version 
Summary0004697: platform regulatory.0: firmware: failed to load regulatory.db (-2) after update to kernel 4.15
DescriptionLooks 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 Reproducepossibly any internal broadcom wireless card and a Kali linux version updated to the 4.15 kernel


has duplicate 0004711 closedrhertzog problem in the startup 



2018-04-13 13:35

administrator   ~0009035

This message is probably unrelated to your issue. The regulatory.db issue is described here:

I have prepared an updated wireless-regdb package if you want to test it out:

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.


2018-04-13 21:05

administrator   ~0009036

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.


2018-10-30 11:14

administrator   ~0009855

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x/2017.x/2018.1), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux -

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read:

Issue History

Date Modified Username Field Change
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
2018-10-30 11:14 g0tmi1k Status assigned => closed
2018-10-30 11:14 g0tmi1k Resolution open => suspended
2018-10-30 11:14 g0tmi1k Note Added: 0009855