LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 05-14-2021, 04:01 PM   #1
kermitdafrog8
Member
 
Registered: Dec 2018
Location: Orlando, FL
Distribution: Slackware ARM and X86_64
Posts: 152

Rep: Reputation: Disabled
sarpi3-boot-firmware May 13


After upgrading to 13May21 release wifi no longer works.
 
Old 05-14-2021, 04:06 PM   #2
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by kermitdafrog8 View Post
After upgrading to 13May21 release wifi no longer works.
OK thanks for letting me know. I'll take a look into it.

[EDIT] Yep, this is a RPi3 onboard wireless issue because the interface is AWOL. On the RPi4 it's working OK. Leave it with me and I'll get back to you just as soon as I can. Apologies for any inconvenience caused.

Last edited by Exaga; 05-14-2021 at 04:21 PM. Reason: edit
 
Old 05-14-2021, 04:26 PM   #3
kermitdafrog8
Member
 
Registered: Dec 2018
Location: Orlando, FL
Distribution: Slackware ARM and X86_64
Posts: 152

Original Poster
Rep: Reputation: Disabled
sarpi3-boot-firmware May 13

It's all part of the fun.
 
1 members found this post helpful.
Old 05-15-2021, 04:45 AM   #4
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by kermitdafrog8 View Post
It's all part of the fun.
I really dislike the way the RPi onboard wireless keeps failing. It's far from euphemistic "fun" by any stretch of the imagination. In my mind, once it's working it should stay working. Alas, that has not always been the case and is unlikely to be. In recent months it's been quite a rollercoaster ride of mishaps. Meh.

I've done some comparing this morning between the RPi3B/RPi3B+ and here's what I found...

Code:
root@drie:~# cat /proc/device-tree/model
Raspberry Pi 3 Model B Rev 1.2
root@drie:~# uname -a
Linux drie 5.10.35-v7-sarpi3 #1 SMP Thu May 13 16:04:24 BST 2021 armv7l BCM2835 GNU/Linux
root@drie:~# dmesg |grep brcm
[    6.399004] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[    6.408678] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.415401] usbcore: registered new interface driver brcmfmac
[    6.736131] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[    6.757204] ieee80211 phy0: brcmf_c_process_clm_blob: clmload (4733 byte file) failed (-52)
[    6.764263] ieee80211 phy0: brcmf_c_preinit_dcmds: download CLM blob file failed, -5
[    6.770184] ieee80211 phy0: brcmf_bus_started: failed: -5
[    6.773975] ieee80211 phy0: brcmf_attach: dongle is not responding: err=-5
[    6.828607] brcmfmac: brcmf_sdio_firmware_callback: brcmf_attach failed
Code:
root@jook:~# cat /proc/device-tree/model
Raspberry Pi 3 Model B Plus Rev 1.3
root@jook:~# uname -a
Linux jook 5.10.35-v7-sarpi3 #1 SMP Thu May 13 16:04:24 BST 2021 armv7l BCM2835 GNU/Linux
root@jook:~# dmesg | grep brcm
[    6.411766] brcmfmac: F1 signature read @0x18000000=0x15264345
[    6.454823] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    6.463973] usbcore: registered new interface driver brcmfmac
[    6.605069] Bluetooth: hci0: BCM4345C0 'brcm/BCM4345C0.hcd' Patch
[    6.793116] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    6.813104] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan  4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
As you can see the clm_blob has failed on the RPi3B but clearly works perfectly on the RPi3B+. These two devices use different firmwares for their wireless chipsets - 43430 and 43455 respectively. The brcmfmac43455-sdio.clm_blob file exists but the brcmfmac43430-sdio.clm_blob is a symlink to cyfmac43430-sdio.clm_blob file.

Code:
root@drie:~# ls -lah /lib/firmware/brcm/brcmfmac43430-sdio.clm_blob
lrwxrwxrwx 1 root root 36 May 13 13:59 /lib/firmware/brcm/brcmfmac43430-sdio.clm_blob -> ../cypress/cyfmac43430-sdio.clm_blob
[RANT] I'm going to be totally honest and admit I do not know what's going on with this RPi wireless firmware, or why! It seems like it's constantly being prodded and poked like a lab-rat-test-subject at every opportunity under the guise of "progress" and I am genuinely disenchanted with it, to say the least. This is the main reason why I advise users who have issues with the RPi onboard wireless to invest in a USB wireless NIC, because it just saves time (especially mine) and is infinitely more reliable and convenient when it just works as expected, like we all know Slackware does. Even the cheapest USB wireless adapters don't suffer from the same indignities as the RPi onboard wireless shizzle. [/RANT]

However, according to the RPi guys, the clm_blob is embedded in the 43430 firmware. So, as a workaround, I deleted all the /lib/firmware/brcm/brcmfmac43430-sdio* related bin, blob, txt files and symlinks. Then I took brcmfmac43430-sdio.bin and brcmfmac43430-sdio.txt files from the latest Raspberry Pi OS and copied them into /lib/firmware/brcm/ in place of the ones I'd just deleted. Then I rebooted the system and...

Code:
root@drie:~# ifconfig wlan0
wlan0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:60:ec:1b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@drie:~# ifconfig wlan0 up
root@drie:~# iwlist wlan0 scan
Now I have the onboard wireless working on the RPi3B. Although dmesg throws up a shedload of errors, wireless works. It's not a solution but a stop-gap until I find another way of solving this issue, again, for like the 3rd or 4th time this year.
 
Old 05-15-2021, 05:51 AM   #5
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Lightbulb solution to fix RPi onboard wireless

"Familiarity breeds contempt" as the saying goes.

