PANDA PAU06 DRIVER INSTALLATION ERROR

[hack3rWIZ (Dhruv)]

PLEASE HELP ME!! :
I am not able to install the drivers for my PANDA PAU06 adapter correctly.
I downloaded the drivers from their official site : http://www.pandawireless.com/download/LinuxDriver4Fedora_v2.5.0.3.tar.bz2

I followed each step correctly as asked in the user manual.
USER MANUAL:

1. Blacklist RT2800 wireless module in the Linux Kernel
   $>cd /etc/modprobe.d
   $>vi blacklist.conf
   Add “blacklist rt2800usb” at the end of the file.
2. Copy RT2870STA to /etc (RT2870STA.dat is located in your driver install directory)
   $>mkdir -p Wireless/RT2870STA (under /etc directory)
   $>cp RT2870STA.dat /etc/Wireless/RT2870STA/RT2870STA.dat3)
   Create tftpboot directory under root directory
   $> mkdir /tftpboot4)
   Compile the driver for the Panda Wireless N adapter
   $> tar jxvf LinuxDriver4Fedora_v2.5.0.3.tar.bz2
   $> make

On running the “make” command I got the following output:
make -C tools
make[1]: Entering directory ‘/home/hack3rwiz/Downloads/LinuxDriver4Fedora_v2.5.0.3/tools’
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory ‘/home/hack3rwiz/Downloads/LinuxDriver4Fedora_v2.5.0.3/tools’
/home/hack3rwiz/Downloads/LinuxDriver4Fedora_v2.5.0.3/tools/bin2h
cp -f os/linux/Makefile.6 /home/hack3rwiz/Downloads/LinuxDriver4Fedora_v2.5.0.3/os/linux/Makefile
make -C /lib/modules/5.5.0-1parrot1-amd64/build SUBDIRS=/home/hack3rwiz/Downloads/LinuxDriver4Fedora_v2.5.0.3/os/linux modules
make[1]: Entering directory ‘/usr/src/linux-headers-5.5.0-1parrot1-amd64’
sh: 0: Can’t open /usr/src/linux-headers-5.5.0-1parrot1-common/scripts/mkmakefile
make[3]: *** [/usr/src/linux-headers-5.5.0-1parrot1-common/Makefile:514: outputmakefile] Error 127
/usr/src/linux-headers-5.5.0-1parrot1-common/Makefile:659: include/config/auto.conf.cmd: No such file or directory
make[2]: *** [/usr/src/linux-headers-5.5.0-1parrot1-common/Makefile:677: include/config/auto.conf.cmd] Error 2
make[1]: *** [/usr/src/linux-headers-5.5.0-1parrot1-common/Makefile:179: sub-make] Error 2
make[1]: Leaving directory ‘/usr/src/linux-headers-5.5.0-1parrot1-amd64’
make: *** [Makefile:357: LINUX] Error 2

I am able to switch to monitor mode using : airmon-ng start wlx9cefd5fcef98
but, when I scan for networks using : airodump-ng wlan0mon
I get no access points as result. My aim is to use it for pen testing.

Version : Linux parrot 5.5.0-1parrot1-amd64 #1 SMP Parrot 5.5.17-1parrot1 (2020-04-25) x86_64 GNU/Linux

lsusb
Bus 001 Device 003: ID 148f:5372 Ralink Technology, Corp. RT5372 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

lsmod | grep “rt”
rt2800usb 28672 0
rt2x00usb 28672 1 rt2800usb
rt2800lib 143360 1 rt2800usb
rt2x00lib 73728 3 rt2800usb,rt2x00usb,rt2800lib
mac80211 880640 3 rt2x00lib,rt2x00usb,rt2800lib
crc_ccitt 16384 1 rt2800lib
cfg80211 839680 2 rt2x00lib,mac80211
parport_pc 28672 0
parport 61440 3 parport_pc,lp,ppdev
usbcore 315392 7 rt2800usb,ohci_hcd,ehci_pci,usbhid,ehci_hcd,ohci_pci,rt2x00usb

Installed it using the ISO file for Parrot Security (MATE) as Debian64 using Virtual Box.
I also installed the guest additions for it.

[RightToPrivacy (birdlover)]

@hack3rWIZ

/usr/src/linux-headers-5.5.0-1parrot1-common/Makefile:659: include/config/auto.conf.cmd: No such file or directory

Did you install kernel-headers for your exact kernel version, prior to attempting to compile/install drivers?

[hack3rWIZ (Dhruv)]

I did not install kernel-headers for my exact kernel version. I’m not sure how to do that.

[RightToPrivacy (birdlover)]

search for the Parrot package using:

apt search linux-headers

find the version for your linux kernel. Then, after successfully installing, try the driver installation again.

[hack3rWIZ (Dhruv)]

@RightToPrivacy

apt search linux-headers

I did the same, my headers are apparently installed correctly. This is not the issue I suppose. I am not able to install the drivers. Please help me.

[return_zero (Zeppole & Espresso)]

I plugged in my atheros usb device, in order to try to duplicate the problem. when i used airmon-ng to put it in monitor mode, the first instance complained that the name of the device was too long and was being renamed wlan0. running ifconfig at that point, i saw that the device had been renamed but was still in managed mode. simply running airmon-ng start wlan0 rather than airmon-ng start wlx********* successfully put it in monitor mode. So 2 step process instead of just one. First time renames second time makes the change…
Hope it helps, good luck