-
Notifications
You must be signed in to change notification settings - Fork 34
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
iw dev del hangs in OpenWrt #12
Comments
Hi. |
Thanks, i've already found the problem. The errors above were caused by base kernel headers utilizing slightly different wiphy structure. Rebuilding the module against the backport solve the issue.
Then any network operations hang and the kernel is unable to reboot properly. |
Looks like it's the common Realtek drivers problem according to this thread: |
I did tests for all three drivers on OpenWrt 19.07.10 with the same results as for OpenWrt 21.02.0. Your driver is the only usable, but also has "client mode authorization" issue on this version of OpenWrt: #14 |
I think I am running into similar issues (on openwrt 22.03), can you pls detail better how did you built against backport? But I get weird build errors. In file included from /home/valter/scorpio_v_next/openwrt/build_dir/target-aarch64_cortex-a53_musl/linux-bcm27xx_scorpio/linux-5.10.161/include/linux/bits.h:6, |
I managed to build the driver, now the device is detected and I can do a scan, but as soon as it tries to join a network it hangs. |
Looks like the same issue i described above. When adding or modifying a network Openwrt internally executing delete and add a virtual wireless interface commands:
Try via ssh |
Here is my OpenWrt Makefile:
Also, the driver source requires some fixes to build against OpenWrt tree:
|
Yes, it's exactly the same issue. I see that if I rmmod/insmod the driver the adapter is re-initialized, but not when it's stuck in that condition. This is my makefile and patches, I think I solved the issues more or less in the same way you did. |
I didn't test enough before posting this workaround, it still has issues if you change the adapter configuration. Ok, I have a kind of nasty workaround for openwrt. |
Second (hopefully better) attempt. |
After reading this post I came to the same conclusion about the need to patch the driver for error on delete interface attempt. Unfortunately i have not enough skills for this. But your solution modifying ash script is easy and efficient, thanks. Going to test it more, but seems everything works as it should. Except unknown signal quality and bitrate values for a connection in client mode, but seems it's Realtek and |
Summing it up, the problem is not in OpenWrt, the problem is Realtek drivers do not support virtual interfaces. But for some reason their driver allows |
And more, maybe this will be useful for someone. As i wrote before this version of driver is the only that doesn't hang for earlier OpenWrt versions on |
Hi,
the driver was successfully built for OpenWrt using buildroot, but doesn't recognize my adapter (TL-WN 722N v3).
Seems like the module is loaded ok, but when inserting an adapter it fails to init.
Kernel log and other info are below:
lsmod | grep 8188
lsusb
uname -r
Xiaomi Router 3G v1 using OpenWrt 22.03.0 r19685-512e76967f (ramips/mt7621)
Any suggestions how to fix it?
The text was updated successfully, but these errors were encountered: