void-docs VS firmware-nonfree

In general, Void assumes familiarity with the principles of Linux and UNIX system. Basic questions about configuring or running a Linux system can frequently be answered with a Google search. The Internet grew up with UNIX, and Linux grew up on the Internet; you are encouraged to avail yourself of the extensive body of knowledge already out there. Some particulars of Void administration are described in the handbook; consult this document before asking common questions about configuring Void systems.

I know for sure that these images work with espeakup, and espeakup can be enabled at boot by adding live.screenreader to the command line as described here

You might look at https://docs.voidlinux.org/, which provides a good overview of Void. The package manager, xbps is [my opinion] better that apt [I have to use the latter in AntiX Linux].

the final criticism i have for void is the way they have decided to host their docs; as this void-docs. This bottlenecks the possible amount of expertise you'd receive from your doc writers by ensuring that only those who want to learn git are able to contribute to your docs. this, to me, is very inadequate if your intent is to have documentation written by those who are very good at docwriting but not necessarily maneuvering in version control systems like git. i'm not sure what the impetus was to move away from the traditional wiki model, but this from my perspective is a failure.

Follow the guide on the void website and you will be fine. Come here for support, we love helping others out and it's a great community, on par with the OpenBSD community as far as being helpful and encouraging you to learn the OS. If you find there's a package you need that hasn't been added to xbps yet, you can use a Flatpak or AppImage (easy way) or build the package yourself using xbps-src (advanced way, worth learning down the line).

I just made a PR on their github to add this.

Perl has traditionally been my language of choice for this sort of stuff (e.g. this script for converting mdBook to LaTeX), but more recently i've been focusing on POSIX shell scripts as a personal challenge and learning exercise.

from https://docs.voidlinux.org/

Understanding how runit manages services is critical. Also, there are certain "restricted" packages that xbps can manage but not download. The handbook does a good job covering both topics.

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.