-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: AWUS036ACH not entering monitor mode on Raspberry Pi 5 using Raspberry Pi OS #43
Comments
Excellent report. I did not understand that your issue was with monitor mode. What you are experiencing is not a bug but rather that monitor mode is not supported in this driver. From the README.md:
I made a decision about a year ago that any new out-of-kernel drivers that I bring up will not support monitor mode because Realtek simply does a bad job with monitor mode. I do not like to leave users hanging so there is a fallback plan. The new rtl8812au in-kernel driver was recently approved for merging into the Linux kernel. It is going into kernel 6.13 this week. In the meantime, you can install the repo we used to built it: https://github.com/lwfinger/rtw88 Follow the directions at that repo as they are somewhat different than here. Once you have the repo installed, you will be running the code that is going into the kernel. This driver was approved by Realtek but the work was not done by Realtek. I would like a report on how monitor mode is working. Let me know how it turns out. |
And do not forget to fully uninstall/remove this driver. |
I came here because i was having the same issue, I just want to confirm that monitor mode works using the repo you linked.. Thank you! |
? https://github.com/lwfinger/rtw88 Monitor mode works in the new driver. I have done basic testing but we need others to report results. |
I was having issues putting in monitor mode my AWUS036ACH (based on chipset RTL8812AU) on raspberry pi 5 with stock os and I got it to work after using the driver available here https://github.com/lwfinger/rtw88 @morrownr are you saying that it's supposed to work now? (despite the disclaimer in the README saying it is not supported) |
Let me clarify: The driver in this repo, 8812au-20210820, does not support monitor mode. There are no plans to support monitor mode. My efforts have been going into https://github.com/lwfinger/rtw88 . This rtw88 repo is being upstreamed into the linux kernel. In fact, the new drivers (rtw88) for rtl8812au and rtl8821au started going into the kernel with kernel 6.13 and finished with 6.14. Once you are using kernel 6.14 or later, there is no need to find and compile a driver. Until you get to kernel 6.14, you can use https://github.com/lwfinger/rtw88 . A new driver for the rtl8814au chip is in the process of going into the kernel right now. If all goes well, there will be a new (rtw88) in-kernel driver for rtl8814au based adapters in kernel 6.15 if all goes well and 6.16 if there is some slippage in the timeline. |
thank you @morrownr, you have confirmed what I was able to figure out in the last couple of weeks! I'm just a bit disappointed as a Debian user because it doesn't look like it will be included in Trixie, so I will keep compiling the driver from that repo for a while :) |
I am a Debian user also so I understand. On the other hand, the timing for Ubuntu 25.04 is perfect. The story: Dubhater, lwfinger and I started the project over one year ago. lwfinger passed away in May. Dubhater worked very hard but one big thing we ran into was the need to fix a LOT of things in rtw88. Patch after patch flowed into the kernel to get rtw88 into good enough shape to continue with the new drivers. We worked hard to get plenty of testers and helpers. I think rtw88 in kernel 6.14 is really good. A new driver for the rtl8814au chip is now going in and will hopefully be fully in kernel 6.15, if not, then kernel 6.16. As far as I can tell, that will give Linux users good drivers for all commonly used USB WiFi 5 chips. One thing am trying to do is get the message out to Linux users to avoid Realtek WiFi 6 and 7 based adapters as most of those adapters are multi-state (windows driver onboard) and there is no usb support in rtw89. That makes for unhappy Linux users. But there is no reason to be unhappy as Mediatek is making great in-kernel drivers for WiFi 6 and 7. https://github.com/morrownr/USB-WiFi Scroll down and read items 1 and 2. Cheers |
Checklist
Is Secure Boot enabled?
None
uname
Linux faradaypi 6.6.51+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt3 (2024-10-08) aarch64 GNU/Linux
lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
rfkill
0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: phy1: Wireless LAN Soft blocked: no Hard blocked: no
dkms
iw
git status
install-driver.sh
What happened?
The AWUS036ACH adapter appears in iwconfig and lsusb and is able to connect to and see nearby networks in Network Manager.
Running aireplay-ng --test wlan1 yields:
ioctl(SIOCSIWMODE) failed: Invalid argument
ioctl(SIOCSIWMODE) failed: Invalid argument
Error setting monitor mode on wlan1
Running hcxdumptool -i wlan1 yields:
**initialization of hcxdumptool 6.2.6 (depending on the capabilities of the device, this may take some time)...
failed to set monitor mode, ioctl(SIOCSIWMODE) not supported by driver: Invalid argument
warning: failed to init socket
terminating...
1 driver error encountered
usually this error is related to pselect() after SIGTERM has been received
ERRORs < 10 are related to a slow initialization and can be ignored**
I tried commenting out blacklist rtw88_8812au and blacklist rtw_8812au in the 8812au.conf file, but that did not work. I also have a AWUS036ACS and AXML adapter that both enter monitor mode no problem, I don't know if those drivers cause any conflicts with the installed 8812au driver
The text was updated successfully, but these errors were encountered: