Closed sskaje closed 1 year ago
Hi @sskaje
I've been looking over the information you posted. You aren't going to like what I am going say but please try to understand. From the README:
Note: OpenWRT is not supported. OpenWRT provides drivers for USB WiFi adapters. OpenWRT provided drivers include support for the MT7921au (AXE3000), MT7612u (AC1200), MT7610u (AC600) chipsets. It is a challenge to use Realtek based adapters that use out-of-kernel drivers with OpenWRT so it is strongly advised to use the already supported chipsets.
Words of advice: You will hurt yourself trying to make this work but that is unnecessary given the usb wifi drivers that are already provided in OpenWRT. Recommend you go to the site Main Menu:
https://github.com/morrownr/USB-WiFi
Reading menu item 1 is a good idea. Then open menu item 2 as it contains a lot of adapters that work in OpenWRT. I use adapters with mt7921au, mt7612u and my7610u. Use Luci to update Software and search with mt7
.
Hope this helps,
@morrownr
Hi @morrownr , thank you for your reply and also the "site Main Menu" repo.
You're right, realtek's official drivers are not reliable (including rtw88), some chip+driver works everywhere, some works only on popular linux + arch, or some device + certain config.
This nanopi has debian/ubuntu with same kernel from vendor, also hang, that's why I start an issue and ask if there is anything I can do to find out what causes the kernel or network related modules hang, maybe kernel misconfigured, etc.
I choose AX55 nano because it is small enough, like logitech's mouse/keyboard dongle, I can always leave it plugged in the small ARM device, not as wireless router but make my nanopi can be connected when I forgot to bring a ethernet adapter.
And also thank you for your recommendation, I did look up some MTK's alternatives, if I want to make my nanopi as wireless router, MT7921au devices are better choices.
This nanopi has debian/ubuntu with same kernel from vendor, also hang, that's why I start an issue and ask if there is anything I can do to find out what causes the kernel or network related modules hang, maybe kernel misconfigured, etc.
Finding the cause could be a challenge. Fixing it, if it is found, could be a real challenge as well. I did the best I could with this Realtek source but while working on it, I knew I needed to warn users that there are better alternatives out there. These Realtek out-of-kernel drivers are simply not made for desktop, server and even sbc use. They seem to be made for embedded systems and getting help from Realtek is not something that is available unless you are an adapter maker.
On the other hand, Mediatek appears to be all in with Linux wifi. Their drivers are Linux WiFi Standards compilant and we have the ability to communicate problems to the Mediatek kernel devs so as to get problems fixed, Kernel 6.7 will see a new MT7925 driver for a new WiFi 7 chipset that will be available for USB and PCIe. Hopefully we see the chipset made available to makers in 2024 and we will see adapters in late 2024 or early 2025. Note how the driver is going in long before we can buy an adapter. This is similar to Intel, AMD and other power players in the Linux world. The difference between Mediatek and Realtek Linux support for USB WiFi is huge.
I wish you luck if you decide to continue getting your adapter working but I'll need you to narrow down what the problem likely is before I can take a crack at it as I am very busy on other projects right now.
@morrownr
@morrownr Thank you, I think I should try MTK devices instead of wasting time on realtek.
Do you need help checking to see what drivers are in the kernel of FriendlyWRT? I am not familiar with it but it might a good idea to check before you get a new adapter.
OpenWRT has drivers and firmware for several adapters including the following: mt7921au, mt7612u and mt7610u. With OpenWRT, you have to install the packages for the drivers. I so not know how FWRT works?
@morrownr , Thank you, I can do it by myself, and I have experiences porting latest rtw88 to get rtl8822bu work.
The kernel driver for mt76 are here, I see mt7921 code with usb is included.
Remember that in-kernel drivers require one or more firmware files:
Don't forget to check them.
Remember that in-kernel drivers require one or more firmware files:
Don't forget to check them.
Thank you, your guide helped me again on MT7922
You are welcome. I have a PCIe card based on the mt7922 I really like it and I thought I saw signs of a usb version of the mt7922 would be made available but am not so sure now with the mt7925 driver going into kernel 6.7 as we speak. The mt7925 WILL have a usb version per the patches adding the new driver to the kernel. It is a WiFi 7 capable chipset. Hopefully we have adapters available for purchase at some point in 2024.
Platform: NanoPi R6s (arm64, rk3588s) + FriendlyWRT (an OpenWrt fork for NanoPi) Kernel: 5.10, 6.1 Kernel repo: https://github.com/friendlyarm/kernel-rockchip Dongle: Asus AX53 Nano Ethernet connected
Tested on Dell Laptop + Debian Bookworm, amd64, works pefect, with https://github.com/lakinduakash/linux-wifi-hotspot
OpenWrt AP settings: Mode AX, 5GHz, Channel: 36/149, bandwidth: 20/80MHz, Country Code US
Kernel module is loaded on boot, with the 8852bu.conf from this repo.
On this OpenWrt fork, dongle can be recognized.
When I plugged the device in, configured openwrt and clicked apply, Luci not responding,
iw list
not responding,ifconfig
not responding.If I start the device with dongle plugged in, network hang, cannot access remotely, console access with keyboard + monitor is fine.
iw list
,ifconfig
also responding.Such not responding, I can't interrupt by ctrl+c from ssh or console. But if it's frozen after luci clicking apply, I can still start an new ssh connection.
If kernel module is not auto loaded on boot, no frozen on boot if with dongle plugged in.
I enabled DEBUG in Makefile, and paste the full dmesg at the bottom, kernel no message at all after rtw_wdev_unregister.
RTW88 rtl8822bu + AC53-Nano works well.
Is there anyway to find out what froze the network?
I also tried to follow modifications of other rtl drivers by the device vendor's github, all same behaviors.
lsusb
no rfkill, no dkms
iw list
Default dmesg
dmesg with CONFIG_RTW_DEBUG on and log level = 5