cfg80211: failed to load regulatory.db

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
mgkiller
Level 3
Level 3
10 replies posted 10 questions asked 10 sign-ins

Although i have success to make my cypress wifi work.,but i notice that there is a error when wifi bringup:

[ 135.200000] cfg80211: failed to load regulatory.db

And i have read though  a Regulatory wiki(https://wireless.wiki.kernel.org/en/developers/Regulatory), but I don’t have enough expertise to really understand it.

Should any one tell me how to do deal with wifi regulatory?  if  our wifi device will deploy around the world.

 

0 Likes
1 Solution
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Yes, the clm_blob file has the regulatory information and it'll do the same things as regulation.db and it's not required as our driver uses clm_blob.

Thanks

Aditi

View solution in original post

9 Replies
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Can you share the full logs with us? Also, provide the .config file of yours to check the build strings.

Thanks

Aditi

0 Likes

Sure, @Aditi_B 

Here is the log:

[ 71.350000] ios->clock=400000
[ 71.740000] ios->clock=400000
[ 71.740000] ios->clock=400000
[ 71.920000] ios->clock=400000
[ 71.940000] mmc0: queuing unknown CIS tuple 0x80 (2 bytes)
[ 71.940000] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[ 71.970000] mmc0: queuing unknown CIS tuple 0x80 (3 bytes)
[ 71.970000] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
[ 72.000000] mmc0: queuing unknown CIS tuple 0x81 (1 bytes)
[ 72.170000] ios->clock=400000
[ 72.190000] ios->clock=50000000
[ 72.190000] ios->clock=50000000
[ 72.190000] mmc0: new high speed SDIO card at address 0001
[ 75.060000] Loading modules backported from Linux version v5.4.18-2021_0527-0-gc6ec8acef0b8
[ 75.060000] Backport generated by backports.git v5.4.27-1-0-gf6e8852f
[ 75.990000] brcmfmac_module_init No platform data available.
[ 76.010000] brcmf_chip_recognition found AXI chip: BCM43430/1
[ 76.030000] brcmf_chip_cores_check [1 ] core 0x800:49 base 0x18000000 wrap 0x18100000
[ 76.090000] brcmf_chip_cores_check [2 ] core 0x812:39 base 0x18001000 wrap 0x18101000
[ 76.090000] brcmf_chip_cores_check [3 ] core 0x829:21 base 0x18002000 wrap 0x18102000
[ 76.140000] brcmf_chip_cores_check [4 ] core 0x82a:9 base 0x18003000 wrap 0x18103000
[ 76.140000] brcmf_chip_cores_check [5 ] core 0x80e:22 base 0x18004000 wrap 0x18104000
[ 76.190000] brcmf_chip_cores_check [6 ] core 0x135:0 base 0x00000000 wrap 0x18105000
[ 76.220000] brcmf_chip_cores_check [7 ] core 0x240:0 base 0x00000000 wrap 0x18106000
[ 76.240000] brcmf_chip_get_raminfo RAM: base=0x0 size=524288 (0x80000) sr=65536 (0x10000)
[ 76.240000] brcmf_chip_setup ccrev=49, pmurev=24, pmucaps=0x39d25f18
[ 76.270000] brcmf_get_module_param Enter, bus=0, chip=43430, rev=1
[ 76.270000] brcmf_sdio_drivestrengthinit No SDIO driver strength init needed for chip BCM43430/1 rev 1 pmurev 24
[ 76.310000] brcmf_sdio_probe completed!!
[ 76.310000] brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac43430-sdio for chip BCM43430/1
[ 76.440000] brcmf_sdio_verifymemory Compare RAM dl & ul at 0x00000000; size=419798
[ 76.650000] brcmf_sdio_verifymemory Compare RAM dl & ul at 0x0007fda0; size=608
[ 76.810000] brcmf_sdio_firmware_callback enable F2: err=0
[ 76.810000] brcmf_sdio_sr_init SR enabled
[ 76.810000] brcmf_bus_change_state ignoring transition, bus not attached yet
[ 76.870000] brcmf_sdio_readshared sdpcm_shared address 0x000469C0
[ 76.870000] brcmf_sdio_readshared sdpcm_shared address 0x000469C0
[ 76.890000] brcmf_add_if allocate netdev interface
[ 76.920000] brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac43430-sdio for chip BCM43430/1
[ 76.950000] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766
[ 76.980000] brcmf_c_preinit_dcmds CLM version = API: 12.2 Data: Cypress.CYW4343W Compiler: 1.29.4 ClmImport: 1.36.3 Customization: v1 200525 Creation: 2021-03-30 01:02:09
[ 77.040000] brcmf_pktfilter_add_remove add packet filter number 0
[ 77.060000] brcmf_feat_firmware_capabilities [ ap sta wme 802.11d 802.11h rm cac ampdu ampdu_tx ampdu_rx amsdurx radio_pwrsave p2p mchan p2po anqpo dfrts txpwrcache stbc-tx stbc-rx-1ss wnm bsstrans mfp sae ]
[ 77.090000] brcmf_feat_firmware_capabilities enabling feature: MCHAN
[ 77.090000] brcmf_feat_firmware_capabilities enabling feature: P2P
[ 77.120000] brcmf_feat_firmware_capabilities enabling feature: DOT11H
[ 77.140000] brcmf_feat_firmware_capabilities enabling feature: SAE
[ 77.150000] brcmf_feat_iovar_int_get enabling feature: MFP
[ 77.190000] brcmf_feat_iovar_int_get enabling feature: FWSUP
[ 77.210000] brcmf_fws_attach FWS queueing will be avoided
[ 77.220000] brcmf_cfg80211_attach Registering custom regulatory
[ 77.250000] brcmf_setup_wiphybands nmode=1, vhtmode=0, bw_cap=(1, 0)
[ 77.280000] brcmf_setup_wiphybands nchain=1
[ 77.340000] check_vif_up device is not ready : status (0)
[ 77.340000] brcmf_net_attach wlan0: Broadcom Dongle Host Driver
[ 83.160000] check_vif_up device is not ready : status (0)
[ 83.160000] check_vif_up device is not ready : status (0)
[ 83.190000] check_vif_up device is not ready : status (0)
[ 83.190000] check_vif_up device is not ready : status (0)
[ 83.220000] check_vif_up device is not ready : status (0)
[ 83.260000] brcmf_config_dongle power save set to enabled
[ 83.300000] brcmf_dongle_roam Internal Roaming = On
[ 83.310000] brcmf_cfg80211_change_iface IF Type = Infra
[ 83.340000] brcmf_set_mpc MPC : 1
[ 83.350000] brcmf_cfg80211_set_power_mgmt power save enabled
[ 84.060000] brcmf_cfg80211_connect ie (c35c7248), ie_len (22)
[ 118.170000] brcmf_cfg80211_connect ie (c1fde448), ie_len (22)
[ 135.520000] cfg80211: failed to load regulatory.db
~ #
~ # ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 70:66:55:3F:EB:EB
inet addr:172.16.24.120 Bcast:172.16.24.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2229 (2.1 KiB) TX bytes:3416 (3.3 KiB)

~ # iwconfig wlan0
wlan0 IEEE 802.11 ESSID:"Robustel-Visitor"
Mode:Managed Frequency:2.462 GHz Access Point: 20:65:8E:BA:56:61
Bit Rate=48 Mb/s Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
Link Quality=49/70 Signal level=-61 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:1 Invalid misc:0 Missed beacon:0

~ # iw reg get
country 00: DFS-UNSET
(2402 - 2472 @ 40), (6, 20), (N/A)
(2457 - 2482 @ 20), (6, 20), (N/A), PASSIVE-SCAN
(2474 - 2494 @ 20), (6, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (6, 20), (N/A), PASSIVE-SCAN
(5250 - 5330 @ 80), (6, 20), (0 ms), DFS, PASSIVE-SCAN
(5490 - 5730 @ 160), (6, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (6, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
~ #

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Thank You for providing the logs. Please provide the .config file as well.

Thanks

Adit

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Please provide the driver version/chipset/host that you've in your setup.

Thanks

Aditi

0 Likes

Driver version: v5.4.18-2021_0527 (backport to linux v3.10.108)

Chipset: Cy43438

Host: NUC970(ARM9) + Linux(v3.10.108)

0 Likes
lock attach
Attachments are accessible only for community members.

Here is my kernel .config @Aditi_B 

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Thanks for sharing the .config file. Have you checked whether you have the regulatory.db file in your LINUX kernel source folder? Can you try to locate it if you haven't?

Also, our driver uses clm_blob file instead of this reg.db to acquire regulatory information. So, even if it(reg.db) fails to load you'll be able to bringup wireless interfaces. Are you facing any specific problems due to this?

Thanks

Aditi

0 Likes

There is not a regulatory.db in my Linux kernel source(v3.10.108).

Except that the kernel will print out "cfg80211: failed to load regulation.db", no other exceptions have been found so far.

AditiB_81, do you mean that clm_blob file do the same things as regulation.db and regulation.db is no looger needed?

0 Likes
Aditi_B
Moderator
Moderator
Moderator
500 replies posted 5 questions asked 250 replies posted

Hi,

Yes, the clm_blob file has the regulatory information and it'll do the same things as regulation.db and it's not required as our driver uses clm_blob.

Thanks

Aditi