Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I downloaded the firmware-brcm80211_20161130-3+rpt3_all.deb package and found that I was missing a blob file for the brcmfmac43455. I added what you said for the cmdline.txt file. Attached is the latest dmesg log.
[1198262.720551] sysrq: Loglevel set to 8
[1198265.926373] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[1198265.934865] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[1198265.942333] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5)
[1198269.319271] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[1198269.344205] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[1198269.351402] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[1198269.360391] platform regulatory.0: Falling back to syfs fallback for: regulatory.db
[1198269.413175] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1
[1198269.617311] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43362-sdio for chip BCM43362/1
It doesn't have to be mounted there, although that's where it should be mounted when you do updates.
The critical point is that the first partition on the SD card is where the firmware, device tree, and kernel (and initrd, where applicable) must be in order to boot from the SD card. And the format must be FAT32.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.