Kali on Raspberry Pi 5 compiling issues

[pgielen]

Hi,

I have acquired an Alfa AWUS036AX adapter which uses a Realtek rtl8832BU chip and spent the morning trying to get it to work on my Raspberry Pi 5 with Kali Linux.

This requires a number of deviations from the installation procedure in the README.md file.

First of all, Kali for the RPi5 already has the kernel headers installed, so I installed the build essentials without the kernel-headers:
$ sudo apt install -y build-essential bc dkms git libelf-dev rfkill iw

I then activated the kernel headers following an advice on kali.org) with:
$ cd /usr/src/kernel $ sudo git clean -fdx && sudo make bcm2711_defconfig && sudo make modules_prepare

The current version of Kali for RPi5 comes with gcc 14 and the driver is built with gcc 12, so I first installed gcc-12 and g++-12, created an alternatives list and selected gcc12 as default:
$ sudo apt install gcc-12 $ sudo apt install g++-12 $ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-14 14 $ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/g++-14 14 $ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-12 12 $ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/g++-12 12 $ sudo update-alternatives --config gcc

Next, I issued the install command:
$ sudo ./install-driver.sh

This installation ended with a dkms error 10:

`
: ---------------------------
: install-driver.sh v20240429
: aarch64 (kernel architecture)
: arm64 (architecture to send to gcc)
: 4/4 (in-use/total processing units)
: 8131708 (total system memory)
: 6.6.45-v8+ (kernel version)
: gcc (version of gcc used to compile the kernel)
: gcc (Debian 12.4.0-2) 12.4.0
: dkms-3.0.13
: This system doesn't support Secure Boot
: ---------------------------

Checking for previously installed drivers...
Finished checking for and uninstalling previously installed drivers.
: ---------------------------

Starting installation.
Copying 8852bu.conf to /etc/modprobe.d
The dkms installation routines are in use.
Copying source files to /usr/src/rtl8852bu-1.19.3
Creating symlink /var/lib/dkms/rtl8852bu/1.19.3/source -> /usr/src/rtl8852bu-1.19.3
The driver was added to dkms successfully.
: ---------------------------

The kernel is built without module signing facility, modules won't be signed

Building module:
Cleaning build area...
Building module(s).......................................................................(bad exit status: 2)
Failed command:
kernelver=6.6.45-v8+ ./dkms-make.sh
Error! Bad return status for module build on kernel: 6.6.45-v8+ (aarch64)
Consult /var/lib/dkms/rtl8852bu/1.19.3/build/make.log for more information.
An error occurred. dkms build error: 10
Please report this error.
Please copy all screen output and paste it into the problem report.
Run the following before reattempting installation.
$ sudo ./remove-driver.sh
`

The make.log specifies the following errors:

ERROR: modpost: "mutex_lock" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "schedule" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "_raw_spin_lock_irqsave" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "iwe_stream_add_point" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "napi_disable" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "__arch_copy_from_user" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "register_netdev" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "memmove" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "skb_put" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! ERROR: modpost: "napi_schedule_prep" [/var/lib/dkms/rtl8852bu/1.19.3/build/8852bu.ko] undefined! WARNING: modpost: suppressed 192 unresolved symbol warnings because there were too many) make[3]: *** [scripts/Makefile.modpost:145: /var/lib/dkms/rtl8852bu/1.19.3/build/Module.symvers] Error 1 make[2]: *** [/usr/src/kernel/Makefile:1873: modpost] Error 2 make[1]: *** [Makefile:234: __sub-make] Error 2 make[1]: Leaving directory '/usr/src/kernel' make: *** [Makefile:751: modules] Error 2

Now I am at a loss. What should I try next?

[morrownr]

Hi @pgielen

Kali on Raspberry Pi's is problematic if using Realtek based USB WiFi adapters. I do my best to make the drivers work on as many distros as possible but some distros are a challenge. Not to mention that the Realtek drivers are a challenge.

What should I try next?

Here is what I would do: Return the adapter you have for a refund. Go to The Plug and Play List and get an adapter with a Mediatek chipset. It can be one with mt7921au or mt7612u or mt7610u chipsets. The Plug and Play List is menu item 2 on the Main Menu. Under that menu item is another items that is recommendations that are specific to Kali.

That will save you a LOT of frustration as the Mediatek drivers are in the kernel so the adapters just work. Also, the Mediatek drivers are SUPERIOR for monitor mode work, which is what I assume you are trying to do if you are running Kali. Several folks here can give advice on which adapter would work best for you if you provide details of your use case,

[morrownr]

Here is a direct link to the Recommended Adapters for Kali Linux document:

https://github.com/morrownr/USB-WiFi/blob/main/home/Recommended_Adapters_for_Kali_Linux.md

[pgielen]

Thank you! I chose the AWUS036ACHM from the list and got it today. It worked right away in Kali, without even having to install any drivers. This is a relief after spending way too much time trying in vain to get the AWUS036AX and before that the AWUS1900 to work on my new Raspberry Pi 5!

[morrownr]

@pgielen

I chose the AWUS036ACHM from the list and got it today. It worked right away in Kali, without even having to install any drivers.

The ACHM should serve you well. It is a favorite for use with Kali. I did not buy my ACHM for use with Kali and it was maybe a year after I bought it that I was doing a range test for this site and I discovered that it has range that is second to none. When other adapters have lost the connection, the little ACHM is still pushing packets.

I am very aware that the internet has Best Adapter for Kali lists all over the place and they are all bad in my opinion. Most appear to be click bait and the authors are not actually testing the adapters with Kali. The first hint that a list may be bad is if they have adapters that use Realtek chips. Realtek drivers are just not good for monitor mode use...maybe that can change but that is how it is today.

I hope you enjoy your ACHM as much as I have enjoyed mine.