How do i install after download?

[aibugra]

hello, i am very new to these issues, i need your help. i downloaded the driver you shared, but i don't know how to install it, i would appreciate it if you tell me step by step :)

[morrownr]

Hi @aibugra

From a terminal, run the following and paste the results in a reply:

$ lsusb

[morrownr]

Forgot to mention that you need to place the usb wifi adapter in a port before running the above.

[aibugra]

┌──(root㉿kali)-[/home/kali/7612u] └─# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Virtual Bluetooth Adapter Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

[morrownr]

Okay, I don't see a usb wifi adapter in your system. I see you are running Kali but I really don't have any details to go on.

Can you tell me the brand and name of your adapter? What version of Kali are you using? What computer are your using? amd64? 64 bit? arm64?

Can you elaborate on what you are done so far and what your plans are?

[aibugra]

adapter = comfast cf-wu785ac my computer 64 bit linux: 6.4.0-kali3-amd64

[morrownr]

I think that adapter uses a mt7612u chipset so it should be plug and play on a modern distro of Kali amd64. It is, however, a multi-state adapter so we may need to see if Modeswitching is working:

https://github.com/morrownr/USB-WiFi

Look at menu item 6. How to Modeswitch for an idea of what I am talking about.

I need to be away from my desk for a while but should be back in a few hours.

[aibugra]

still not happening

[morrownr]

You might have a bad connection. Unplug the cable from both ports and plug them back in.

lsusb should show the adapter if it is plugged in and you start the computer.

[aibugra]

I do what you said but it doesn't work. it works on windows machine the adapter is not broken.

[morrownr]

I did a review of what you have posted and I see the problem. I missed it the first time:

VMware, Inc

You are running in a VM. I am not familiar with VMware but I do know there will be some settings you need to change to allow the usb adapter to work. Let me throw out some ideas:

• go to the VMware forums and post an issue with your details to see if someone that knows how can help you.
• go to the Kali forums and post requesting help... make sure you tell them you are running in VMware.
• there are some videos on Youtube that could help.

[aibugra]

I switched to vitualbox and typed lsusb ┌──(kali㉿kali)-[~] └─$ lsusb Bus 002 Device 002: ID 0e8d:7612 MediaTek Inc. MT7612U 802.11a/b/g/n/ac Wireless Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub it's coming out now

[morrownr]

Bus 002 Device 002: ID 0e8d:7612 MediaTek Inc. MT7612U 802.11a/b/g/n/ac Wireless Adapter

That is it. You must have already changed the settings in VirtualBox. I usually keep one installation of VirtualBox in my lab for testing. I keep a link to a guide for VirtualBox in the FAQ of some of the drivers I maintain. I use it as Linux host and Linux client as I don't use Windows.

Keep in mind that your adapter does not require the installation of a driver as the driver for the mt7612u chipset is maintained inside the kernel.

If you need anything else, let me know. In case you have not been there, The Main Menu for this site is:

https://github.com/morrownr/USB-WiFi

[aibugra]

sorry i don't understand what i have to do

[aibugra]

┌──(root㉿kali)-[/home/kali/Downloads/7612u-main] └─# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 08:00:27:53:0c:ba txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 130 bytes 24029 (23.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 4 bytes 240 (240.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4 bytes 240 (240.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Only when I type lsusb the device appears

[morrownr]

ifconfig

I recommend you not to use ifconfig as it is depreciated and is not longer maintained.

Use "iw"

Try:

$ iw dev

... and post what you get.

sorry i don't understand what i have to do

That depends on what you want to do. Tell me what you want to do and I'll try to help.

[aibugra]

┌──(root㉿kali)-[/home/kali] └─# iw dev I want to use monitor mode

[aibugra]

When I type iw dev it should exit but it doesn't.

[morrownr]

When I type iw dev it should exit but it doesn't.

exit?

I'm not sure why it would exit (close terminal).

What it should do is show the wifi interfaces that are available to you. Example:

$ iw dev phy#2 Interface wlx00c0cab37abb ifindex 5 wdev 0x200000001 addr 00:c0:ca:b3:7a:bb type managed txpower 3.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcoltx-bytes tx-packets 0 0 0 0 0 0 0 00

[aibugra]

┌──(root㉿kali)-[/home/kali] └─# iw dev

┌──(root㉿kali)-[/home/kali] └─# it doesn't seem

[morrownr]

Is this your first experience with Linux?

If so, let me advise you that what you are doing is like starting high school without having attended elementary school.

Can I suggest a better way? If so, do you have an older computer that could be used to practice with Linux? Maybe a friend has an unused computer that can be cleaned up and you can install a Linux distro as the only operating system and practice?

Using Linux is something that really needs a month or two of practice so that you have many of the basics down. Tell me what you think.

@morrownr

[aibugra]

No, I've been dealing with software for about 2 years, I'm just trying to solve this adapter, but I couldn't handle it.

[morrownr]

Okay. There are many people that have a hard time with wifi in VM's. Let me give you some alternatives ways to do what you are trying to do:

Dual Booting Kali with Windows https://www.kali.org/docs/installation/dual-boot-kali-with-windows/

Making a Kali Bootable USB Drive on Windows https://www.kali.org/docs/usb/live-usb-install-with-windows/

Both of those methods will allow to run Kali without a VM. I use Dual Booting a lot here as it allows me to run several Linux distros on the same system. Both of the above should be accomplished with care.

[aibugra]

I guess that's what happens because the driver is not installed

[morrownr]

The driver is not installed per se because it comes with the kernel. It is there. The problem is somewhere between the host os and the client os which leaves the VM.

I did find this:

https://forums.kali.org/showthread.php?128646-SOLVED-Alfa-AWUS036ACM-amp-Kali-2022-4-on-VB

[aibugra]

You need to install the driver to fix the error, I couldn't understand your driver, finally if you can help me with this, my friend, after installing the driver, the job is done.

[morrownr]

Hi @aibugra

I do not have a driver for the mt7612u chipset. The person that has the driver is Linus Torvalds. You may recognize the name.

Here is his github site and the folder where the driver is maintained:

https://github.com/torvalds/linux/tree/master/drivers/net/wireless/mediatek

The following location is where the driver is on my system:

/usr/lib/modules/6.2.0-32-generic/kernel/drivers/net/wireless/mediatek/mt76/mt76x2/mt76x2u.ko

To see it on your system, please use the following command to determine your kernel version:

$ uname -r

Now replace <kernel version> in the line below with your kernel version and go see if the driver is there:

/usr/lib/modules//kernel/drivers/net/wireless/mediatek/mt76/mt76x2/mt76x2u.ko

Tell me if the above file is located at the above spot on your system.

[aibugra]

┌──(root㉿kali)-[/home/kali] └─# /usr/lib/modules/6.4.0-kali3-amd64/kernel/drivers/net/wireless/mediatek/mt76/mt76x2/mt76x2u.ko

zsh: permission denied: /usr/lib/modules/6.4.0-kali3-amd64/kernel/drivers/net/wireless/mediatek/mt76/mt76x2/mt76x2u.ko

[morrownr]

Try:

$ cd /usr/lib/modules/6.4.0-kali3-amd64/kernel/drivers/net/wireless/mediatek/mt76/mt76x2

$ ls

Tell me what files you see.

[aibugra]

┌──(root㉿kali)-[/usr/…/wireless/mediatek/mt76/mt76x2] └─# ls mt76x2-common.ko mt76x2e.ko mt76x2u.ko

[morrownr]

There you go.

mt79x2u.ko is the usb chipset driver, which is what you need. It is there. No need to install what is there.

So, where are you in the process? Remember that I have almost no visibility on what you have been doing so be detailed. Are you installing Kali as multiboot, on a flash driver or are you still fighting with the VM?

[aibugra]

I'm having trouble with vm

[morrownr]

My ability to help you with the VM is limited. Please stop by and post detailed reports on the VirtualBox and Kali forums.

Good luck.

[aibugra]

It gave an error when I did "make" while downloading, so it didn't install properly

[aibugra]

sorry bro the problem is not with vm

[aibugra]

