Trying to install wifi adaptor to kali linux manually

I have a huaweii matebookd, with a VM box and kali linux installed.
Bought a Wireless adapter (TL-WN725N), and although it appears on my VM, it does not appear on my kali.
I am trying to manually install it using these instructions:
1)You will need to blacklist another driver in order to use this one.
2)”echo “blacklist r8188eu” > “/etc/modprobe.d/realtek.conf”
3)”make && make install”
4)Reboot in order to blacklist and load the new driver/module.

However, when I am on step 3, this error appears:
make *** no rule to make target “install”. Stop.

Then it says no targets specified and no makefile found. Stop.

Any suggestions?

Go to Source
Author: Pedro

How to active the second console to a FreeBSD guest running in bhyve?

Background

I’m running FreeBSD 12.1-RELEASE as a host for bhyve virtual machines.

I have a FreeBSD 12.1-RELEASE guest running inside a VM. I would like to have two TTY-class devices configured for it.

According to the manual page, in order to start the VM with two TTY-class devices I have to start bhyve with command-line options similar to those: -l com1,/dev/nmdm0B -l com2,/dev/nmdm1B. Then I should be able to connect to the guest via those two nullmodem terminals with cu -l /dev/nmdm0A and cu -l /dev/nmdm1A.

Problem

The first command works as expected: cu -l /dev/nmdm0A shows me the main console of the guest.

The second command, however, attaches to the guest, but shows nothing. I would expect to show me a login prompt as if switched to another TTY.

What am I missing?


Additional details

  • The guest is a fresh installation of FreeBSD.

  • The output of dmesg | grep uart on the guest is as follows:

    uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0          
    uart0: console (115200,n,8,1)                                                    
    uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
    
  • I’ve tried setting hint.uart.1.flags first to 0x10 and then to 0x80 (although this one is for kernel debuggers from what I understand from uart(4)) and rebooted after each change. It didn’t work.

References

Go to Source
Author: Mateusz Piotrowski