0005282: Driver installation for AWUS1900 on RPi 3+ fails consistently. - Kali Linux Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0005282	Kali Linux	Kali Package Bug	public	2019-02-28 15:11	2019-03-01 12:37

Reporter	peerj	Assigned To	sbrun
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	no change required
Product Version	2019.1

Summary	0005282: Driver installation for AWUS1900 on RPi 3+ fails consistently.
Description	Installing the driver for USB wifi network card fails. See below for installation protocol and some other information.
Steps To Reproduce	apt-get install realtek-rtl88xxau-dkms
Additional Information	dmesg [108322.588622] usb 1-1.2: new high-speed USB device number 8 using dwc_otg [108322.677806] usb 1-1.2: New USB device found, idVendor=0bda, idProduct=8813 [108322.677836] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [108322.677855] usb 1-1.2: Product: 802.11ac NIC [108322.677872] usb 1-1.2: Manufacturer: Realtek [108322.677889] usb 1-1.2: SerialNumber: 123456 lsusb Bus 001 Device 008: ID 0bda:8813 Realtek Semiconductor Corp. RTL8814AU 802.11a/b/g/n/ac Wireless Adapter #Treiberinstallation: apt-get install realtek-rtl88xxau-dkms Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms Suggested packages: python3-apport Recommended packages: linux-headers-686-pae \| linux-headers-amd64 \| linux-headers-generic \| linux-headers The following NEW packages will be installed: dkms realtek-rtl88xxau-dkms 0 upgraded, 2 newly installed, 0 to remove and 2 not upgraded. Need to get 1920 kB of archives. After this operation, 19.1 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main arm64 dkms all 2.6.1-4 [74.4 kB] Get:2 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/contrib arm64 realtek-rtl88xxau-dkms all 5.2.20.2~20181106-0kali1 [1846 kB] Fetched 1920 kB in 3s (565 kB/s) Selecting previously unselected package dkms. (Reading database ... 324109 files and directories currently installed.) Preparing to unpack .../archives/dkms_2.6.1-4_all.deb ... Unpacking dkms (2.6.1-4) ... Selecting previously unselected package realtek-rtl88xxau-dkms. Preparing to unpack .../realtek-rtl88xxau-dkms_5.2.20.2~20181106-0kali1_all.deb ... Unpacking realtek-rtl88xxau-dkms (5.2.20.2~20181106-0kali1) ... Setting up dkms (2.6.1-4) ... Setting up realtek-rtl88xxau-dkms (5.2.20.2~20181106-0kali1) ... Loading new realtek-rtl88xxau-5.2.20.2~20181106 DKMS files... It is likely that 4.14.71-v8 belongs to a chroot's host Building for 4.14.71-v8 Building initial module for 4.14.71-v8 Error! Bad return status for module build on kernel: 4.14.71-v8 (aarch64) Consult /var/lib/dkms/realtek-rtl88xxau/5.2.20.2~20181106/build/make.log for more information. dpkg: error processing package realtek-rtl88xxau-dkms (--configure): installed realtek-rtl88xxau-dkms package post-installation script subprocess returned error exit status 10 Processing triggers for man-db (2.8.5-2) ... Errors were encountered while processing: realtek-rtl88xxau-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) cat /var/lib/dkms/realtek-rtl88xxau/5.2.20.2~20181106/build/make.log DKMS make.log for realtek-rtl88xxau-5.2.20.2~20181106 for kernel 4.14.71-v8 (aarch64) Thu Feb 28 14:03:27 UTC 2019 make ARCH=arm64 CROSS_COMPILE= -C /lib/modules/4.14.71-v8/build M=/var/lib/dkms/realtek-rtl88xxau/5.2.20.2~20181106/build modules make[1]: Entering directory '/usr/src/kernel' ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. WARNING: Symbol version dump ./Module.symvers is missing; modules will have no dependencies and modversions. Building modules, stage 2. scripts/Makefile.modpost:43: include/config/auto.conf: No such file or directory make[2]: No rule to make target 'include/config/auto.conf'. Stop. make[1]: [Makefile:1531: modules] Error 2 make[1]: Leaving directory '/usr/src/kernel' make: *** [Makefile:1935: modules] Error 2 uname -a Linux kali 4.14.71-v8 0000001 SMP PREEMPT Wed Oct 31 21:41:06 UTC 2018 aarch64 GNU/Linux

sbrun 2019-02-28 15:52 manager ~0010377	Thank you for your interest in Kali. Please report this issue to upstream: https://github.com/aircrack-ng/rtl8812au

peerj 2019-02-28 16:18 reporter ~0010378	Reported to upstream, see: https://github.com/aircrack-ng/rtl8812au/issues/287

peerj 2019-03-01 10:56 reporter ~0010380	I closed the bug on upstream where the conclusion is: The kali images support the adapter out of the box. It's plug and play and does not require any additional drivers The stock kali installation is set up correctly and exhaustive to allow compiling kernel drivers without any additional packages apart from "bc" We need to update the driver documentation to point out that the dkms package is not required for Kali-Pi's and not supported either. I'm not sure how my installation started to switch to 4.19 (my guess it's the rolling upgrades starting from the 2018.4 image) although I still had the 4.14 kernel, a desync which seemed to hinder the driver compilations which he declared now as unsupported for Kali-RP. So the problem I started this thread with seems to be solved as far as upstream is concerned, but I'm not sure if such a desync could still happen later with upgrading through the rollings, which might create certain problems in an installation. So, i'll start afresh with another image and SD card, but I'll leave this open to check if the rolling mechanism needs some correction, and leave it up to you to close it, to ask for more info or to reclassify it.

peerj 2019-03-01 11:21 reporter ~0010381	Also, the explanations from upstream made me remember that when I chose the image to install, I didn't know which one to chose from https://www.offensive-security.com/kali-linux-arm-images/, my platform being a RPi3+: Kali Linux RPi Kali Linux RPi0w Nexmon Kali Linux RaspberryPi 3 64 bit Kali Linux P4wnP1 Aloa Kali Linux RaspberryPi 2 and 3 So I went with the 64 bit following some incomplete heuristic based on lack of knowledge in the details of the differences between these versions, excluding only RPi0w (which it is not) and "P4wnP1 Aloa" (which googling showed it to be a special purpose use of the Pi, so it looks like maybe it should rather be a meta package and not a separate image), and considereing that "" must mean some kind of old RPi 1 or so, and "64 bit" being more advanced and thus better, although with the explanations it seems that it's rather less advanced since it's newer and less tested. In other words, I become somewhat unwittingly a tester for the newer 64 bit platform instead of getting a better proven image to test the things I wanted to test. That's fine with me since it's a useful learning experience as well, but maybe the download page could benefit with some more details to help choose the right image: The names given mix board revisions, purpose and driver details, which would be a 3 dimensional choice matrix, crammed into a shortened one-liner expliciting only some of the choices made to build the variant. So this leads to more questions like: "what do I chose if I want to use "Nexmon" with a "Pi3+"? Will I then need to compile anew (with dkms...)? The answers maybe become clear only when reading a lot of blog and external sites (or when studying the build scripts).

Date Modified	Username	Field	Change
2019-02-28 15:11	peerj	New Issue
2019-02-28 15:52	sbrun	Note Added: 0010377
2019-02-28 16:18	peerj	Note Added: 0010378
2019-03-01 10:56	peerj	Note Added: 0010380
2019-03-01 11:21	peerj	Note Added: 0010381
2019-03-01 12:37	sbrun	Assigned To	=> sbrun
2019-03-01 12:37	sbrun	Status	new => closed
2019-03-01 12:37	sbrun	Resolution	open => no change required