On 2018-12-17 16:21 -0600, Bruce Dubbs via blfs-dev wrote: > [ 0.316853] platform regulatory.0: Direct firmware load for > regulatory.db failed with error -2 > > There are some things I found about something called regdb, but that > doesn't explain to me why the firmware isn't loading. > > Any ideas?
Hi Bruce, I have the same problem. dmesg outputs: > [ 1.021649] cfg80211: Loading compiled-in X.509 certificates for > regulatory d > atabase > [ 1.022809] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' > [ 1.022823] ALSA device list: > [ 1.022828] No soundcards found. > [ 1.025334] platform regulatory.0: Direct firmware load for regulatory.db > failed with error -2 > [ 1.025358] cfg80211: failed to load regulatory.db > [ 1.092576] fbcon: inteldrmfb (fb0) is primary device > [ 1.282343] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > [ 1.283254] ata1.00: NCQ Send/Recv Log not supported > [ 1.283259] ata1.00: ATA-9: SAMSUNG MZMTD128HAFV-000L1, DXT42L0Q, max > UDMA/133 > [ 1.283263] ata1.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 32), AA > [ 1.283859] ata1.00: NCQ Send/Recv Log not supported > [ 1.283947] ata1.00: configured for UDMA/133 It's very clear that cfg80211 tries to load the firmware, even *before* the hard drive comes up :(. I changed the kernel configuration to build cfg80211 as a module so it can not be loaded before the hard drive come up. So the problem is workarounded. -- Xi Ruoyao <xry...@mengyan1223.wang> School of Aerospace Science and Technology, Xidian University -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