┌──(root㉿kali)-[/home/kali/Downloads/mt7612u-master] └─# make make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.4.0-kali3-amd64/build M=/home/kali/Downloads/mt7612u-master modules make[1]: Entering directory '/usr/src/linux-headers-6.4.0-kali3-amd64' CC [M] /home/kali/Downloads/mt7612u-master/ap/ap_mbss.o In file included from /home/kali/Downloads/mt7612u-master/include/rtmp_os.h:37, from /home/kali/Downloads/mt7612u-master/include/rtmp_comm.h:38, from /home/kali/Downloads/mt7612u-master/include/rt_config.h:35, from /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:47: /home/kali/Downloads/mt7612u-master/include/os/rt_linux.h:230:9: error: unknown type name ‘mm_segment_t’ 230 | mm_segment_t fs; | ^~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c: In function ‘MBSS_Init’: /home/kali/Downloads/mt7612u-master/include/os/rt_linux.h:125:33: error: expected ‘(’ before ‘static’ 125 | #define inline static inline | ^~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/compiler_types.h:332:24: note: in expansion of macro ‘__inline’ 332 | #define asm_inline asm inline | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:28:9: note: in expansion of macro ‘asm_inline’ 28 | asm_inline volatile("1:\t" ins "\n" \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:83:9: note: in expansion of macro ‘_BUG_FLAGS’ 83 | _BUG_FLAGS(ASM_UD2, flags, ASM_REACHABLE); \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:106:17: note: in expansion of macro ‘__WARN_FLAGS’ 106 | WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:133:17: note: in expansion of macro ‘WARN_printf’ 133 | __WARN_printf(TAINT_WARN, format); \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/once_lite.h:31:25: note: in expansion of macro ‘WARN’ 31 | func(VA_ARGS); \ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:151:9: note: in expansion of macro ‘DO_ONCE_LITE_IF’ 151 | DO_ONCE_LITE_IF(condition, WARN, 1, format) | ^~~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:578:9: note: in expansion of macro ‘WARN_ONCE’ 578 | WARN_ONCE(fortify_memcpy_chk(fortify_size, p_size, \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:630:26: note: in expansion of macro ‘fortify_memcpy_chk’ 630 | #define memcpy(p, q, s) fortify_memcpy_chk(p, q, s, \ | ^~~~~~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:134:17: note: in expansion of macro ‘memcpy’ 134 | memcpy(&netDevHook, pNetDevOps, sizeof(netDevHook)); | ^~ In file included from /usr/src/linux-headers-6.4.0-kali3-common/include/linux/bug.h:5, from /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/paravirt.h:15, from /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/cpuid.h:62, from /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/processor.h:19, from /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/timex.h:5, from /usr/src/linux-headers-6.4.0-kali3-common/include/linux/timex.h:67, from /usr/src/linux-headers-6.4.0-kali3-common/include/linux/time32.h:13, from /usr/src/linux-headers-6.4.0-kali3-common/include/linux/time.h:60, from /usr/src/linux-headers-6.4.0-kali3-common/include/linux/stat.h:19, from /usr/src/linux-headers-6.4.0-kali3-common/include/linux/module.h:13, from /home/kali/Downloads/mt7612u-master/include/os/rt_linux.h:18: /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:28:29: error: expected identifier or ‘(’ before string constant 28 | asm_inline volatile("1:\t" ins "\n" \ | ^~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:83:9: note: in expansion of macro ‘_BUG_FLAGS’ 83 | _BUG_FLAGS(ASM_UD2, __flags, ASM_REACHABLE); \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:106:17: note: in expansion of macro ‘WARN_FLAGS’ 106 | WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:133:17: note: in expansion of macro ‘__WARN_printf’ 133 | WARN_printf(TAINT_WARN, format); \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/once_lite.h:31:25: note: in expansion of macro ‘WARN’ 31 | func(VA_ARGS); \ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:151:9: note: in expansion of macro ‘DO_ONCE_LITE_IF’ 151 | DO_ONCE_LITE_IF(condition, WARN, 1, format) | ^~~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:578:9: note: in expansion of macro ‘WARN_ONCE’ 578 | WARN_ONCE(fortify_memcpy_chk(fortify_size, p_size, \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:630:26: note: in expansion of macro ‘fortify_memcpy_chk’ 630 | #define memcpy(p, q, s) fortify_memcpy_chk(p, q, s, \ | ^~~~~~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:134:17: note: in expansion of macro ‘memcpy’ 134 | memcpy(&netDevHook, pNetDevOps, sizeof(netDevHook)); | ^~ /home/kali/Downloads/mt7612u-master/include/os/rt_linux.h:125:33: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] 125 | #define inline static inline | ^~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/compiler_types.h:332:24: note: in expansion of macro ‘__inline’ 332 | #define asm_inline asm inline | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:28:9: note: in expansion of macro ‘asm_inline’ 28 | asm_inline volatile("1:\t" ins "\n" \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:83:9: note: in expansion of macro ‘_BUG_FLAGS’ 83 | _BUG_FLAGS(ASM_UD2, flags, ASM_REACHABLE); \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:106:17: note: in expansion of macro ‘__WARN_FLAGS’ 106 | WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:133:17: note: in expansion of macro ‘WARN_printf’ 133 | __WARN_printf(TAINT_WARN, format); \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/once_lite.h:31:25: note: in expansion of macro ‘WARN’ 31 | func(VA_ARGS); \ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:151:9: note: in expansion of macro ‘DO_ONCE_LITE_IF’ 151 | DO_ONCE_LITE_IF(condition, WARN, 1, format) | ^~~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:578:9: note: in expansion of macro ‘WARN_ONCE’ 578 | WARN_ONCE(fortify_memcpy_chk(fortify_size, p_size, \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:630:26: note: in expansion of macro ‘fortify_memcpy_chk’ 630 | #define memcpy(p, q, s) fortify_memcpy_chk(p, q, s, \ | ^~~~~~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:134:17: note: in expansion of macro ‘memcpy’ 134 | memcpy(&netDevHook, pNetDevOps, sizeof(netDevHook)); | ^~ /home/kali/Downloads/mt7612u-master/include/os/rt_linux.h:125:33: error: expected ‘(’ before ‘static’ 125 | #define __inline static inline | ^~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/compiler_types.h:332:24: note: in expansion of macro ‘inline’ 332 | #define asm_inline asm inline | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:28:9: note: in expansion of macro ‘asm_inline’ 28 | asm_inline volatile("1:\t" ins "\n" \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:83:9: note: in expansion of macro ‘_BUG_FLAGS’ 83 | _BUG_FLAGS(ASM_UD2, __flags, ASM_REACHABLE); \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:106:17: note: in expansion of macro ‘WARN_FLAGS’ 106 | WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:133:17: note: in expansion of macro ‘__WARN_printf’ 133 | WARN_printf(TAINT_WARN, format); \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/once_lite.h:31:25: note: in expansion of macro ‘WARN’ 31 | func(VA_ARGS); \ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:151:9: note: in expansion of macro ‘DO_ONCE_LITE_IF’ 151 | DO_ONCE_LITE_IF(condition, WARN, 1, format) | ^~~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:578:9: note: in expansion of macro ‘WARN_ONCE’ 578 | WARN_ONCE(fortify_memcpy_chk(fortify_size, p_size, \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:634:27: note: in expansion of macro ‘fortify_memcpy_chk’ 634 | #define memmove(p, q, s) fortify_memcpy_chk(p, q, s, \ | ^~~~~~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:141:17: note: in expansion of macro ‘memmove’ 141 | memmove(&netDevHook.devAddr[0], &wdev->bssid[0], MAC_ADDR_LEN); | ^~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:28:29: error: expected identifier or ‘(’ before string constant 28 | asm_inline volatile("1:\t" ins "\n" \ | ^~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:83:9: note: in expansion of macro ‘_BUG_FLAGS’ 83 | _BUG_FLAGS(ASM_UD2, flags, ASM_REACHABLE); \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:106:17: note: in expansion of macro ‘__WARN_FLAGS’ 106 | WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:133:17: note: in expansion of macro ‘WARN_printf’ 133 | __WARN_printf(TAINT_WARN, format); \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/once_lite.h:31:25: note: in expansion of macro ‘WARN’ 31 | func(VA_ARGS); \ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:151:9: note: in expansion of macro ‘DO_ONCE_LITE_IF’ 151 | DO_ONCE_LITE_IF(condition, WARN, 1, format) | ^~~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:578:9: note: in expansion of macro ‘WARN_ONCE’ 578 | WARN_ONCE(fortify_memcpy_chk(fortify_size, p_size, \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:634:27: note: in expansion of macro ‘fortify_memcpy_chk’ 634 | #define memmove(p, q, s) fortify_memcpy_chk(p, q, s, \ | ^~~~~~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:141:17: note: in expansion of macro ‘memmove’ 141 | memmove(&netDevHook.devAddr[0], &wdev->bssid[0], MAC_ADDR_LEN); | ^~~ /home/kali/Downloads/mt7612u-master/include/os/rt_linux.h:125:33: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] 125 | #define __inline static inline | ^~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/compiler_types.h:332:24: note: in expansion of macro ‘inline’ 332 | #define asm_inline asm inline | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:28:9: note: in expansion of macro ‘asm_inline’ 28 | asm_inline volatile("1:\t" ins "\n" \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/arch/x86/include/asm/bug.h:83:9: note: in expansion of macro ‘_BUG_FLAGS’ 83 | _BUG_FLAGS(ASM_UD2, __flags, ASM_REACHABLE); \ | ^~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:106:17: note: in expansion of macro ‘WARN_FLAGS’ 106 | WARN_FLAGS(BUGFLAG_NO_CUT_HERE | BUGFLAG_TAINT(taint));\ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:133:17: note: in expansion of macro ‘__WARN_printf’ 133 | WARN_printf(TAINT_WARN, format); \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/once_lite.h:31:25: note: in expansion of macro ‘WARN’ 31 | func(VA_ARGS); \ | ^~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/asm-generic/bug.h:151:9: note: in expansion of macro ‘DO_ONCE_LITE_IF’ 151 | DO_ONCE_LITE_IF(condition, WARN, 1, format) | ^~~~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:578:9: note: in expansion of macro ‘WARN_ONCE’ 578 | WARN_ONCE(fortify_memcpy_chk(fortify_size, p_size, \ | ^~~~~ /usr/src/linux-headers-6.4.0-kali3-common/include/linux/fortify-string.h:634:27: note: in expansion of macro ‘fortify_memcpy_chk’ 634 | #define memmove(p, q, s) fortify_memcpy_chk(p, q, s, \ | ^~~~~~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:141:17: note: in expansion of macro ‘memmove’ 141 | memmove(&netDevHook.devAddr[0], &wdev->bssid[0], MAC_ADDR_LEN); | ^~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c: In function ‘MBSS_Close’: /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:279:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] 279 | if (BssId < 0) | ^~ /home/kali/Downloads/mt7612u-master/include/os/rt_linux.h:559:49: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ 559 | #define RTMP_OS_NETDEV_STOP_QUEUE(_pNetDev) netif_stop_queue((_pNetDev)) | ^~~~ /home/kali/Downloads/mt7612u-master/ap/ap_mbss.c:282:9: note: in expansion of macro ‘RTMP_OS_NETDEV_STOP_QUEUE’ 282 | RTMP_OS_NETDEV_STOP_QUEUE(pDev); | ^~~~~~~~~ make[2]: [/usr/src/linux-headers-6.4.0-kali3-common/scripts/Makefile.build:257: /home/kali/Downloads/mt7612u-master/ap/ap_mbss.o] Error 1 make[1]: [/usr/src/linux-headers-6.4.0-kali3-common/Makefile:2057: /home/kali/Downloads/mt7612u-master] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.4.0-kali3-amd64' make: *** [Makefile:615: modules] Error 2

[morrownr]

Please stop trying to compile an out-of-kernel driver. If you were to get it to compile, which is extremely unlikely, it would just conflict with the driver that is already installed (I'll call it installed to make you happy.)

Seriously, please stop trying to install a driver. You are simply going to make a mess and not solve the problem.

I've already given you the best advice I can give you. My ACM works just fine on numerous computers here and I have never compiled and installed a driver. If you were using Kali on bare metal, my bet is that we would not be having this conversation. I am not setup currently to try to duplicate this.

It might help you understand how drivers work on Linux if you read menu item 1 on the Main Menu.

[aibugra]

bro you are saying that there is no need to download the driver, it comes already installed. then why are there errors when i look inside the mt76x2u driver

[aibugra]

^@MAC RX failed to stop ^@ROM patch already applied ^@mt7662_rom_patch.bin^@failed to load firmware ^@ROM patch build: %.15s ^@failed to load ROM patch ^@mt7662.bin^@Firmware Version: %d.%d.%02d ^@Build: %x ^@Build Time: %.16s ^@firmware failed to start

like this

[amisix]

I think you should take the advice @morrownr has so graciously given you.

[morrownr]

are saying that there is no need to download the driver

Yes. I have said it several times. You seem to think that Linux works like Windows. It does not in many ways. The development model of Linux is far different than Windows. Windows uses a development model where a new version is released every few years. The API's are mostly locked and drivers for Windows 7 should always work on Windows 7. Linux on the other hard does not lock the API's for years at a time. In fact, we get a new version of the Linux kernel about every 2.5 months on a reliable schedule. So, the API's are locked for about 2.5 months. The very old out-of=kernel driver you found for the mt7612u chipset had absolutely no chance of working on a modern 6.4 kernel. Mediatek transitioned from the wireless model many years ago and adopted the guidance from the Linux Foundation which spells out what is commonly called mac80211. The very old WEX way of doing things is depreciated.

Guidance from the Linux Foundation is for companies to join and work within the established structure to maintain their drivers in the Linux kernel. Mediatek does a good job with this. When a new Linux kernel comes out, a new driver automatically comes with the new kernel and if API changes were necessary, the Mediatek devs would have made the adjustments for us. More info is available in Main Menu items 1 and 2.

^@MAC RX failed to stop ^@rom patch already applied ^@mt7662_rom_patch.bin^@failed to load firmware ^@rom patch build: %.15s ^@failed to load ROM patch ^@mt7662.bin^@firmware Version: %d.%d.%02d ^@build: %x ^@build Time: %.16s ^@firmware failed to start

like this

This appears to indicate that the Firmware is not loading correctly. Each in-kernel driver has one or more firmware files that support the driver. What is happening in this case is not clear. I do not know everything that you have done. Your insistence on installing an old out-of-kernel driver that stood no chance of working may have caused some damage to the system.

What needs to be done at this point is you need a clean installation. As I previously recommended, multi-boot and running from a usb flash drive are options you should seriously consider unless you can find an old system to do your Linux learning on.

I've been using Linux since around 1994. I try to help fellow Linux users as best I can. Sometimes that help is to sent users to other locations that are better suited to the problem as hand. Sometimes I suggest things to read so users can gain a better understanding of how things work. You have been resisting my suggestions. I am already dealing with health problems but have taken the time to try to to help you.

[aibugra]

I really thank you for your efforts. I also experienced the last devastating earthquake in Turkey, so the instinct of resistance was formed, I think that feeling is reflected here as well, so I apologize.

[morrownr]

I really thank you for your efforts.

You are welcome.

I also experienced the last devastating earthquake in Turkey...

I hate to hear that. We are well aware of the disaster that was this earthquake and hope that the recovery is going well. Over here in North America, we know about disasters to include hurricanes, tornadoes, earthquakes, floods and more.

I have spent a lot of time in Turkey. I worked out of a location near Adana. I enjoyed my time in Turkey.

I apologize

Accepted.

I can continue to try to help but I really need you to understand that while using a VM to do what you want may work, it can be a challenge. Throw in the fact that Kali is a challenge because it is a bleeding edge rolling distro and the issues are compounded. I can help you get a VB/Kali setup going with your ACM, but it will not happen fast because I would have to duplicate your setup (Linux instead of Windows for the host) but I have an ACM. Think about it and let me know.

Regards

[aibugra]

I also live in Adana, and things are getting better.