Wireless regulatory can not be loaded due to unknown signature

[loicpoulain]

Kernel log shows the following when booting:
cfg80211: loaded regulatory.db is malformed or signature is missing/invalid

This is because the regulatory.db point to custom debian one:
/lib/firmware/regulatory.db -> /etc/alternatives/regulatory.db

But kernel does not seem to include the right key for it.

Updating to upstream regulatory.db fixes the issue:
update-alternatives --set regulatory.db /lib/firmware/regulatory.db-upstream

[basak-qcom]

Thanks! @lool should we perhaps do this automatically in our images when an external kernel is being used in the build?

[lool]

@basak-qcom Yes, I think you're right; I also suspect we're not building kernels with the right configs to set the keys properly :-/

There might be a kernel config we can flip to return to the upstream db by default, that might be less invasive, not sure