firmware-nonfree VS linux

Added nexmon firmware patch bcm43430a1/7_45_41_46 in an attempt to support RPiZ2Ws that use the RPi3 wifi chip (see https://github.com/RPi-Distro/firmware-nonfree/issues/23 for further information)

Rather than downloading the new driver from a random google drive (Step 1), I went to the source on GitHub: https://github.com/RPi-Distro/firmware-nonfree/raw/buster/brcm/brcmfmac43455-sdio.bin

The main issue I ran into was Wi-Fi support. The Pi Zero 2 requires firmware from the Raspberry Pi firmware repository in order to get access to the wlan0 interface. Found here: https://github.com/RPi-Distro/firmware-nonfree/tree/buster/brcm

I managed to get this working by copying the files from this repository to the /lib/firmware/brcm directory: https://github.com/bsdkurt/brcm-supplemental They are renamed files from the official Raspberry Pi repository for non-free firmware: Source Location: https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm Renamed to be board specific and set ccode=X2: brcmfmac43436-sdio.raspberrypi,model-zero-2-w.bin brcmfmac43436-sdio.raspberrypi,model-zero-2-w.clm_blob brcmfmac43436-sdio.raspberrypi,model-zero-2-w.txt

The directory for these files is /lib/firmware/brcm. You will need to download the brcmfmac43456 version of those three files available at https://github.com/RPi-Distro/firmware-nonfree/tree/master/brcm or grabbing from a working PiOS. But Kali will still try to load the brcmfmac4345 ones, so you need to rename the brcmfmac43456 to change that 6 to a 5.

Fan control generally involves hysteresis. This means a cooling fan turns on at one temperature, and then turns off once temperature has fallen to another lower temperature. This avoids cycling the fan on and off too much. The difference between those two temperatures is hysteresis. The default hysteresis is 10°C and maybe the fan never manages to cool the CPU to 45°C. A parameter has been added to change hysteresis: https://github.com/raspberrypi/linux/commit/fa390133fd17f2cc6aa5a7d2e472c073a1115fe1

I see that the PR against the Raspberry Pi linux repo is out [0]. Interestingly they are introducing a BCM2712 defconfig with a 64k default page size.

[0] - https://github.com/raspberrypi/linux/pull/5618

and can grab their patched kernel source here ( use the dtbs and overlays and kernel from your compiled version)

Also was your pi issue related to this? https://github.com/raspberrypi/linux/issues/3381 or what do you mean jittery, unstable?

Could be related to the driver load order/blacklisting (https://github.com/raspberrypi/linux/issues/435) Or couple of people report configuring the dtoverlay=imx477 in the boot config helped (https://raw.githubusercontent.com/raspberrypi/firmware/master/boot/overlays/README)

thanks, I also found this: https://github.com/raspberrypi/linux/issues/5398

And ready! :)

> It is the most basic task for Linux computer...

Well, it depends for whom. Also, you need adequate software and hardware. About wireless, the chipset in an RPi4 is designed for clients, not APs, and its capabilities on having multiple clients are quite limited:

https://github.com/raspberrypi/linux/issues/3010

Routers like the Omnia Turris, Mikrotik, PC Engines... use specific mini PCIe cards that can be as expensive as a full Raspberry Pi 4, just for the wireless.

https://www.discomp.eu/wireless-minipci-cards_c14501412.html