Unable to connect to wireless as of update 22 Jan

TheTKS · 01-31-2021, 11:13 AM

Quote:

Originally Posted by rsamurti

I followed your advice. Now both wifi and wired connections are working. Thank you so much for reporting this.

Glad it’s working for you, too, but just a caution that, since I erased everything that was in /lib/firmware/brcm before reinstalling sarpi-hacks, I (and you) might now be missing some needed firmware files. I backed those up so if it turns out some are missing, they can be copied back in from backup.

But I’m enjoying the victory of recovering working wifi.

TKS

rsamurti · 01-31-2021, 11:46 AM

But bluetooth is not working. This has to be investigated.

TheTKS · 01-31-2021, 12:46 PM

Quote:

Originally Posted by rsamurti

But bluetooth is not working. This has to be investigated.

That’s happening in another thread. I’m going to follow that thread because I am curious about it, but have never tried to run BT on my RPi.

TKS

xor_ebx_ebx · 02-06-2021, 08:05 PM

I was having the same problem on my new Pi 4. After a little tinkering I discovered that /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt is the offender

Running

Code:

# rm /lib/fimrware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt

And rebooting gets wlan0 working for me

Odd that Exaga wouldn't be having this problem with his Pi. Given that this is a NVRAM config file, I'm thinking silent board revision. Either way, maybe a notice somewhere on the sarpi site about this? Or in the slack-desc for sarpi4-hacks?

zenithpbarm · 02-12-2021, 01:29 AM

Hi

Had this very same issue, no wlan0 interface, and dmesg would detect :

Code:

 brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6

then complain :

Code:

 brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

Solved the issue in /lib/firmware/brcm by removing all brcmfmac43455 files and importing the three brcmfmac43455 files from a working raspbian install

Cheers,
zp

rayburn · 02-19-2021, 08:47 AM

Quote:

Originally Posted by xor_ebx_ebx

I was having the same problem on my new Pi 4. After a little tinkering I discovered that /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt is the offender

Running

Code:

# rm /lib/fimrware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt

And rebooting gets wlan0 working for me

Odd that Exaga wouldn't be having this problem with his Pi. Given that this is a NVRAM config file, I'm thinking silent board revision. Either way, maybe a notice somewhere on the sarpi site about this? Or in the slack-desc for sarpi4-hacks?

Thank you for posting this simple solution! I tried various other fixes, but this one worked for me on my Pi4.

drmozes · 02-19-2021, 10:19 AM

Quote:

Originally Posted by zenithpbarm

Hi
Solved the issue in /lib/firmware/brcm by removing all brcmfmac43455 files and importing the three brcmfmac43455 files from a working raspbian install

Cheers,
zp

It'd be worth looking at the upstream versions of these and working with them - feeding back these issues.

These firmware files are from the Slackware firmware package, which obtains them from here.

Exaga · 02-19-2021, 06:01 PM

Quote:

Originally Posted by xor_ebx_ebx

I was having the same problem on my new Pi 4. After a little tinkering I discovered that /lib/firmware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt is the offender

Running

Code:

# rm /lib/fimrware/brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt

And rebooting gets wlan0 working for me

Odd that Exaga wouldn't be having this problem with his Pi. Given that this is a NVRAM config file, I'm thinking silent board revision. Either way, maybe a notice somewhere on the sarpi site about this? Or in the slack-desc for sarpi4-hacks?

Others around the Internet have done the same. The word is that this is a stop-gap solution as there's no impact to performance, but it does produce errors in 'dmesg'. However odd it may seem, it makes no sense to put up any notices somewhere until things are resolved upstream. Then once that's been done we'll see what's what. It's more than likely that nothing will need to be done after the stable tree fixes are in place.

Last month there was a storm on the horizon: https://git.kernel.org/pub/scm/linux...4936e310be2478

Quote:

brcm: Update Raspberry Pi 3B+/4B NVRAM for downstream changes
The Raspberry Pi Foundation NVRAM files have been updated for a new
BT/WiFi coexistence parameter for firmwares newer than 177, now
we have new firmwares (7.45.221) from Cypress for the BCM43455
update the NVRAM for these parameters.

Update the RPi4B NVRAM boardflags3 parameter to match too, which
also happens to be what we already have for the RPi3B+.

Earlier this month it looks like the storm was still raging: https://github.com/raspberrypi/linux/issues/4145

Quote:

a change in brcmfmac43455-sdio.raspberrypi,4-model-b.txt is to blame. That might explain why deleting the file helps.

... and still raging: https://bugzilla.kernel.org/show_bug.cgi?id=211731

Quote:

manually reverting the "boardflags3" change in brcmfmac43455-sdio.raspberrypi,4-model-b.txt seems to fix the problem. In other words, change that line back to:

> boardflags3=0x44200100

In the past few days: https://bugzilla.kernel.org/show_bug.cgi?id=210681

Quote:

Unfortunately it is taking quite a long time to get the fix for this into Linus' tree and the stable rules say that only fixes which are in Linus' tree can be cherry-picked into the stable series.

Of course, users are more than welcome to waste their own time finding fixes on Google or where-ever. https://forum.manjaro.org/t/wlan0-in...rpi-3b/52022/2

So let's just be patient and wait to see what happens and/or how long it takes.

Exaga · 03-20-2021, 06:26 AM

Quote:

Originally Posted by Exaga

So let's just be patient and wait to see what happens and/or how long it takes.

Guessing from the "no noise" phenomenon regarding the RPi3 and RPi4 onboard wireless and Bluetooth that there are no problems now. Only TKS has informed me that it's working as expected.

For future reference, in situations like these, waiting until things are fixed upstream is the best policy. Saves a lot of; effort, wasting time, and typing.

louigi600 · 03-21-2021, 12:30 PM

Don't want to take away from anything that has been said above ... just want to remind 2 things that can happen while you update your system:

accidentally overwrite some firmware required to get your wifi/BT card to work properly (while upgrading kernel-firmware)
wipe your wpa_supplicant.conf file if you choose to overwrite it with the one distributed with the new wpa_supplicant package

Exaga · 03-22-2021, 04:33 PM

Quote:

Originally Posted by louigi600

Don't want to take away from anything that has been said above ... just want to remind 2 things that can happen while you update your system:

accidentally overwrite some firmware required to get your wifi/BT card to work properly (while upgrading kernel-firmware)
wipe your wpa_supplicant.conf file if you choose to overwrite it with the one distributed with the new wpa_supplicant package

Just (re-)install sarpi-hacks*.txz pkg for firmware. For wpa_supplicant.conf ...

~# nano -w /etc/wpa_supplicant.conf

Code:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
update_config=0
country=<Insert 2 letter ISO 3166-1 country code here>

network={
 ssid="<Name of your wireless LAN>"
 psk="<Password for your wireless LAN>"
}

https://www.raspberrypi.org/document...ss/headless.md