search

aircrack-ng / rtl8188eus

RealTek RTL8188eus WiFi driver with monitor mode & frame injection support
958 stars 407 forks source link

Manjaro Linux: Wifi adapter (rtl8188eu) not detected after driver installation #297

Open FixedFish opened 5 days ago

FixedFish commented 5 days ago

I'm facing an issue with my rtl8188eu wifi adapter on Manjaro Linux with kernel 6.1.0. After compiling and installing the driver from here, the adapter isn't being detected by the system, even though the driver seems to be successfully installed and loaded.

What I've tried:

My system:

FixedFish commented 3 days ago

Used this fix for 6.1: https://github.com/gglluukk/rtl8188eus @gglluukk help me

gglluukk commented 2 days ago

I don't use Manjaro as well as any GUI tools: iwconfig could show if there are any interfaces for wifi.

Best approach is to upgrade to Manjaro 24.1 where it runs kernel 6.10 with builtin driver rtl8xxxu supporting all dongles with less bugs than rtl8188eus has

FixedFish commented 2 days ago

I don't use Manjaro as well as any GUI tools: iwconfig could show if there are any interfaces for wifi.

Best approach is to upgrade to Manjaro 24.1 where it runs kernel 6.10 with builtin driver rtl8xxxu supporting all dongles with less bugs than rtl8188eus has

Im already on manjaro 24.1, switched to kernel 6.10 and same, installed rtl8xxxu from github, iwconfig doesnt show my usb adapter

iwconfig lo no wireless extensions.

enp3s0 no wireless extensions.

enp0s29u1u4 no wireless extensions.

ip link 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 90:2b:34:47:ce:74 brd ff:ff:ff:ff:ff:ff 3: enp0s29u1u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000 link/ether aa:5d:83:65:81:aa brd ff:ff:ff:ff:ff:ff

lsusb Bus 002 Device 006: ID 350b:9101 ZTopInc 802.11n NIC

lsmod Module Size Used by rtl8xxxu_git 303104 0 mac80211 1609728 1 rtl8xxxu_git libarc4 12288 1 mac80211 cfg80211 1372160 2 rtl8xxxu_git,mac80211

gglluukk commented 2 days ago
dubhater commented 2 days ago

You can always add the ID 350b:9101 to usb_intf.c in this driver, or to core.c in rtl8xxxu and test. Maybe it's that simple.

FixedFish commented 1 day ago

You can always add the ID 350b:9101 to usb_intf.c in this driver, or to core.c in rtl8xxxu and test. Maybe it's that simple.

Adding ID to usb_intf.c looks like worked, ip_link shows wlan0, thanks. Should i do a pr with the addition of my usb adapter?

dubhater commented 1 day ago

If you can connect to a network, yes.

FixedFish commented 1 day ago

If you can connect to a network, yes.

cant up wlan0

ip link show wlan0 4: wlan0: <BROADCAST,MULTICAST> mtu 2312 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:e0:4c:5e:14:1f brd ff:ff:ff:ff:ff:ff

sudo ip link set wlan0 up RTNETLINK answers: Operation not permitted

ifconfig wlan0 wlan0: flags=4098<BROADCAST,MULTICAST> mtu 2312 ether 00:e0:4c:5e:14:1f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

dubhater commented 1 day ago

Change these lines in the makefile:

CONFIG_RTW_DEBUG = n           <- change to y
CONFIG_RTW_LOG_LEVEL = 0       <- change to 4

Recompile and reload the driver, then post the unfiltered output of dmesg. Then we can see what is going wrong.

FixedFish commented 1 day ago

Change these lines in the makefile:

CONFIG_RTW_DEBUG = n           <- change to y
CONFIG_RTW_LOG_LEVEL = 0       <- change to 4

Recompile and reload the driver, then post the unfiltered output of dmesg. Then we can see what is going wrong.

After i compiled with adding 350b:9101 into usb_intf.c, when compiled i get that warning

rtl8188eus/8188eu.o: warning: objtool: mp_xmit_packet_thread+0xb7: thread_exit() is missing a __noreturn annotation

Here dmesg output, driver cant initialize: dmesg_output.txt

FixedFish commented 1 day ago

Some info about my usb adapter.

After purchasing the adapter, it came with a driver disk (for Windows only). I requested Linux drivers from seller, downloaded them, but couldn't compile them. It seems they are intended for an older kernel version (probably 4.1.4). I can provide a link to the driver source code if needed.

dubhater commented 1 day ago

Yes, the Linux driver from the seller would be helpful. I think your chip is not RTL8188EUS.

FixedFish commented 1 day ago

Yes, the Linux driver from the seller would be helpful. I think your chip is not RTL8188EUS.

YandexDisk Only on YandexDisk, because seller from Russia That driver worked when i installed on Windows

dubhater commented 1 day ago

That's strange, because I can't find 350b:9101 in any of those Windows drivers, or in the Linux driver. But if you have it working in Windows, just look at Device Manager. The name of the chip should be there.

FixedFish commented 1 day ago

That's strange, because I can't find 350b:9101 in any of those Windows drivers, or in the Linux driver. But if you have it working in Windows, just look at Device Manager. The name of the chip should be there.

I dont have access Windows now, I'm on Manjaro, what i can do?

On this site shows it have 2310:9086 and 350b:910 https://treexy.com/products/driver-fusion/database/network-adapters/ztop-microelectronics/9101-usb-80211b-g-n-wireless-device/

Maybe it helpful

dubhater commented 1 day ago

Can you copy the Windows driver from the CD?

treexy.com wants you to install their driver downloader.

FixedFish commented 1 day ago

Dont have acces to pc now. I'll check the CD in the morning and let you know.

FixedFish commented 19 hours ago

Can you copy the Windows driver from the CD?

treexy.com wants you to install their driver downloader.

Drivers from CD here https://www.mediafire.com/file/l1yq742v67j6zft/Drivers.zip/file

In drivers cd i found that in version.log

`####driver info: version = 6271

firmware info:

ZT9101_fw_r2688_win `

FixedFish commented 9 hours ago

lspci output

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 06)

dubhater commented 8 hours ago

Okay, so the chip is called ZT9101. It's not a Realtek chip. I couldn't find any Linux driver.

dubhater commented 8 hours ago

But apparently this chip is used in some cameras, which run Linux, so a driver must exist. You should ask the OpenIPC folks if they know anything about it.

FixedFish commented 8 hours ago

But apparently this chip is used in some cameras, which run Linux, so a driver must exist. You should ask the OpenIPC folks if they know anything about it.

ndiswrapper can help or not?

dubhater commented 8 hours ago

I don't know.

FixedFish commented 8 hours ago

So what i can do except for help from OpenIPC?

dubhater commented 8 hours ago

You can return the device and tell the seller why (no Linux support). If you can return it.

dubhater commented 8 hours ago

Or you can use Wireshark in Windows to record all the USB communications between the driver and the chip and try to write a Linux driver. That could be fun!