To save time and effort, just do this...

Code:
root@drie:~# rm -rf /lib/firmware/brcm
root@drie:~# installpkg sarpi*-hacks*.txz
root@drie:~# reboot
Solves the missing wireless interface issue.
 
Old 05-15-2021, 06:06 AM   #6
kermitdafrog8
Member
 
Registered: Dec 2018
Location: Orlando, FL
Distribution: Slackware ARM and X86_64
Posts: 152

Original Poster
Rep: Reputation: Disabled
sarpi3-boot-firmware May 13

Reinstall the hack package? OK I'll try that. And I meant the fun of using the latest release of something. Something is always bound to happen when upgrading.

Last edited by kermitdafrog8; 05-15-2021 at 06:07 AM.
 
1 members found this post helpful.
Old 05-15-2021, 06:45 AM   #7
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by kermitdafrog8 View Post
Reinstall the hack package? OK I'll try that. And I meant the fun of using the latest release of something. Something is always bound to happen when upgrading.
Ahuh, just delete whatever is in the /lib/firmware/brcm directory and (re)install/upgrade the sarpi*-hacks pkg. That'll bring back the missing wireless interface. You'll be installing the same files from the github.com/RPi-Distro/firmware-nonfree/brcm firmware tree. They work. The other brcm firmware files come from the kernel-firmware pkg shipped with Slackware ARM. Not entirely sure what's changed or why it's stopped the wireless from working.

I totally understand about the "fun" aspect but where this issue is concerned there is no fun, only repetitive frustration with it.

[EDIT] I found this in the Slackware ARM kernel-firmware pkg doinst.sh script...

Quote:
( cd lib/firmware/brcm ; rm -rf brcmfmac43430-sdio.clm_blob )
( cd lib/firmware/brcm ; ln -sf ../cypress/cyfmac43430-sdio.clm_blob brcmfmac43430-sdio.clm_blob )
This creates the brcmfmac43430-sdio.clm_blob symlink. "Why?" I really don't know the answer, BUT I also found this in the same script file...

Quote:
( cd lib/firmware/brcm ; rm -rf brcmfmac43455-sdio.clm_blob )
( cd lib/firmware/brcm ; ln -sf ../cypress/cyfmac43455-sdio.clm_blob brcmfmac43455-sdio.clm_blob )
Which has not created a brcmfmac43455-sdio.clm_blob symlink on my system. Although this is somewhat strange it should make these changes each time the kernel-firmware pkg is installed/updated. So the potential is there for the wireless interface to go AWOL as a result.

Fundamentally, because the clm_blob is embedded in the RPi brcmfmac43430 firmware, the brcmfmac43430-sdio.clm_blob file or symlink should be deleted. I think this is what's causing a lot of wireless issues for many users across the board on the RPi3/4 devices, not just on Slackware ARM.

Last edited by Exaga; 05-15-2021 at 07:43 AM. Reason: edit
 
Old 05-15-2021, 09:31 AM   #8
kermitdafrog8
Member
 
Registered: Dec 2018
Location: Orlando, FL
Distribution: Slackware ARM and X86_64
Posts: 152

Original Poster
Rep: Reputation: Disabled
sarpi3-boot-firmware May 13

This worked on my end and wireless has been restored. Thanks.
 
1 members found this post helpful.
Old 05-15-2021, 04:21 PM   #9
Exaga
SARPi Maintainer
 
Registered: Nov 2012
Distribution: Slackware [ARM]
Posts: 689

Rep: Reputation: 414Reputation: 414Reputation: 414Reputation: 414Reputation: 414
Quote:
Originally Posted by kermitdafrog8 View Post
This worked on my end and wireless has been restored. Thanks.
Good to hear you've nailed it. Need to thank you too for making me aware of this issue so quickly. It's caused me to address a few questions about it and other issues in relation to it within the SARPi shizzle.

It's whatever's going on between upstream and the RPi wireless firmware that's causing the problem(s) here, again. I've been wrestling with the thought of what I've advised you to do in order to solve the problem, and ideas on how to implement a more permanent solution. It's not really acceptable to ask users to delete files before installing a Slackware pkg in order for the hardware to work as intended, or even expect them to be aware of it beforehand. In addition to that, I do not condone messing about with the software pkgs which Mozes distributes. Alas, in this particular case it has to be done, from time to time. Otherwise it's going to cause the RPi onboard wireless to fail for a lot of users who rely on it.

So, seeing as the RPi3B+ and RPi4 onboard wireless is working as expected I'm not going to change anything with the existing firmware files until it becomes an issue. What I have decided to do is some jiggery-pokery with the sarpi-hacks pkg. From now on any brcmfmac43430-sdio* firmware files that exist will be removed and firmware that's known to work will replace them when the sarpi-hacks pkg is installed. I employed the same methods last year, or the year before that, when the RPi wireless firmware and upstream versions were asynchronous. Hopefully this will offer some respite and fewer headaches for Slackware ARM users on the RPis. Until the next time...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] SARPi3 on qemu pakcjo Slackware - ARM 4 10-17-2018 03:08 AM
Slackware ARM - SARPi3. Is it safe to perform system upgrade? horizn Slackware - ARM 1 08-10-2018 12:16 PM
Slackware ARM on a Raspberry Pi 3 - SARPi3 Exaga Slackware - ARM 11 08-05-2018 03:38 AM
SARPi3 - updated to kernel 4.4.8 Exaga Slackware - ARM 1 05-08-2016 01:27 PM
messed up my ipod firmware..need new firmware.. casimir Linux - Hardware 2 09-13-2004 08:11 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 06:42 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration